[kig] [Bug 490427] New: Could not find plugin kf5/parts/kigpart when start kig

[Tong Chen]

https://bugs.kde.org/show_bug.cgi?id=490427

Bug ID: 490427
   Summary: Could not find plugin kf5/parts/kigpart  when start
kig
Classification: Applications
   Product: kig
   Version: unspecified
  Platform: RedHat Enterprise Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: david.narv...@computer.org
  Reporter: tomz...@outlook.com
  Target Milestone: ---

***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

I'm testing kig compiled from the master source code of github.  When I start
the program in my terminal, it says like this:

Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use
QT_QPA_PLATFORM=wayland to run on Wayland anyway.
kf.coreaddons: "Could not find plugin kf5/parts/kigpart"
Segmentation fault (core dumped)

but the kigpart plugin is actually located at :
/usr/local/lib64/plugins/kf5/parts/kigpart.so

Feeling like this is a version matching issue, but I'm not sure.
The code is built with kf5 in rockylinux 8, i.e. centos 8 or redhat 8.

The kig version can get from the kig_version.h in kig source code base from
github:
  1 // This file was generated by ecm_setup_version(): DO NOT EDIT! 
  2 
  3 #ifndef KIG_VERSION_H   
  4 #define KIG_VERSION_H   
  5 
  6 #define KIG_VERSION_STRING "24.07.70"   
  7 #define KIG_VERSION_MAJOR 24
  8 #define KIG_VERSION_MINOR 7 
  9 #define KIG_VERSION_PATCH 70
 10 #define KIG_VERSION ((24<<16)|(7<<8)|(70))  
 11 
 12 #endif 

STEPS TO REPRODUCE
1.  download source code(master.zip) from github
2.  build it with cmake, and make install in rockylinux 8
3.  just start kig in terminal, with kig or kig &

OBSERVED RESULT
error msg of the cmd:
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use
QT_QPA_PLATFORM=wayland to run on Wayland anyway.
kf.coreaddons: "Could not find plugin kf5/parts/kigpart"
Segmentation fault (core dumped)

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: rockylinux 8 + kf5-kparts-devel-5.96.0-1.el8.x86_64
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: kf5-kparts-devel-5.96.0-1.el8.x86_64
Qt Version: qt5

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmplot] [Bug 488338] New: No "show sliders" in view menu

[Haonan Chen]

https://bugs.kde.org/show_bug.cgi?id=488338

Bug ID: 488338
   Summary: No "show sliders" in view menu
Classification: Applications
   Product: kmplot
   Version: unspecified
  Platform: NixOS
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: cf...@kde.org
  Reporter: c...@chn.moe
  Target Milestone: ---

Created attachment 170363
  --> https://bugs.kde.org/attachment.cgi?id=170363=edit
"view" menu of kmplot

SUMMARY

No "show sliders" in the "view" menu. The slider window could still be opened
by setting a keyboard shortcut.

Version 1.3.24022.

STEPS TO REPRODUCE

Open kmplot, click "view". There is only an option "fullscreen". (please see
attachment)

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: yes
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 486799] New: plasma crash when i wake up my computer from sleep

[Shaoze Chen]

https://bugs.kde.org/show_bug.cgi?id=486799

Bug ID: 486799
   Summary: plasma crash when i wake up my computer from sleep
Classification: Plasma
   Product: plasmashell
   Version: 6.0.4
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: mail.szc...@gmail.com
  Target Milestone: 1.0

Application: plasmashell (6.0.4)

Qt Version: 6.7.0
Frameworks Version: 6.1.0
Operating System: Linux 6.6.30-1-lts x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 6.0.4 [CoredumpBackend]

-- Information about the crash:
my plasmashell often crash when I boot up my computer and I wake up my computer
from sleep. Once it crashed, taskbar will reset to default.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: plasmashell (plasmashell), signal: Segmentation fault


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 1236684]
[New LWP 3159]
[New LWP 3161]
[New LWP 3240]
[New LWP 3162]
[New LWP 3292]
[New LWP 3316]
[New LWP 3315]
[New LWP 3293]
[New LWP 3317]
[New LWP 4184]
[New LWP 4164]
[New LWP 1192852]
[New LWP 4163]
[New LWP 4168]
[New LWP 4166]
[New LWP 4176]
[New LWP 4174]
[New LWP 4186]
[New LWP 4115]
[New LWP 4139]
[New LWP 6314]
[New LWP 4160]
[New LWP 4161]
[New LWP 4169]
[New LWP 4162]
[New LWP 4165]
[New LWP 4167]
[New LWP 4170]
[New LWP 4171]
[New LWP 4173]
[New LWP 5753]
[New LWP 4172]
[New LWP 4175]
[New LWP 4179]
[New LWP 4180]
[New LWP 4181]
[New LWP 4182]
[New LWP 4183]
[New LWP 4185]
[New LWP 5754]
[New LWP 5755]
[New LWP 5756]
[New LWP 48541]
[New LWP 1192841]
[New LWP 1192851]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x75a3780ac194 in ?? () from /usr/lib/libc.so.6
[Current thread is 1 (Thread 0x75a2dae5e6c0 (LWP 1236684))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x75a2dae5e6c0 (LWP 1236684))]

Thread 46 (Thread 0x75a249fff6c0 (LWP 1192851)):
#0  0x75a3780a68d9 in ??? () at /usr/lib/libc.so.6
#1  0x75a3780a9299 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x75a3788b8a80 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x75a37a1f341a in ??? () at /usr/lib/libQt6Quick.so.6
#4  0x75a3788adbc3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x75a3780aa1cf in ??? () at /usr/lib/libc.so.6
#6  0x75a37812b6ec in ??? () at /usr/lib/libc.so.6

Thread 45 (Thread 0x75a2427fe6c0 (LWP 1192841)):
#0  0x75a3780a68d9 in ??? () at /usr/lib/libc.so.6
#1  0x75a3780a9299 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x75a3788b8a80 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x75a37a1f341a in ??? () at /usr/lib/libQt6Quick.so.6
#4  0x75a3788adbc3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x75a3780aa1cf in ??? () at /usr/lib/libc.so.6
#6  0x75a37812b6ec in ??? () at /usr/lib/libc.so.6

Thread 44 (Thread 0x75a242fff6c0 (LWP 48541)):
#0  0x75a3780a68d9 in ??? () at /usr/lib/libc.so.6
#1  0x75a3780a9299 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x75a3788b8a80 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x75a37a1f341a in ??? () at /usr/lib/libQt6Quick.so.6
#4  0x75a3788adbc3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x75a3780aa1cf in ??? () at /usr/lib/libc.so.6
#6  0x75a37812b6ec in ??? () at /usr/lib/libc.so.6

Thread 43 (Thread 0x75a32b7fe6c0 (LWP 5756)):
#0  0x75a37811d9ed in poll () at /usr/lib/libc.so.6
#1  0x75a3773a8306 in ??? () at /usr/lib/libglib-2.0.so.0
#2  0x75a377349dc7 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0
#3  0x75a373bf783c in ??? () at /usr/lib/libgio-2.0.so.0
#4  0x75a377377065 in ??? () at /usr/lib/libglib-2.0.so.0
#5  0x75a3780aa1cf in ??? () at /usr/lib/libc.so.6
#6  0x75a37812b6ec in ??? () at /usr/lib/libc.so.6

Thread 42 (Thread 0x75a32bfff6c0 (LWP 5755)):
#0  0x75a37812948d in syscall () at /usr/lib/libc.so.6
#1  0x75a3773a3487 in g_cond_wait () at /usr/lib/libglib-2.0.so.0
#2  0x75a377313454 in ??? () at /usr/lib/libglib-2.0.so.0
#3  0x75a37737829e in ??? () at /usr/lib/libglib-2.0.so.0
#4  0x75a377377065 in ??? () at /usr/lib/libglib-2.0.so.0
#5  0x75a3780aa1cf in ??? () at /usr/lib/libc.so.6
#6  0x75a37812b6ec in ??? () at /usr/lib/libc.so.6

Thread 41 (Thread 0x75a32a7fc6c0 (LWP 

[valgrind] [Bug 457504] Add LOONGARCH64/Linux port to Valgrind

[Feiyang Chen]

https://bugs.kde.org/show_bug.cgi?id=457504

Feiyang Chen  changed:

   What|Removed |Added

Version|3.23 GIT|unspecified

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 457504] Add LOONGARCH64/Linux port to Valgrind

[Feiyang Chen]

https://bugs.kde.org/show_bug.cgi?id=457504

--- Comment #19 from Feiyang Chen  ---
Created attachment 168969
  --> https://bugs.kde.org/attachment.cgi?id=168969=edit
patches-v7

Based on 42ec38caebf9024ed2f875f0eae5d6b801a9dd04.

== 728 tests, 4 stderr failures, 0 stdout failures, 0 stderrB failures, 0
stdoutB failures, 0 post failures ==
helgrind/tests/getaddrinfo   (stderr)
drd/tests/getaddrinfo(stderr)
drd/tests/pth_mutex_signal   (stderr)
none/tests/libvexmultiarch_test  (stderr)

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 484555] Enhance with “Create folder from selected files”

[Chengkun Chen]

https://bugs.kde.org/show_bug.cgi?id=484555

Chengkun Chen  changed:

   What|Removed |Added

 CC||serix2...@outlook.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 457504] Add LOONGARCH64/Linux port to Valgrind

[Feiyang Chen]

https://bugs.kde.org/show_bug.cgi?id=457504

Feiyang Chen  changed:

   What|Removed |Added

Version|3.22 GIT|3.23 GIT

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 457504] Add LOONGARCH64/Linux port to Valgrind

[Feiyang Chen]

https://bugs.kde.org/show_bug.cgi?id=457504

--- Comment #18 from Feiyang Chen  ---
Created attachment 164702
  --> https://bugs.kde.org/attachment.cgi?id=164702=edit
patches-v6

Changes:
- Rebased on 6c949b85762849c70b65db803eae547874edffa3.
- Add basic 128-bit/256-bit vector support.
- Squashed commits into 4 patches.

Test environment:
# uname -a
Linux fedora 6.6.0-0.rc4.20231005git3006adf3be79.36.fc38.loongarch64 #1 SMP
PREEMPT Sun Oct  8 14:18:09 CST 2023 loongarch64 GNU/Linux
# ld --version
GNU ld version 2.41-5.fc38
# gcc --version
gcc (GCC) 13.2.1 20230728 (Red Hat 13.2.1-2)
# ldd --version
ldd (GNU libc) 2.38.9000
# cat /etc/os-release
NAME="Fedora Linux"
VERSION="38 (MATE-Compiz Prerelease)"
ID=fedora
VERSION_ID=38
VERSION_CODENAME=""
PLATFORM_ID="platform:f38"
PRETTY_NAME="Fedora Linux 38 (MATE-Compiz Prerelease)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:38"
DEFAULT_HOSTNAME="fedora"
HOME_URL="https://fedoraproject.org/;
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/rawhide/system-administrators-guide/;
SUPPORT_URL="https://ask.fedoraproject.org/;
BUG_REPORT_URL="https://bugzilla.redhat.com/;
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=rawhide
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=rawhide
VARIANT="MATE-Compiz"
VARIANT_ID=matecompiz

Test results:
== 717 tests, 2 stderr failures, 0 stdout failures, 0 stderrB failures, 0
stdoutB failures, 0 post failures ==
drd/tests/pth_mutex_signal   (stderr)
none/tests/libvexmultiarch_test  (stderr)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 362493] quoting with blockquote

[Yaohan Chen]

https://bugs.kde.org/show_bug.cgi?id=362493

Yaohan Chen  changed:

   What|Removed |Added

 CC||yaohan.c...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 464967] dolphin process for another user (using kdesu) crashes after screen wake

[Kolei Chen]

https://bugs.kde.org/show_bug.cgi?id=464967

Kolei Chen  changed:

   What|Removed |Added

   Platform|Manjaro |Archlinux
 CC||chenko...@gmail.com
Version|22.12.3 |23.08.1

--- Comment #11 from Kolei Chen  ---
I also have the same problem with 23.08.1, it's reproducible every time I turn
off my monitor and turn it back on.
BTW, every time when it crashed, it was allocating a large amount of RAM (about
6GiB or more).
OS: Arch Linux
CPU: AMD Ryzen 5 5600X
GPU: AMD RX6500XT

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 474171] New: Dolphin crashes when turning screen on

[Kolei Chen]

https://bugs.kde.org/show_bug.cgi?id=474171

Bug ID: 474171
   Summary: Dolphin crashes when turning screen on
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: chenko...@gmail.com
  Target Milestone: ---

Application: dolphin (23.08.0)

Qt Version: 5.15.10
Frameworks Version: 5.109.0
Operating System: Linux 6.1.51-1-lts x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.27.7 [KCrashBackend]

-- Information about the crash:
Dolphin almost always crashes when I turn on the screen on

CPU: Happens on both Ryzen 5 2400G and 5600X
GPU: Radeon RX6800

The crash can be reproduced every time.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6  __memcpy_avx_unaligned () at
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:220
#7  0x7fb9fcbab38a in memmove (__len=262112, __src=0x7fb511a7e810,
__dest=) at /usr/include/bits/string_fortified.h:36
#8  copy_unswapped (rect=..., img=...,
dstBytesPerLine=262112, dst=) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:547
#9  native_sub_image (swap=false, rect=..., src=, dstStride=262112, buffer=) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:590
#10 QXcbBackingStoreImage::flushPixmap(QRegion const&, bool)
(this=this@entry=0x55f273f70b60, region=..., fullRegion=) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:669
#11 0x7fb9fcbab6d3 in QXcbBackingStoreImage::flushPixmap(QRegion const&,
bool) (fullRegion=, this=this@entry=0x55f273f70b60, region=...,
fullRegion=fullRegion@entry=true) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:690
#12 0x7fb9fcbab937 in QXcbBackingStoreImage::flushPixmap(QRegion const&,
bool) (fullRegion=false, region=..., this=0x55f273f70b60) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:627
#13 QXcbBackingStoreImage::put(unsigned int, QRegion const&, QPoint const&)
(this=0x55f273f70b60, dst=153092125, region=..., offset=) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:741
#14 0x7fb9fcbac28e in QXcbBackingStore::flush(QWindow*, QRegion const&,
QPoint const&) (this=0x55f273e316d0, window=, region=, offset=...) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbbackingstore.cpp:877
#15 0x7fba02cea9f7 in QBackingStore::flush(QRegion const&, QWindow*, QPoint
const&) () at /usr/lib/libQt5Gui.so.5
#16 0x7fba03382ad1 in  () at /usr/lib/libQt5Widgets.so.5
#17 0x7fba03383025 in  () at /usr/lib/libQt5Widgets.so.5
#18 0x7fba0338472d in  () at /usr/lib/libQt5Widgets.so.5
#19 0x7fba033d0a70 in  () at /usr/lib/libQt5Widgets.so.5
#20 0x7fba0337893f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#21 0x7fba0269c6f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55f273e6c680, event=0x7ffc848b6930) at
kernel/qcoreapplication.cpp:1064
#22 0x7fba02b45986 in
QGuiApplicationPrivate::processGeometryChangeEvent(QWindowSystemInterfacePrivate::GeometryChangeEvent*)
() at /usr/lib/libQt5Gui.so.5
#23 0x7fba02b2a6c5 in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() at /usr/lib/libQt5Gui.so.5
#24 0x7fb9fcbb33e0 in xcbSourceDispatch(GSource*, GSourceFunc, gpointer)
(source=) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbeventdispatcher.cpp:105
#25 0x7fba00510a61 in g_main_dispatch (context=0x7fb9f8000ee0) at
../glib/glib/gmain.c:3460
#26 g_main_context_dispatch (context=0x7fb9f8000ee0) at
../glib/glib/gmain.c:4200
#27 0x7fba0056dc29 in g_main_context_iterate.isra.0
(context=context@entry=0x7fb9f8000ee0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4276
#28 0x7fba0050e112 in g_main_context_iteration (context=0x7fb9f8000ee0,
may_block=1) at ../glib/glib/gmain.c:4343
#29 0x7fba026eb51c in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x55f27383ca40, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#30 0x7fba0269b404 in
QEventLoop::exec(QFlags)
(this=this@entry=0x7ffc848b6c20, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#31 0x7fba0269c8a3 in QCoreApplication::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#32 0x55f272fabdb8 in main(int, char**) (argc=,
argv=) at
/usr/src/debug/dolphin/dolphin-23.08.0/src/main.cpp:255
[Inferior 1 (process 42538) detached]

The reporter indicates this bug may be a duplicate of or related to bug 472240,
bug 472418.

Reported using 

[valgrind] [Bug 457504] Add LOONGARCH64/Linux port to Valgrind

[Feiyang Chen]

https://bugs.kde.org/show_bug.cgi?id=457504

--- Comment #17 from Feiyang Chen  ---
Test on Fedora 38:
https://mirrors.wsyu.edu.cn/fedora/linux/development/rawhide/Everything/loongarch64/iso/livecd-fedora-mate-4.loongarch64.iso

== 689 tests, 3 stderr failures, 0 stdout failures, 0 stderrB failures, 0
stdoutB failures, 0 post failures ==
helgrind/tests/pth_mempcpy_false_races   (stderr)
drd/tests/pth_mutex_signal   (stderr)
none/tests/libvexmultiarch_test  (stderr)

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 457504] Add LOONGARCH64/Linux port to Valgrind

[Feiyang Chen]

https://bugs.kde.org/show_bug.cgi?id=457504

Feiyang Chen  changed:

   What|Removed |Added

Version|3.21 GIT|3.22 GIT

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 457504] Add LOONGARCH64/Linux port to Valgrind

[Feiyang Chen]

https://bugs.kde.org/show_bug.cgi?id=457504

--- Comment #16 from Feiyang Chen  ---
Created attachment 159998
  --> https://bugs.kde.org/attachment.cgi?id=159998=edit
patches-v5

Rebase on b4cc7815ba722426c5456831f858a2aeceb3761f and squash commits.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kirigami] [Bug 465154] (Regression.) GlobalDrawer{} Z-order drawn on top of descendant elements, like Controls.Menu{} and Kirigami Tooltips.

[Will Chen]

https://bugs.kde.org/show_bug.cgi?id=465154

--- Comment #4 from Will Chen  ---
Seems like there are quite a few places where `.z` gets imperatively or
declaratively assigned an arbitrary-but-high value:

https://invent.kde.org/search?search=z%3A_id=2506_id=1552_code=true_ref=master
https://invent.kde.org/search?search=z+%3D_id=2506_id=1552_code=true_ref=master

I guess the question then is why, and what changed that this didn't used to
happen.

IIRC Personally I have been working around this by simply unsetting `.z` in my
GlobalDrawer instance, so it's not a showstopper— I guess that would still
cause a single right click event to be missed, and have no effect, when the bug
and hierarchy change is triggered, though.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Falkon] [Bug 458645] Adblock is absolutely useless in the current state

[Will Chen]

https://bugs.kde.org/show_bug.cgi?id=458645

Will Chen  changed:

   What|Removed |Added

 CC||inbox@willchen.business

--- Comment #4 from Will Chen  ---
> When will you finally add ublock origin to your browser? That would be the 
> solution for everything (at least for now).

As I understand it, the problem is that it's really not as easy as to simply
"add UBlock Origin". QTWebEngine does not support the same extensions API as
Firefox, Chromium, etc (https://bugs.kde.org/show_bug.cgi?id=393358,
https://bugreports.qt.io/browse/QTBUG-70370,
https://bugreports.qt.io/browse/QTBUG-61676). As a result, any "Extensions"
that are available for Falkon basically have to be completely reprogrammed
starting from nothing. QT provides capabilities that make ad blocking possible,
but bear in mind that projects like UBlock Origin, Adblock (Plus), and so on
are major team efforts with multiple contributors that have built up their
capabilities over many years.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krunner] [Bug 468043] New: KRunner doesn't focus correct window when switching to window on other virtual desktop.

[Will Chen]

https://bugs.kde.org/show_bug.cgi?id=468043

Bug ID: 468043
   Summary: KRunner doesn't focus correct window when switching to
window on other virtual desktop.
Classification: Plasma
   Product: krunner
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: windows
  Assignee: plasma-b...@kde.org
  Reporter: inbox@willchen.business
CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de
  Target Milestone: ---

KDE

When using KRunner to switch to a window on a different virtual desktop,
KRunner switches to that virtual desktop but does not focus the chosen window.


STEPS TO REPRODUCE
1. On one virtual desktop, open at least two distinct windows.
2. Remember which window has focus.
3. Switch to a different virtual desktop (which possibly has its own windows).
4. Press Alt+F2 to launch KRunner. Type the title of one of the non-focused
windows you opened in Step 1. Select it.

OBSERVED RESULT

KRunner switches to the original virtual desktop, but the selected window does
not gain focus.


EXPECTED RESULT

KRunner should switch to the original virtual desktop, and the selected window
should gain focus.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: X
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kirigami] [Bug 465154] (Regression.) GlobalDrawer{} Z-order drawn on top of descendant elements, like Controls.Menu{} and Kirigami Tooltips.

[Will Chen]

https://bugs.kde.org/show_bug.cgi?id=465154

--- Comment #3 from Will Chen  ---
I neglected to mention this in my original report. I believe this is a recent
regression. It only started happening on my main machine when I updated in
January, and it does not happen, for example, in NixPkgs
`23.05pre436403.ba6ba2b9009` from December 20 2022, corresponding to Kirigami2
5.101.0.

https://github.com/NixOS/nixpkgs/tree/ba6ba2b90096dc49f448aa4d4d783b5081b1cc87

```
nix-repl> pkgs.libsForQt5.kirigami2.version
"5.101.0"
```

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kirigami] [Bug 465154] (Regression.) GlobalDrawer{} Z-order drawn on top of descendant elements, like Controls.Menu{} and Kirigami Tooltips.

[Will Chen]

https://bugs.kde.org/show_bug.cgi?id=465154

Will Chen  changed:

   What|Removed |Added

Summary|GlobalDrawer{} Z-order  |(Regression.)
   |drawn on top of descendant  |GlobalDrawer{} Z-order
   |elements, like  |drawn on top of descendant
   |Controls.Menu{} and |elements, like
   |Kirigami Tooltips.  |Controls.Menu{} and
   ||Kirigami Tooltips.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 457504] Add LOONGARCH64/Linux port to Valgrind

[Feiyang Chen]

https://bugs.kde.org/show_bug.cgi?id=457504

--- Comment #12 from Feiyang Chen  ---
(In reply to Paul Floyd from comment #11)
> Same mistake as last time, didn't delete the merge artifacts.
> 
> paulf> gmake post-regtest-checks
> tests/post_regtest_checks
> /usr/home/paulf/scratch/valgrind_ports/loongson_valgrind2 gdbserver_tests
> memcheck cachegrind callgrind helgrind drd massif dhat lackey none exp-bbv
> ...checking makefile consistency
> none/tests/loongarch64/Makefile.am:1: error: atomic.stderr.exp is in
> EXTRA_DIST but doesn't exist
> none/tests/loongarch64/Makefile.am:1: error: branch.stderr.exp is in
> EXTRA_DIST but doesn't exist
> none/tests/loongarch64/Makefile.am:1: error: cpucfg.stderr.exp is in
> EXTRA_DIST but doesn't exist
> none/tests/loongarch64/Makefile.am:1: error: float.stderr.exp is in
> EXTRA_DIST but doesn't exist
> none/tests/loongarch64/Makefile.am:1: error: integer.stderr.exp is in
> EXTRA_DIST but doesn't exist
> none/tests/loongarch64/Makefile.am:1: error: llsc.stderr.exp is in
> EXTRA_DIST but doesn't exist
> none/tests/loongarch64/Makefile.am:1: error: memory.stderr.exp is in
> EXTRA_DIST but doesn't exist
> none/tests/loongarch64/Makefile.am:1: error: move.stderr.exp is in
> EXTRA_DIST but doesn't exist
> none/tests/loongarch64/Makefile.am:1: error: pc.stderr.exp is in EXTRA_DIST
> but doesn't exist
> none/tests/loongarch64/Makefile.am:1: error: special.stderr.exp is in
> EXTRA_DIST but doesn't exist

Most of these files were introduced by the v4-0104 patch.
I don't know why these empty files are missing :)
Or can I just remove them from my local tree and EXTRA_DIST?

Subject: [PATCH v4 104/123] loongarch64: Add dummy none tests

---
 .gitignore| 15 ++
 configure.ac  |  1 +
 none/tests/Makefile.am|  9 +---
 none/tests/allexec_prepare_prereq | 13 ++--
 none/tests/loongarch64/Makefile.am| 25 +++
 none/tests/loongarch64/allexec.c  |  1 +
 none/tests/loongarch64/atomic.c   |  5 +
 none/tests/loongarch64/atomic.stderr.exp  |  0
 none/tests/loongarch64/atomic.stdout.exp  |  0
 none/tests/loongarch64/atomic.vgtest  |  2 ++
 none/tests/loongarch64/branch.c   |  5 +
 none/tests/loongarch64/branch.stderr.exp  |  0
 none/tests/loongarch64/branch.stdout.exp  |  0
 none/tests/loongarch64/branch.vgtest  |  2 ++
 none/tests/loongarch64/filter_stderr  |  3 +++
 none/tests/loongarch64/float.c|  5 +
 none/tests/loongarch64/float.stderr.exp   |  0
 none/tests/loongarch64/float.stdout.exp   |  0
 none/tests/loongarch64/float.vgtest   |  2 ++
 none/tests/loongarch64/integer.c  |  5 +
 none/tests/loongarch64/integer.stderr.exp |  0
 none/tests/loongarch64/integer.stdout.exp |  0
 none/tests/loongarch64/integer.vgtest |  2 ++
 none/tests/loongarch64/memory.c   |  5 +
 none/tests/loongarch64/memory.stderr.exp  |  0
 none/tests/loongarch64/memory.stdout.exp  |  0
 none/tests/loongarch64/memory.vgtest  |  2 ++
 27 files changed, 93 insertions(+), 9 deletions(-)
 create mode 100644 none/tests/loongarch64/Makefile.am
 create mode 12 none/tests/loongarch64/allexec.c
 create mode 100644 none/tests/loongarch64/atomic.c
 create mode 100644 none/tests/loongarch64/atomic.stderr.exp
 create mode 100644 none/tests/loongarch64/atomic.stdout.exp
 create mode 100644 none/tests/loongarch64/atomic.vgtest
 create mode 100644 none/tests/loongarch64/branch.c
 create mode 100644 none/tests/loongarch64/branch.stderr.exp
 create mode 100644 none/tests/loongarch64/branch.stdout.exp
 create mode 100644 none/tests/loongarch64/branch.vgtest
 create mode 100755 none/tests/loongarch64/filter_stderr
 create mode 100644 none/tests/loongarch64/float.c
 create mode 100644 none/tests/loongarch64/float.stderr.exp
 create mode 100644 none/tests/loongarch64/float.stdout.exp
 create mode 100644 none/tests/loongarch64/float.vgtest
 create mode 100644 none/tests/loongarch64/integer.c
 create mode 100644 none/tests/loongarch64/integer.stderr.exp
 create mode 100644 none/tests/loongarch64/integer.stdout.exp
 create mode 100644 none/tests/loongarch64/integer.vgtest
 create mode 100644 none/tests/loongarch64/memory.c
 create mode 100644 none/tests/loongarch64/memory.stderr.exp
 create mode 100644 none/tests/loongarch64/memory.stdout.exp
 create mode 100644 none/tests/loongarch64/memory.vgtest

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kirigami] [Bug 465154] GlobalDrawer{} Z-order drawn on top of descendant elements, like Controls.Menu{} and Kirigami Tooltips.

[Will Chen]

https://bugs.kde.org/show_bug.cgi?id=465154

--- Comment #2 from Will Chen  ---
Manually setting the Z-Order can fix it as a temporary workaround:

```QML
_testMenu.z = _globalDrawer.z + 1
```

At the point where it breaks, the ancestry tree of the button and the
GlobalMenu{} itself changes:

```QML
let ancestry = []
let p = parent
while (p) {
console.log(p)
ancestry.push(p)
p = p.parent
}

console.log(ancestry.map(x => x.toString()))
```

Working:

```Console
qml: StableCollapsibleIconButton_QMLTYPE_116(0x55b9ea241dd0)
qml: TabDelegateBase_QMLTYPE_119(0x55b9e8c99e30)
qml: QQuickItem(0x55b9e5b37300)
qml: QQuickListView(0x55b9e5b40ce0)
qml: QQuickColumnLayout_QML_151(0x55b9e5b8b450)
qml: QQuickColumnLayout(0x55b9e5a352d0)
qml: QQuickItem(0x55b9e6461f50)
qml: QQuickFlickable(0x55b9e5be8290)
qml: ScrollView_QMLTYPE_95(0x55b9e5cbca10)
qml: QQuickPopupItem(0x55b9e58600c0)
qml: QQuickRootItem(0x55b9e5913c50)
qml:
[StableCollapsibleIconButton_QMLTYPE_116(0x55b9ea241dd0),TabDelegateBase_QMLTYPE_119(0x55b9e8c99e30),QQuickItem(0x55b9e5b37300),QQuickListView(0x55b9e5b40ce0),QQuickColumnLayout_QML_151(0x55b9e5b8b450),QQuickColumnLayout(0x55b9e5a352d0),QQuickItem(0x55b9e6461f50),QQuickFlickable(0x55b9e5be8290),ScrollView_QMLTYPE_95(0x55b9e5cbca10),QQuickPopupItem(0x55b9e58600c0),QQuickRootItem(0x55b9e5913c50)]
```

Broken:

```Console
qml: StableCollapsibleIconButton_QMLTYPE_116(0x55b9ea241dd0)
qml: TabDelegateBase_QMLTYPE_119(0x55b9e8c99e30)
qml: QQuickItem(0x55b9e5b37300)
qml: QQuickListView(0x55b9e5b40ce0)
qml: QQuickColumnLayout_QML_151(0x55b9e5b8b450)
qml: QQuickColumnLayout(0x55b9e5a352d0)
qml: QQuickItem(0x55b9e6461f50)
qml: QQuickFlickable(0x55b9e5be8290)
qml: ScrollView_QMLTYPE_95(0x55b9e5cbca10)
qml: QQuickPopupItem(0x55b9e58600c0)
qml: QQuickOverlay(0x55b9e59b2230) ←←← This is new.
qml: QQuickRootItem(0x55b9e5913c50)
qml:
[StableCollapsibleIconButton_QMLTYPE_116(0x55b9ea241dd0),TabDelegateBase_QMLTYPE_119(0x55b9e8c99e30),QQuickItem(0x55b9e5b37300),QQuickListView(0x55b9e5b40ce0),QQuickColumnLayout_QML_151(0x55b9e5b8b450),QQuickColumnLayout(0x55b9e5a352d0),QQuickItem(0x55b9e6461f50),QQuickFlickable(0x55b9e5be8290),ScrollView_QMLTYPE_95(0x55b9e5cbca10),QQuickPopupItem(0x55b9e58600c0),QQuickOverlay(0x55b9e59b2230),QQuickRootItem(0x55b9e5913c50)]
```

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kirigami] [Bug 465154] GlobalDrawer{} Z-order drawn on top of descendant elements, like Controls.Menu{} and Kirigami Tooltips.

[Will Chen]

https://bugs.kde.org/show_bug.cgi?id=465154

Will Chen  changed:

   What|Removed |Added

Summary|Inconsistent Z-order for|GlobalDrawer{} Z-order
   |GlobalDrawer{} with |drawn on top of descendant
   |Controls.Menu{}.|elements, like
   ||Controls.Menu{} and
   ||Kirigami Tooltips.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kirigami] [Bug 465154] Inconsistent Z-order for GlobalDrawer{} with Controls.Menu{}.

[Will Chen]

https://bugs.kde.org/show_bug.cgi?id=465154

--- Comment #1 from Will Chen  ---
Created attachment 155871
  --> https://bugs.kde.org/attachment.cgi?id=155871=edit
Tooltips are also covered.

This also happens to tooltips, as can be seen in Kirigami Gallery 22.12.1 when
the GlobalDrawer is set to "Collapsible Sidebar Drawer" and you mouse over the
"Close Sidebar" button at the bottom. (See attached screenshot.)

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kirigami] [Bug 465154] New: Inconsistent Z-order for GlobalDrawer{} with Controls.Menu{}.

[Will Chen]

https://bugs.kde.org/show_bug.cgi?id=465154

Bug ID: 465154
   Summary: Inconsistent Z-order for GlobalDrawer{} with
Controls.Menu{}.
Classification: Frameworks and Libraries
   Product: frameworks-kirigami
   Version: 5.102.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: inbox@willchen.business
CC: notm...@gmail.com
  Target Milestone: Not decided

SUMMARY

When a `GlobalDrawer{}` contains items that open a `Controls.Menu{}` on right
click, and you keep repeatedly right clicking on those items to close and open
that menu, eventually the `GlobalDrawer{}` will seem to gain some kind of focus
and the `Menu{}` will begin to show up underneath the `GlobalDrawer{}` instead
of on top of it.


STEPS TO REPRODUCE

A minimum reproducer and screenshots of the expected and broken behaviour are
provided in the below repository. Check the main commit as well for a clear
view of everything required:

https://invent.kde.org/intralexical/globaldrawerzorder_bug-reproducer

1. Right click on a button in a GlobalDrawer{} that opens a Menu{}.
2. When the Menu{} is open, move your mouse left or up a bit, off of the
Menu{}.
3. Left or right click on either the button or the area around it to close the
Menu{}.
4. Do this repeatedly.


OBSERVED RESULT

5. Eventually, the GlobalDrawer{} will seem to gain focus on click, and move to
on top of the Menu{}.
6. Once this happens, all subsequent times opening the Menu{} will also show it
underneath the drawer.


EXPECTED RESULT

Right-click context menu should always be shown on top of the UI elements it
contextualizes.


SOFTWARE/OS VERSIONS

KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 457504] Add LOONGARCH64/Linux port to Valgrind

[Feiyang Chen]

https://bugs.kde.org/show_bug.cgi?id=457504

--- Comment #9 from Feiyang Chen  ---
Now we can use QEMU 7.2 for testing:
https://github.com/loongson/valgrind-loongarch64/releases/tag/v3.21-GIT

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kirigami] [Bug 465073] GlobalDrawer gets hidden by Esc. even when in non-modal Sidebar mode.

[Will Chen]

https://bugs.kde.org/show_bug.cgi?id=465073

--- Comment #1 from Will Chen  ---
Okay. Looks like this is just the default behaviour of
`Controls.Popup.closePolicy: Popup.CloseOnEscape | Popup.CloseOnPressOutside`,
and setting it to `Popup.NoAutoClose` restores the previous behaviour— Which
presumably was itself actually broken?

https://doc.qt.io/qt-5/qml-qtquick-controls2-popup.html#closePolicy-prop

…Idk. I don't see how this would be caused by the import namespace refactor in
Kirigami, so maybe I also changed something else in the meantime, but I also
have three different builds for different repositories and only one of them
changed.

Either way, this ticket can be closed I think. I will leave it open however in
case anyone else thinks of any applications that might be affected by the
difference.

Also, even currently, the HIG and QT docs both say this: "Pressing the close
button **or anywhere outside of it** collapses it". That is still broken.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kirigami] [Bug 465073] New: GlobalDrawer gets hidden by Esc. even when in non-modal Sidebar mode.

[Will Chen]

https://bugs.kde.org/show_bug.cgi?id=465073

Bug ID: 465073
   Summary: GlobalDrawer gets hidden by Esc. even when in
non-modal Sidebar mode.
Classification: Frameworks and Libraries
   Product: frameworks-kirigami
   Version: 5.102.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: inbox@willchen.business
CC: notm...@gmail.com
  Target Milestone: Not decided

SUMMARY

The GlobalDrawer component can be set to always show as a persistent sidebar of
icons even when collapsed.

This is officially recommended for some Desktop applications in the HIG:

https://develop.kde.org/hig/components/navigation/globaldrawer/#collapsible

However, with a recent change, even when the GlobalDrawer is configured as
such, pressing [Esc.] will still make it disappear completely.

There's a couple problems with this:
- There's no GUI element to completely hide the drawer when it's serving as a
sidebar. So this creates a secret state that can be reached only with the
keyboard.
- The icon-sidebar view is *already* the "collapsed" state when it's set to be
used. A completely hidden state is superfluous.
- Depending on the application, there may not be a way to get the drawer back.


STEPS TO REPRODUCE

1. Open Kirigami Gallery.
2. In the Global Drawer, set the mode to "Collapsible Sidebar Drawer".
3. The drawer should now be a persistent sidebar, similar to the example
described in the HIG.

4. Press [Esc].


OBSERVED RESULT

Oh No! The drawer is gone!

I'm pretty sure this is new/a regression. I've been developing an application
that relies on the sidebar mode pretty heavily, and I would have noticed if
pressing Esc. made my main sidebar disappear every time.


EXPECTED RESULT

The drawer should not disappear when used as a sidebar.


SOFTWARE/OS VERSIONS

KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8


ADDITIONAL INFORMATION

I suspect this may have been introduced in MR #798, as that does touch the
shortcuts and back button, and nothing else has for a couple years.

https://invent.kde.org/frameworks/kirigami/-/merge_requests/798

Separate issue:

I'm pretty sure `enabled: !isMenu` is also new, but the code makes it much
clearer that that's supposed to happen, so I suppose that was broken before.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 457504] Add LOONGARCH64/Linux port to Valgrind

[Feiyang Chen]

https://bugs.kde.org/show_bug.cgi?id=457504

Feiyang Chen  changed:

   What|Removed |Added

Version|3.20 GIT|3.21 GIT

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 457504] Add LOONGARCH64/Linux port to Valgrind

[Feiyang Chen]

https://bugs.kde.org/show_bug.cgi?id=457504

--- Comment #8 from Feiyang Chen  ---
Created attachment 155754
  --> https://bugs.kde.org/attachment.cgi?id=155754=edit
patches-v4

Rebased on a1f365150565e3dd69666ebac85bf535bbe194a1.

Fix build warnings.
Add Ijk_Call and Ijk_Ret support for LoongArch64, which fixes
none/tests/libvexmultiarch_test.
Remove changes and extra test for helgrind tls_threads.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 457504] Add LOONGARCH64/Linux port to Valgrind

[Feiyang Chen]

https://bugs.kde.org/show_bug.cgi?id=457504

--- Comment #7 from Feiyang Chen  ---
(In reply to Paul Floyd from comment #6)
> (In reply to Feiyang Chen from comment #5)
> > > You need to cleanup the new Makefile.am files
> > > 
> > > memcheck/tests/loongarch64-linux/Makefile.am:1: error: filter_stderr.orig 
> > > is
> > > missing in dist_noinst_SCRIPTS
> > I ran make regtest on both amd64-linux and loongarch64-linux, but neither of
> > them reported the makefile consistency error. So I don't know how these
> > errors are generated. Could you help me?
> 
> Sorry, my fault, I didn't look carefully, a lot of them were warnings about
> the artifacts left over after merging the patches.
> 
> If I run  gmake post-regtest-checks then I get
> 
> helgrind/tests/Makefile.am:1: error: tls_threads_tunable.stdout.exp is in
> EXTRA_DIST but doesn't exist
> none/tests/loongarch64/Makefile.am:1: error: atomic.stderr.exp is in
> EXTRA_DIST but doesn't exist
> none/tests/loongarch64/Makefile.am:1: error: branch.stderr.exp is in
> EXTRA_DIST but doesn't exist
> none/tests/loongarch64/Makefile.am:1: error: cpucfg.stderr.exp is in
> EXTRA_DIST but doesn't exist
> none/tests/loongarch64/Makefile.am:1: error: float.stderr.exp is in
> EXTRA_DIST but doesn't exist
> none/tests/loongarch64/Makefile.am:1: error: integer.stderr.exp is in
> EXTRA_DIST but doesn't exist
> none/tests/loongarch64/Makefile.am:1: error: llsc.stderr.exp is in
> EXTRA_DIST but doesn't exist
> none/tests/loongarch64/Makefile.am:1: error: memory.stderr.exp is in
> EXTRA_DIST but doesn't exist
> none/tests/loongarch64/Makefile.am:1: error: move.stderr.exp is in
> EXTRA_DIST but doesn't exist
> none/tests/loongarch64/Makefile.am:1: error: pc.stderr.exp is in EXTRA_DIST
> but doesn't exist
> none/tests/loongarch64/Makefile.am:1: error: special.stderr.exp is in
> EXTRA_DIST but doesn't exist
> 
> The first one might be because I badly resolved merge issues.
> 
> I don't see any stderr.exp referred to in none/tests/loongarch64/Makefile.am

They are empty files and I can find them in my local tree.
I might have forgotten to add them.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 457504] Add LOONGARCH64/Linux port to Valgrind

[Feiyang Chen]

https://bugs.kde.org/show_bug.cgi?id=457504

Feiyang Chen  changed:

   What|Removed |Added

 CC||chenfeiy...@loongson.cn

--- Comment #5 from Feiyang Chen  ---
(In reply to Paul Floyd from comment #4)
> With a build based on 45c61d598f435d59302dea084912cd3390de1ffc
> 
> There was 1 merge rejection:
> ./helgrind/tests/Makefile.am.rej
> due to an extra filter I added
> 

Thank you for your review!

I will remove the changes and extra test for helgrind tls_threads.

> I get a few warnings
> 
> priv/guest_loongarch64_toIR.c:354:23: warning: unused function 'mkU16'
> [-Wunused-function]
> 1 warning generated.
> priv/guest_loongarch64_helpers.c:470:26: warning: shift count >= width of
> type [-Wshift-count-overflow]
> 1 warning generated.
> priv/guest_loongarch64_toIR.c:354:23: warning: unused function 'mkU16'
> [-Wunused-function]
> 1 warning generated.

I will fix these build warnings.

> You need to cleanup the new Makefile.am files
> 
> memcheck/tests/loongarch64-linux/Makefile.am:1: error:
> scalar.stderr.exp.orig is missing in EXTRA_DIST
> memcheck/tests/loongarch64-linux/Makefile.am:1: error: filter_stderr.orig is
> missing in dist_noinst_SCRIPTS
> memcheck/tests/Makefile.am:1: error: leak-segv-jmp.stderr.exp.orig is
> missing in EXTRA_DIST
> helgrind/tests/Makefile.am:1: error: tls_threads_tunable.stderr.exp is
> missing in EXTRA_DIST
> helgrind/tests/Makefile.am:1: error: tls_threads_tunable.stderr.exp.orig is
> missing in EXTRA_DIST
> helgrind/tests/Makefile.am:1: error: tls_threads_tunable.vgtest is missing
> in EXTRA_DIST
> massif/tests/Makefile.am:1: error: big-alloc.post.exp-loongarch64.orig is
> missing in EXTRA_DIST
> none/tests/loongarch64/Makefile.am:1: error: atomic.stdout.exp.orig is
> missing in EXTRA_DIST
> none/tests/loongarch64/Makefile.am:1: error: branch.stdout.exp.orig is
> missing in EXTRA_DIST
> none/tests/loongarch64/Makefile.am:1: error: cpucfg.stdout.exp.orig is
> missing in EXTRA_DIST
> none/tests/loongarch64/Makefile.am:1: error: fault.stderr.exp.orig is
> missing in EXTRA_DIST
> none/tests/loongarch64/Makefile.am:1: error: fault.stdout.exp.orig is
> missing in EXTRA_DIST
> none/tests/loongarch64/Makefile.am:1: error: fault_fp.stderr.exp.orig is
> missing in EXTRA_DIST
> none/tests/loongarch64/Makefile.am:1: error: fault_fp.stdout.exp.orig is
> missing in EXTRA_DIST
> none/tests/loongarch64/Makefile.am:1: error: float.stdout.exp.orig is
> missing in EXTRA_DIST
> none/tests/loongarch64/Makefile.am:1: error: integer.stdout.exp.orig is
> missing in EXTRA_DIST
> none/tests/loongarch64/Makefile.am:1: error: llsc.stdout.exp.orig is missing
> in EXTRA_DIST
> none/tests/loongarch64/Makefile.am:1: error: memory.stdout.exp.orig is
> missing in EXTRA_DIST
> none/tests/loongarch64/Makefile.am:1: error: move.stdout.exp.orig is missing
> in EXTRA_DIST
> none/tests/loongarch64/Makefile.am:1: error: pc.stdout.exp.orig is missing
> in EXTRA_DIST
> none/tests/loongarch64/Makefile.am:1: error: special.stdout.exp.orig is
> missing in EXTRA_DIST
> none/tests/loongarch64/Makefile.am:1: error: filter_stderr.orig is missing
> in dist_noinst_SCRIPTS
> none/tests/loongarch64/Makefile.am:1: error: atomic.stderr.exp is in
> EXTRA_DIST but doesn't exist
> none/tests/loongarch64/Makefile.am:1: error: branch.stderr.exp is in
> EXTRA_DIST but doesn't exist
> none/tests/loongarch64/Makefile.am:1: error: cpucfg.stderr.exp is in
> EXTRA_DIST but doesn't exist
> none/tests/loongarch64/Makefile.am:1: error: float.stderr.exp is in
> EXTRA_DIST but doesn't exist
> none/tests/loongarch64/Makefile.am:1: error: integer.stderr.exp is in
> EXTRA_DIST but doesn't exist
> none/tests/loongarch64/Makefile.am:1: error: llsc.stderr.exp is in
> EXTRA_DIST but doesn't exist
> none/tests/loongarch64/Makefile.am:1: error: memory.stderr.exp is in
> EXTRA_DIST but doesn't exist
> none/tests/loongarch64/Makefile.am:1: error: move.stderr.exp is in
> EXTRA_DIST but doesn't exist
> none/tests/loongarch64/Makefile.am:1: error: pc.stderr.exp is in EXTRA_DIST
> but doesn't exist
> none/tests/loongarch64/Makefile.am:1: error: special.stderr.exp is in
> EXTRA_DIST but doesn't exist
> 

I ran make regtest on both amd64-linux and loongarch64-linux, but neither of
them reported the makefile consistency error. So I don't know how these errors
are generated. Could you help me?

> I don't think that the changes and extra test for helgrind tls_threads are
> still necessary.
> 

I will remove them.

> I get one regtest failure.
> 
> none/tests/libvexmultiarch_test 1 0 0
> 
> Gives me
> vex: priv/host_loongarch64_isel.

[kate] [Bug 463416] New: Can't directly open folders in Kate anymore.

[Will Chen]

https://bugs.kde.org/show_bug.cgi?id=463416

Bug ID: 463416
   Summary: Can't directly open folders in Kate anymore.
Classification: Applications
   Product: kate
   Version: 22.12.0
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: inbox@willchen.business
  Target Milestone: ---

SUMMARY
***
You used to be able to open folders directly in Kate when launching, such as
from Dolphin or from the terminal.

You can't do that anymore.
***


STEPS TO REPRODUCE
`$ kate PathToMyFolder`

Or right click in Dolphin on a directory and "Open Folder With" Kate.


OBSERVED RESULT
Kate opens in the last project folder with which it was used, not the folder
given to it on launch.


EXPECTED RESULT
Kate launches directly with the given folder as the active project.

This is what happens with Kate 22.08.3 from the NixOS 22.11 Nix channel.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: X
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 392164] Button for sharing clipboard content

[Will Chen]

https://bugs.kde.org/show_bug.cgi?id=392164

--- Comment #8 from Will Chen  ---
(In reply to Gerion from comment #6)

> Hmm, interesting thought. If I get it right, this is always equal on both 
> sides, isn't it? I'm really interested in a mode:
> - Share only on request from PC to Smartphone.
> - Share always from Smartphone to PC.
> - (Maybe also: Share always from PC to PC.)

I think I *personally* would probably leave the "Clipboard" plugin disabled and
prefer to use the "Share" plugin even if the former did have such a mode, so as
a single user I suppose I don't agree that there needs to be a separate mode.
Well, Unix philosophy and all that, it just seems like a significant amount of
added complexity for not much gain when the "Share" plugin already does much
the same job.

Because I personally wouldn't use it, I suppose I'm not the best person to
comment on the idea. I do think that having some explicit text sharing
capability is better than having none, though, even if the workflow can be
improved.

> Additionally, what do you think of an extension of the plasmoid?:
> - On the smartphone: Share some text with KDE Connect.

The feature overlap could also create a collision in the UI I think. (Or have I
misunderstood? Is this about Clipboard, or Share?) Currently explicit text
sharing on the smartphone already invokes the "Share" plugin. Would it be
replaced with the "Clipboard" plugin, then? So then will the "Share" plugin's
text feature be exposed at all, or basically just dead code? What if the
"Clipboard" plugin isn't set to that mode, or isn't enabled at all? And
personally I think "Explicit text sharing can be configured in the right
(Clipboard) plugin" would be a subjective UX regression for me from "Explicit
text sharing is available by default with the right (Share) plugin"— That may
be again specific to how I would personally prefer to use KDE Connect though.
Will there be two "KDE Connect" options in the Android sharing menu, one for
the "Share" plugin and one for the "Clipboard" plugin, that do basically the
same thing? — Not unresolvable, but I suppose something that should be thought
about.

> - The plasmoid on the PC pops up, shows: "Text {xy} was shared. How do you 
> want to continue: 1. Copy, 2. Open with program 3. Save to file". For the 
> open with program, maybe some autorecognition works, which opens URLs with a 
> Browser/Gwenview/... where the default is opening with KWrite etc.

Efficiency/steps-wise, I think adding a prompt on PC for what to do would
create mostly the same situation as the current behaviour of popping up KWrite.
You can already Copy/Save/whatever right away as soon as KWrite pops up— I
suppose opening with other programs would be half a step less— Can Gwenview
open web addresses? Or would that only be useful for web browsers?

I do think it would look nicer and make it clearer what's happened though.

> Also, it is possible to share certain part of a text within another app on 
> Android? For example some intresting parts of a chat message. On Android, I 
> would long press on that, choose the interesting part and press copy.

If I understand this correctly, from the menu that says "Copy", there should
also be/is a "Share" option that lets the text be send to KDE Connect, I think.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 431066] kscreen reports doublescan modes at double refresh rate (e.g. 120hz mode on 60hz screen)

[Andrew Chen]

https://bugs.kde.org/show_bug.cgi?id=431066

Andrew Chen  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Andrew Chen  ---
This appears to have been fixed in the latest version

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 457504] Add LOONGARCH64/Linux port to Valgrind

[Feiyang Chen]

https://bugs.kde.org/show_bug.cgi?id=457504

--- Comment #3 from Feiyang Chen  ---
Created attachment 153184
  --> https://bugs.kde.org/attachment.cgi?id=153184=edit
patches-v3

Rebased on 3.20.0.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 457504] Add LOONGARCH64/Linux port to Valgrind

[Feiyang Chen]

https://bugs.kde.org/show_bug.cgi?id=457504

--- Comment #2 from Feiyang Chen  ---
Created attachment 151172
  --> https://bugs.kde.org/attachment.cgi?id=151172=edit
patches-v2

Reorder and merge patches to make things keep building for each separate patch.

- Patches 1-4 add some new IROps, a new IRMBusEvent and a new IRJumpKind to
libVEX.
- Patches 5-6 add the VEX and decode infrastructure for LOONGARCH64.
- Patch 7 enables the LOONGARCH64/Linux target in the build system.

Since then, Valgrind for LOONGARCH64/Linux can be compiled on LoongArch64
Linux, or cross-compiled on other machines.

- Patches 8-21 add support for the libVEX loongarch64 front end.
- Patches 22-76 add support for the libVEX loongarch64 back end.

Since then, libVEX for loongarch64 can translate loongarch64 to loongarch64
properly.

- Patch 77 updates vbit test for loongarch64.
- Patch 78-99 add LOONGARCH64/Linux support for core and tools.
- Patch 100 makes libVEX always use fallback LLSC on loongarch64.

Since then, Vaglrind can run on LOONGARCH64/Linux properly.

-Patch 101-121 implement and add tests for LOONGARCH64/Linux.

Since then, Vaglrind can pass a large number of regression tests on
LOONGARCH64/Linux.

- Patch 122 sets up nightly testing for loongarch64.
- Patch 123 adds a simple README for loongarch64.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 457504] Add LOONGARCH64/Linux port to Valgrind

[Feiyang Chen]

https://bugs.kde.org/show_bug.cgi?id=457504

--- Comment #1 from Feiyang Chen  ---
Here is my system environment:
# uname -a
Linux Sunhaiyong 5.19.0-rc8+ #1 SMP PREEMPT Tue Aug 2 09:25:46 UTC 2022
loongarch64 GNU/Linux
# cat /etc/os-release
NAME="My GNU/Linux System for LoongArch64"
VERSION="6.0"
ID=CLFS4LA64
PRETTY_NAME="My GNU/Linux System for LoongArch64 6.0"
VERSION_CODENAME="Sun Haiyong"

Here are my results:
== 650 tests, 1 stderr failure, 0 stdout failures, 0 stderrB failures, 0
stdoutB failures, 0 post failures ==
drd/tests/pth_mutex_signal   (stderr)

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 457504] Add LOONGARCH64/Linux port to Valgrind

[Feiyang Chen]

https://bugs.kde.org/show_bug.cgi?id=457504

Feiyang Chen  changed:

   What|Removed |Added

 CC||chris.chenfeiy...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 457504] New: Add LOONGARCH64/Linux port to Valgrind

[Feiyang Chen]

https://bugs.kde.org/show_bug.cgi?id=457504

Bug ID: 457504
   Summary: Add LOONGARCH64/Linux port to Valgrind
   Product: valgrind
   Version: 3.20 GIT
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: chris.chenfeiy...@gmail.com
  Target Milestone: ---

Created attachment 151124
  --> https://bugs.kde.org/attachment.cgi?id=151124=edit
patches

LoongArch is a brand-new ISA developed by the Loongson Technology Corporation
Limited, which is a bit like RISC-V. LoongArch includes a reduced 32-bit
version, a standard 32-bit version and a 64-bit version (LoongArch64).
You can find the documentation for LoongArch here:
https://github.com/loongson/LoongArch-Documentation

I am focusing on running Valgrind on LoongArch64/Linux.
I develop Valgrind on the CLFS (Cross Linux From Scratch) distribution.
Later I'll provide a 3A5000 machine for remote connection.

Here is my local tree with all the patches applied:
https://github.com/loongson/valgrind-loongarch64

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 456754] New: "Smart home" card: Couldn't find devices

[Chen X.]

https://bugs.kde.org/show_bug.cgi?id=456754

Bug ID: 456754
   Summary: "Smart home" card: Couldn't find devices
   Product: kdeconnect
   Version: unspecified
  Platform: Android
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: cxplaysgui...@foxmail.com
  Target Milestone: ---

Created attachment 150645
  --> https://bugs.kde.org/attachment.cgi?id=150645=edit
the screenshot

SUMMARY
On my xiaomi phone, set KDE Connect as Smart Home card (maybe called Quick
Access Device Controls on other Android systems). It says "Couldn't find
devices. Add devices in KDE Connect first." even if I had already paired my
phone with PC and Tablet and they connected to the same network.

STEPS TO REPRODUCE
1. add a device in KDE Connect
2. Settings app -> Notifications & Control center -> Select KDE Connect from
the Smart Home dropdown
3. that's it

OBSERVED RESULT
couldn't find devices

EXPECTED RESULT
list added device

SOFTWARE/OS VERSIONS
Windows: 10
Phone: Xiaomi MIUI 13 Android 12
KDE Connect: newest version from Google Play

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 455279] New: vex amd64->IR: unhandled instruction bytes: 0x62 0xD2 0xFD 0x28 0x7C 0xC8 0x62 0xF2 0xFD 0x28

[Feng Chen]

https://bugs.kde.org/show_bug.cgi?id=455279

Bug ID: 455279
   Summary: vex amd64->IR: unhandled instruction bytes: 0x62 0xD2
0xFD 0x28 0x7C 0xC8 0x62 0xF2 0xFD 0x28
   Product: valgrind
   Version: 3.20 GIT
  Platform: RedHat RPMs
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: memcheck
  Assignee: jsew...@acm.org
  Reporter: fchen0...@gmail.com
  Target Milestone: ---

SUMMARY
==182758== Memcheck, a memory error detector
==182758== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==182758== Using Valgrind-3.20.0.GIT and LibVEX; rerun with -h for copyright
info

vex amd64->IR: unhandled instruction bytes: 0x62 0xD2 0xFD 0x28 0x7C 0xC8 0x62
0xF2 0xFD 0x28
vex amd64->IR:   REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR:   VEX=0 VEX.L=0 VEX.n=0x0 ESC=NONE
vex amd64->IR:   PFX.66=0 PFX.F2=0 PFX.F3=0
==182758== valgrind: Unrecognised instruction at address 0x5280f9.


STEPS TO REPRODUCE
1. my specific code compiled on this platform failed to be traced by valgrind
2. The machine is Red Hat Enterprise Linux Server release 6.10 (Santiago)
3. The compiler is mix of gcc9.0 (with dev-toolset9) and icc-2019


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
Red Hat Enterprise Linux Server release 6.10 (Santiago)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 453695] KWin crashed with entering overview mode

[Luofan Chen]

https://bugs.kde.org/show_bug.cgi?id=453695

Luofan Chen  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |---
 Status|NEEDSINFO   |REPORTED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 453695] KWin crashed with entering overview mode

[Luofan Chen]

https://bugs.kde.org/show_bug.cgi?id=453695

--- Comment #5 from Luofan Chen  ---
Created attachment 148803
  --> https://bugs.kde.org/attachment.cgi?id=148803=edit
kwin_wayland crash dump

Sorry, here it is

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 453695] KWin crashed with entering overview mode

[Luofan Chen]

https://bugs.kde.org/show_bug.cgi?id=453695

--- Comment #3 from Luofan Chen  ---
The problems seems to be caused by 1.25x scale. When I change it back to 1x or
2x, everything is OK

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 453695] KWin crashed with entering overview mode

[Luofan Chen]

https://bugs.kde.org/show_bug.cgi?id=453695

--- Comment #2 from Luofan Chen  ---
Created attachment 148758
  --> https://bugs.kde.org/attachment.cgi?id=148758=edit
crash message

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 453695] KWin crashed with entering overview mode

[Luofan Chen]

https://bugs.kde.org/show_bug.cgi?id=453695

--- Comment #1 from Luofan Chen  ---
I am not able to add the coredump attachment, which is larger than the size
limit.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 453695] New: KWin crashed with entering overview mode

[Luofan Chen]

https://bugs.kde.org/show_bug.cgi?id=453695

Bug ID: 453695
   Summary: KWin crashed with entering overview mode
   Product: kwin
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: effects-overview
  Assignee: kwin-bugs-n...@kde.org
  Reporter: clf...@protonmail.com
  Target Milestone: ---

**Description: **

Kwin crashes when I try to enter the virtual desktop overview mode

**Reproduce:**
When I do the following thing on my laptop:

  1. Trying 4 Finger up gesture to enter the overview mode -> crash

Or:

  1. Move mouse to the top left hot-corner -> crash or sometimes enter the
overview
  2. Click on the virtual desktop -> crash

journalctl shows a crash of kwin_wayland.

**Journalctl log:**

```
May 12 18:59:38 bbnarch kwin_wayland[2089]:
file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML
Heading: Binding loop detected for property "verticalAlignment"
May 12 18:59:42 bbnarch kwin_wayland[2089]: ASSERT: "created" in file
/home/main-builder/pkgwork/src/kwin/src/libkwineffects/kwingltexture.cpp, line
129
May 12 18:59:42 bbnarch kernel: kauditd_printk_skb: 1 callbacks suppressed
May 12 18:59:42 bbnarch kernel: audit: type=1701 audit(1652353182.004:229):
auid=1000 uid=1000 gid=1000 ses=3 pid=2089 comm="kwin_wayland"
exe="/usr/bin/kwin_wayland" sig=6 res=1
/systemd" hostname=? addr=? terminal=? res=success'
May 12 18:59:42 bbnarch systemd-coredump[3034]: [] Process 2089 (kwin_wayland)
of user 1000 dumped core.
```

See coredump
[core.kwin_wayland.1000.39512d39c26e42478c6ec31dae803a51.2089.165235318200.zst](/uploads/b942666b79a1be539ab52f79e9546cd4/core.kwin_wayland.1000.39512d39c26e42478c6ec31dae803a51.2089.165235318200.zst)in
the attachment

**Side Note**:

`mutter` is built from source, commit: 654313d46

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 451878] Add support for new syscall memfd_secret

[Di Chen]

https://bugs.kde.org/show_bug.cgi?id=451878

--- Comment #3 from Di Chen  ---
Created attachment 148223
  --> https://bugs.kde.org/attachment.cgi?id=148223=edit
[patch v1] Support new memfd_secret linux syscall (447)

This patch supports memfd_secret across these arches: arm64, amd64(x86_64),
x86(i386) according to this link[1].
This patch does not contain a corresponding test case.

[1] https://marcin.juszkiewicz.com.pl/download/tables/syscalls.html

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 390798] Akonadi EWS failed to authenticate with Exchange Server

[Yaohan Chen]

https://bugs.kde.org/show_bug.cgi?id=390798

--- Comment #28 from Yaohan Chen  ---
I'm still having this problem with kdepim 22.03.80. (After completing OAuth in
the browser popup, the "OK" button in the dialog remains disabled.) Attached
akonadi log of my attempt to create EWS account.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 390798] Akonadi EWS failed to authenticate with Exchange Server

[Yaohan Chen]

https://bugs.kde.org/show_bug.cgi?id=390798

Yaohan Chen  changed:

   What|Removed |Added

 CC||yaohan.c...@gmail.com

--- Comment #27 from Yaohan Chen  ---
Created attachment 147659
  --> https://bugs.kde.org/attachment.cgi?id=147659=edit
Akonadi log when creating an EWS account in kmail

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 398959] Chromebook pen works but does not draw (draws in "Tablet Tester"!)

[Benjamin Chen]

https://bugs.kde.org/show_bug.cgi?id=398959

Benjamin Chen  changed:

   What|Removed |Added

 CC||benjamin920...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 442037] The content items in the toolbar settings picture do not match the items in the description

[bise . chen]

https://bugs.kde.org/show_bug.cgi?id=442037

--- Comment #4 from bise.c...@gmail.com  ---
(In reply to Halla Rempt from comment #3)
> "Local Selection" is still an available action, and Isolate layer is now
> Isolate Active Layer. I think the chance for confusion is pretty minimal?

Sorry, I can’t find them on the UI of Krita. Then I went to the Krita Manual
index and I couldn’t find Local Selection and Isolate Layer. After your
explanation, I finally found Local Selection in the search function of
Ctrl+Ender.

As for the Isolate Layer, as you said, it now becomes the Isolate Active Layer.

But this is also because there is a gap with the current UI and documentation,
so there is no need to modify it?

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 442037] The content items in the toolbar settings picture do not match the items in the description

[bise . chen]

https://bugs.kde.org/show_bug.cgi?id=442037

--- Comment #2 from bise.c...@gmail.com  ---
(In reply to Halla Rempt from comment #1)
> Sorry, but it says "This is just an example of a couple of options that are
> used frequently" -- it shows how it _could_ look after the user has
> reconfigured the toolbar.

I understand what you mean, but there are many items in the description file
that do not appear to exist in the current new version, such as "Local
selection" and "Isolate layer", which will cause confusion for new users to
read the description.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 442037] New: The content items in the toolbar settings picture do not match the items in the description

[bise . chen]

https://bugs.kde.org/show_bug.cgi?id=442037

Bug ID: 442037
   Summary: The content items in the toolbar settings picture do
not match the items in the description
   Product: krita
   Version: 5.0.0-beta1
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Documentation
  Assignee: krita-bugs-n...@kde.org
  Reporter: bise.c...@gmail.com
  Target Milestone: ---

Created attachment 141316
  --> https://bugs.kde.org/attachment.cgi?id=141316=edit
Screenshot image of description page with error

In Krita 5.0 beta 1 toolbar menu, the description pictures are different from
the description items, which will confuse users who read the description. 

Description page screenshot image URL:

https://imgur.com/DlUzm4s

-- 
You are receiving this mail because:
You are watching all bug changes.

[forum.kde.org] [Bug 435445] How to go backwards in a forum?

[Hans Chen]

https://bugs.kde.org/show_bug.cgi?id=435445

Hans Chen  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||hanswc...@gmail.com
 Resolution|--- |NOT A BUG

--- Comment #1 from Hans Chen  ---
You can use the navigation bar at the bottom of the page, see
https://forum.kde.org/tour.php for more information.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 431066] New: kscreen reports doublescan modes at double refresh rate (e.g. 120hz mode on 60hz screen)

[Andrew Chen]

https://bugs.kde.org/show_bug.cgi?id=431066

Bug ID: 431066
   Summary: kscreen reports doublescan modes at double refresh
rate (e.g. 120hz mode on 60hz screen)
   Product: KScreen
   Version: 5.20.4
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: libkscreen
  Assignee: kscreen-bugs-n...@kde.org
  Reporter: and...@xortux.com
  Target Milestone: ---

SUMMARY
KScreen shows a 120hz refresh rate mode on my laptop screen even though it only
supports 60hz. xrandr lists the "120hz" modes as 60hz and DoubleScan.

Similar bug in gnome: https://gitlab.gnome.org/GNOME/mutter/-/issues/275

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
KDE Plasma Version: 5.20.4
KDE Frameworks Version: 5.77.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

$ xrandr --verbose

  1920x1080 (0x48) 138.700MHz +HSync -VSync *current +preferred
h: width  1920 start 1968 end 2000 total 2080 skew0 clock  66.68KHz
v: height 1080 start 1083 end 1088 total    clock  60.02Hz
  1920x1080 (0x49) 356.375MHz -HSync +VSync DoubleScan
h: width  1920 start 2080 end 2288 total 2656 skew0 clock 134.18KHz
v: height 1080 start 1081 end 1084 total 1118   clock  60.01Hz
  1920x1080 (0x4a) 266.500MHz +HSync -VSync DoubleScan
h: width  1920 start 1944 end 1960 total 2000 skew0 clock 133.25KHz
v: height 1080 start 1081 end 1084 total    clock  59.97Hz
  1920x1080 (0x4b) 173.000MHz -HSync +VSync
h: width  1920 start 2048 end 2248 total 2576 skew0 clock  67.16KHz
v: height 1080 start 1083 end 1088 total 1120   clock  59.96Hz
  1920x1080 (0x4c) 138.500MHz +HSync -VSync
h: width  1920 start 1968 end 2000 total 2080 skew0 clock  66.59KHz
v: height 1080 start 1083 end 1088 total    clock  59.93Hz

$ kscreen-console output

Modes: 
 "72"""   QSize(1920, 1080)   60.0204
 "73"""   QSize(1920, 1080)   120.016
 "74"""   QSize(1920, 1080)   119.937
 "75"""   QSize(1920, 1080)   59.9628
 "76"""   QSize(1920, 1080)   59.9339

-- 
You are receiving this mail because:
You are watching all bug changes.

[krunner] [Bug 430951] krunner runs previous result / lower ranked result when enter pressed quickly before search finishes

[Andrew Chen]

https://bugs.kde.org/show_bug.cgi?id=430951

--- Comment #7 from Andrew Chen  ---
(In reply to Alexander Lohnau from comment #6)
> It retains the previous query and this produces the results. If you do not
> like that you can just uncheck the option.

Thank you. I did not see this option before. Now krunner is working pretty well
for me.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krunner] [Bug 430951] krunner runs previous result / lower ranked result when enter pressed quickly before search finishes

[Andrew Chen]

https://bugs.kde.org/show_bug.cgi?id=430951

--- Comment #5 from Andrew Chen  ---
Actually, why does krunner retain the previous result? Perhaps it should clear
the results after executing?

-- 
You are receiving this mail because:
You are watching all bug changes.

[krunner] [Bug 430951] krunner runs previous result / lower ranked result when enter pressed quickly before search finishes

[Andrew Chen]

https://bugs.kde.org/show_bug.cgi?id=430951

--- Comment #4 from Andrew Chen  ---
(In reply to Alexander Lohnau from comment #3)
> >I was thinking that clearing the previous results would at least prevent the 
> >previous results from being run.
> 
> So you mean that when you press enter, have already typed sth. else and a
> previous result is being executed? If I understand that correctly another
> user has reported a similar issue.

Yeah, the search for the new results haven't finished when I press enter fast,
so the previous results are still selected and run. Not sure which bug report
you are referring to, I see Bug 368901 but that seems to be a different issue
(not timing related).

-- 
You are receiving this mail because:
You are watching all bug changes.

[krunner] [Bug 430951] krunner runs previous result / lower ranked result when enter pressed quickly before search finishes

[Andrew Chen]

https://bugs.kde.org/show_bug.cgi?id=430951

--- Comment #2 from Andrew Chen  ---
(In reply to Alexander Lohnau from comment #1)
> >Clear the previous results immediately after typing the first letter
> 
> Not sure what you mean. The results get replaced as you type. Completely
> clearing it would cause the window to jump around even more.

I was thinking that clearing the previous results would at least prevent the
previous results from being run. But yeah the window jumping around is quite
undesirable. Although I'm thinking, if the old results are cleared, and the
runners are searched in order of priority (like applications first), then the
initial top choice will also be the final top choice, so it at least won't run
the wrong thing?

> >A runner for user configurable shortcuts that searches fast
> Not sure what you mean, please elaborate :)

A runner (plugin) module where the user can configure actions for certain
things typed into krunner. For example, I would want to always run dolphin if I
type in 'dol' and pressed enter. The idea is this would be a small list, and
prioritized to be searched first, so it could give results immediately. This
might be a more niche use case, but also might be useful regardless of this
bug, for customized shortcuts to applications that don't always end up as the
first on the list perhaps.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krunner] [Bug 430951] New: krunner runs previous result / lower ranked result when enter pressed quickly before search finishes

[Andrew Chen]

https://bugs.kde.org/show_bug.cgi?id=430951

Bug ID: 430951
   Summary: krunner runs previous result / lower ranked result
when enter pressed quickly before search finishes
   Product: krunner
   Version: 5.20.4
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: alexander.loh...@gmx.de
  Reporter: and...@xortux.com
CC: plasma-b...@kde.org
  Target Milestone: ---

SUMMARY

I use krunner to launch a few very commonly used applications, as a result I
would type alt+space, the first few letters of the name, and enter in quick
succession. Sometimes I hit enter too quick, before the search finishes, it
runs the program I previously run, or some other result I don't expect.

I have observed two behaviors:
1. If I have just the Applications runner enabled, the list would retain the
previous search results until the new search terminates, so enter would run the
previous result
2. If I have other runners enabled, sometimes other runners like Software
Center finds a result faster than the Applications runner, so I have observed
discover being run as it is briefly the top result

STEPS TO REPRODUCE
1. Open krunner
2. Type 'd' and enter in quick succession

OBSERVED RESULT
Previous top result is run

EXPECTED RESULT
Dolphin (first result for 'd') is run

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.20.4
KDE Frameworks Version: 5.77.0
Qt Version: 5.12.2

ADDITIONAL INFORMATION

A few changes that I think could help:

- Wait until the search finishes, or wait a small amount of time, before
processing the enter key
- Clear the previous results immediately after typing the first letter
- A runner for user configurable shortcuts that searches fast

Bug 427672 looks the be related

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 429406] Gmail auth token is not remembered across restarts

[Yaohan Chen]

https://bugs.kde.org/show_bug.cgi?id=429406

Yaohan Chen  changed:

   What|Removed |Added

 CC||yaohan.c...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 428083] Window Rules cannot setting position X/Y value to negative number

[Chen Meng]

https://bugs.kde.org/show_bug.cgi?id=428083

--- Comment #5 from Chen Meng  ---
Thank you everyone!
I'm feeling grateful!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 428083] New: Window Rules cannot setting position X/Y value to negative number

[Chen Meng]

https://bugs.kde.org/show_bug.cgi?id=428083

Bug ID: 428083
   Summary: Window Rules cannot setting position X/Y value to
negative number
   Product: kwin
   Version: 5.19.5
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: rules
  Assignee: kwin-bugs-n...@kde.org
  Reporter: observerc...@gmail.com
  Target Milestone: ---

STEPS TO REPRODUCE
1. Move a Window out of screen
2. Add window rule，try "Detect Window Properties", then you can see position
entry with negative number, chose this.
3. Finally, you will see one of the value from negative number become ZERO.


KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0
Qt Version: 5.15.1


ADDITIONAL INFORMATION

Set a window be out of screen sounds little nuts. 
But GUI Emacs cannot be just fit the screen. 
So I feeling when GUI Emacs window size is bigger than screen is better than
the  small one.

sorry for my funny English.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kile] [Bug 416932] Dead link in File -> Statistics -> Help

[Andrew Chen]

https://bugs.kde.org/show_bug.cgi?id=416932

--- Comment #4 from Andrew Chen  ---
Regarding packaging, I did not install my distro's meta package with all the
kde applications, instead I installed the ones I wanted individually. Probably
not really a bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kile] [Bug 416932] Dead link in File -> Statistics -> Help

[Andrew Chen]

https://bugs.kde.org/show_bug.cgi?id=416932

--- Comment #2 from Andrew Chen  ---
I don't have KHelpcenter installed.

File -> Statistics -> Help takes me to this page:
https://docs.kde.org/index.php?branch=stable5=en_US=kile=/kile/statistics.html

$ ls -l /usr/share/doc/HTML/de/kile/index.docbook
-rw-r--r-- 1 root root 196141 Oct 20 14:19
/usr/share/doc/HTML/de/kile/index.docbook

With KHelpcenter installed it takes me to the right page in KHelpcenter.

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 417337] New: can't quit full screen mode with key Esc?

[teckie chen]

https://bugs.kde.org/show_bug.cgi?id=417337

Bug ID: 417337
   Summary: can't quit full screen mode with key Esc?
   Product: okular
   Version: 1.9.1
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: PDF backend
  Assignee: okular-de...@kde.org
  Reporter: teckie_c...@yahoo.com
  Target Milestone: ---

SUMMARY
when i read my pdf book ,i want to quit full screen mode ,pressing key esc
,there is no respond.

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.

[kile] [Bug 416932] New: Dead link in File -> Statistics -> Help

[Andrew Chen]

https://bugs.kde.org/show_bug.cgi?id=416932

Bug ID: 416932
   Summary: Dead link in File -> Statistics -> Help
   Product: kile
   Version: 2.9.93
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: user interface
  Assignee: michel.lud...@kdemail.net
  Reporter: and...@xortux.com
  Target Milestone: ---

Also in Help -> Kile Handbook

Link goes to page saying "The branch stable5 is not available for the specified
application/language."

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 415425] kde connect slideshow remote crashed

[Cyril Chen]

https://bugs.kde.org/show_bug.cgi?id=415425

Cyril Chen  changed:

   What|Removed |Added

 CC||cyrilchen1...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 415425] kde connect slideshow remote crashed

[Cyril Chen]

https://bugs.kde.org/show_bug.cgi?id=415425

--- Comment #1 from Cyril Chen  ---
Created attachment 124787
  --> https://bugs.kde.org/attachment.cgi?id=124787=edit
New crash information added by DrKonqi

kdeconnectd (1.4.0) using Qt 5.13.2

- What I was doing when the application crashed:
Using the mousepad of remote slid control in KDE Connect App.

-- Backtrace (Reduced):
#6  QScopedPointer
>::operator-> (this=) at
../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:118
[...]
#9  QObject::setProperty (this=this@entry=0x0, name=name@entry=0x7f5c87beff82
"xPos", value=...) at kernel/qobject.cpp:3918
#10 0x7f5c87bef3f1 in PresenterPlugin::receivePacket (this=,
np=...) at ./plugins/presenter/presenterplugin.cpp:107
#11 0x7f5ca97d64d0 in Device::privateReceivedPacket (this=,
np=...) at ./core/device.cpp:411
#12 0x7f5ca6ff19ef in QtPrivate::QSlotObjectBase::call (a=0x7ffe0a661b50,
r=0x557afa0055f0, this=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394

-- 
You are receiving this mail because:
You are watching all bug changes.

[lattedock] [Bug 415333] New: Long pressing on Latte dock icon makes it unusable

[Yaohan Chen]

https://bugs.kde.org/show_bug.cgi?id=415333

Bug ID: 415333
   Summary: Long pressing on Latte dock icon makes it unusable
   Product: lattedock
   Version: 0.9.5
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: plasmoid
  Assignee: mvourla...@gmail.com
  Reporter: yaohan.c...@gmail.com
  Target Milestone: ---

SUMMARY
After long-pressing with mouse on a Latte dock icon, a blue border appears
around the icon, and the icon can no longer be used to switch window or launch
the application.

STEPS TO REPRODUCE
1. Have a Latte dock open
2. Move the mouse cursor over an icon in the dock
3. Hold the mouse down for about a second
4. Try to click on the icon to bring the application to the front or launch it

OBSERVED RESULT
A blue border appears around the icon, and the icon can no longer be used to
switch window or launch the application. It still responds to mouse over and
shows the context menu on right click. The icon is usable again if Latte dock
is restarted.

EXPECTED RESULT
The icon should be usable like normal

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.65.0
Qt Version: 5.14.0

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 413296] Gtk theme broken on new kde 5.17

[Andrew Chen]

https://bugs.kde.org/show_bug.cgi?id=413296

Andrew Chen  changed:

   What|Removed |Added

 CC||xor@gmail.com

--- Comment #1 from Andrew Chen  ---
There should also be a way to override the color scheme, for example, there
should be a way to use light theme for an application when the system is set to
dark theme.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 412214] [Feature request] Revert to breadcrumbs on location bar losing focus

[Hans Chen]

https://bugs.kde.org/show_bug.cgi?id=412214

Hans Chen  changed:

   What|Removed |Added

 CC||hanswc...@gmail.com

--- Comment #1 from Hans Chen  ---
Related report (not sure if it counts as a duplicate, but this report has been
closed): https://bugs.kde.org/show_bug.cgi?id=157593

-- 
You are receiving this mail because:
You are watching all bug changes.

[kio-extras] [Bug 408174] fish:// and sftp:// opens a non-existing folder fish:////

[Shimi Chen]

https://bugs.kde.org/show_bug.cgi?id=408174

Shimi Chen  changed:

   What|Removed |Added

 CC||shimi.c...@gmail.com
Version|18.12.3 |19.08.0
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from Shimi Chen  ---
I can confirm this on Arch Linux using version 19.08.1. It occurs both in Kate
and KWrite, but not in okular or ark.
Steps to reproduce:
1. Using the Kate "Open File" dialog (ctrl+o or File->Open...) open a text file
located on an sftp server.
2. Go to File->Open.. or File->Save As...

Expected result:
The application will open the directory in which the file is saved in order to
select another file in it (or save the file in another name at the same place).

Actual result:
The application attempts to browse the opened file itself as a directory, which
produces an error (as indeed there is no directory with the same name as the
opened file).

Bug 320319 may be related, however it is in Windows.
It seems that this issue already existed around 2016 on linux, but was twice
reported as fixed at that time (bug 352490, comment 2 and bug 363365, comment
2).

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app

[Yaohan Chen]

https://bugs.kde.org/show_bug.cgi?id=404990

Yaohan Chen  changed:

   What|Removed |Added

 CC||yaohan.c...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 409374] You can not enable sub-pixel rendering other than vendor default because system settings will put a check mark in the box to block anti-aliasing and make fonts unreadable

[Yaohan Chen]

https://bugs.kde.org/show_bug.cgi?id=409374

Yaohan Chen  changed:

   What|Removed |Added

 CC||yaohan.c...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-nm] [Bug 409392] NetworkManager widget freezes on connection issues blocking all Plasma

[Andrew Chen]

https://bugs.kde.org/show_bug.cgi?id=409392

Andrew Chen  changed:

   What|Removed |Added

 CC||xor@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 284172] Kmail does not correctly recognize some IMAP-Inbox-Folders

[Yaohan Chen]

https://bugs.kde.org/show_bug.cgi?id=284172

--- Comment #27 from Yaohan Chen  ---
I'm also having this problem with one of my IMAP accounts.

According to this article about MS Outlook, some IMAP servers put all folders
under the Inbox folder. Outlook actually has a "Root Folder" setting, which if
set to Inbox, will make the other folders appear as top level.

https://www.msoutlook.info/question/619

So maybe the nested folder structure is not due to a bug in KMail but just how
the servers behave? It would be nice to have a similar "Root Folder" setting
though, so users can use their IMAP accounts in a consistent way.

I'm not sure if this is related to the problem where Server-Side Subscriptions
must be turned off in order to view emails in the Inbox folder.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 284172] Kmail does not correctly recognize some IMAP-Inbox-Folders

[Yaohan Chen]

https://bugs.kde.org/show_bug.cgi?id=284172

Yaohan Chen  changed:

   What|Removed |Added

 CC||yaohan.c...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-integration] [Bug 374913] Open does not use directory for currently open file with sftp://

[Shimi Chen]

https://bugs.kde.org/show_bug.cgi?id=374913

Shimi Chen  changed:

   What|Removed |Added

 CC||shimi.c...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 399894] "Refresh rate" drop down shows repeated values

[Andrew Chen]

https://bugs.kde.org/show_bug.cgi?id=399894

--- Comment #3 from Andrew Chen  ---
I don't think this is a problem with kde. Your monitor or graphics driver is
listing 60hz twice for some reason.

> 1920x1080 60.00*+  60.0050.0059.94

For comparison, mine shows

> 1920x1080 60.02*+  59.9348.00

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 399894] "Refresh rate" drop down shows repeated values

[Andrew Chen]

https://bugs.kde.org/show_bug.cgi?id=399894

Andrew Chen  changed:

   What|Removed |Added

 CC||andrew.chuanye.chen@gmail.c
   ||om

--- Comment #1 from Andrew Chen  ---
That appears to be a problem with the backend. Can you post the output of
xrandr?

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 349124] Add support for changing qt4 theme in system settings

[Andrew Chen]

https://bugs.kde.org/show_bug.cgi?id=349124

Andrew Chen  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 Status|REPORTED|RESOLVED

--- Comment #1 from Andrew Chen  ---
Now that qt4 has been deprecated for a long time, and there are hardly any apps
that still require it, I feel this feature would not be useful anymore, so I'm
closing this bug report.

-- 
You are receiving this mail because:
You are watching all bug changes.

[klipper] [Bug 399096] New: klipper makes plasma desktop freeze while huge content in clipboard history

[Minwei Chen]

https://bugs.kde.org/show_bug.cgi?id=399096

Bug ID: 399096
   Summary: klipper makes plasma desktop freeze while huge content
in clipboard history
   Product: klipper
   Version: 5.12.4
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: 900...@gmail.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Run desktop env with klipper
2. Copy a huge text content(something like 50Mb)

OBSERVED RESULT
Related process begins occupying 100% of one cpu core and plasma desktop
freezes after a while, restarting session & system won't resolve

EXPECTED RESULT
Copy correctly and auto clean/warning if issue

SOFTWARE VERSIONS
Kubuntu 17.10
KDE Plasma 5.12.4
KDE Framework 5.44.0
Qt 5.9.1
Kernel 4.13.0-38-generic

ADDITIONAL INFORMATION
Manual solution is here :
https://askubuntu.com/questions/1024071/plasmashell-freezes-crashes-once-restarted

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 396269] New: Touchpad settings are changed when another mouse is connected

[Andrew Chen]

https://bugs.kde.org/show_bug.cgi?id=396269

Bug ID: 396269
   Summary: Touchpad settings are changed when another mouse is
connected
   Product: systemsettings
   Version: 5.13.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_mouse
  Assignee: unassigned-b...@kde.org
  Reporter: andrew.chuanye.c...@gmail.com
CC: unassigned-b...@kde.org
  Target Milestone: ---

Steps to reproduce:
1. Enable natural scrolling in system settings -> touchpad
2. Connect a mouse (I used bluetooth, but usb should also work)
3. Observe natural scrolling is no longer active on the touchpad
4. Also the touchpad settings display a warning that active settings don't
match saved settings

I suspect this is caused by kcm_mouse applying the mouse settings to all
pointer devices (including touchpad?) when a new pointer device is connected.

I see
> Initializing  "kcm_mouse" :  "kcminit_mouse"
in the system logs when I connect the mouse.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 388356] New: KDE crashed when application launcher was clicked

[Chen Yifan]

https://bugs.kde.org/show_bug.cgi?id=388356

Bug ID: 388356
   Summary: KDE crashed when application launcher was clicked
   Product: plasmashell
   Version: 5.11.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: xingqibache...@qq.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.11.4)

Qt Version: 5.10.0
Frameworks Version: 5.41.0
Operating System: Linux 4.14.9-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
I clicked the application launcher. I did not see it but plasma crashed.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff99f0e2840 (LWP 4716))]

Thread 12 (Thread 0x7ff8b1d35700 (LWP 5213)):
#0  0x7ff997e6638d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7ff998cad00c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7ff99caee9ca in  () at /usr/lib/libQt5Quick.so.5
#3  0x7ff99caeee54 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7ff998cabb2d in  () at /usr/lib/libQt5Core.so.5
#5  0x7ff997e6008a in start_thread () at /usr/lib/libpthread.so.0
#6  0x7ff9985b342f in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7ff8b3fff700 (LWP 5148)):
#0  0x7ff997e6638d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7ff998cad00c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7ff99caee9ca in  () at /usr/lib/libQt5Quick.so.5
#3  0x7ff99caeee54 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7ff998cabb2d in  () at /usr/lib/libQt5Core.so.5
#5  0x7ff997e6008a in start_thread () at /usr/lib/libpthread.so.0
#6  0x7ff9985b342f in clone () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7ff8b33fe700 (LWP 4946)):
#0  0x7ff9985a8f2b in poll () at /usr/lib/libc.so.6
#1  0x7ff992daaed3 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7ff992daafae in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7ff998ef46b4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7ff998e9682b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7ff998ca678e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7ff998cabb2d in  () at /usr/lib/libQt5Core.so.5
#7  0x7ff997e6008a in start_thread () at /usr/lib/libpthread.so.0
#8  0x7ff9985b342f in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7ff8b9f49700 (LWP 4814)):
#0  0x7ff997e6638d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7ff998cad00c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7ff99caee9ca in  () at /usr/lib/libQt5Quick.so.5
#3  0x7ff99caeee54 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7ff998cabb2d in  () at /usr/lib/libQt5Core.so.5
#5  0x7ff997e6008a in start_thread () at /usr/lib/libpthread.so.0
#6  0x7ff9985b342f in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7ff8c2b46700 (LWP 4813)):
#0  0x7ff9985a8f2b in poll () at /usr/lib/libc.so.6
#1  0x7ff992daaed3 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7ff992daafae in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7ff998ef46b4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7ff998e9682b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7ff998ca678e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7ff8c54f91ba in KCupsConnection::run() () at /usr/lib/libkcupslib.so
#7  0x7ff998cabb2d in  () at /usr/lib/libQt5Core.so.5
#8  0x7ff997e6008a in start_thread () at /usr/lib/libpthread.so.0
#9  0x7ff9985b342f in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7ff8d9316700 (LWP 4812)):
#0  0x7ff997e6638d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7ff998cad00c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7ff99caee9ca in  () at /usr/lib/libQt5Quick.so.5
#3  0x7ff99caeee54 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7ff998cabb2d in  () at /usr/lib/libQt5Core.so.5
#5  0x7ff997e6008a in start_thread () at /usr/lib/libpthread.so.0
#6  0x7ff9985b342f in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7ff8db630700 (LWP 4809)):
#0  0x7ff992dd25f9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7ff992daa77d in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7ff992daadf6 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7ff992daafae in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  

[Breeze] [Bug 386895] dialog-password grossly oversized in gtk3

[Andrew Chen]

https://bugs.kde.org/show_bug.cgi?id=386895

--- Comment #4 from Andrew Chen <andrew.chuanye.c...@gmail.com> ---
@Nate No it doesn't help.

The issue seems to be that the icon is marked as fixed size:

> #64x64 - Fixed size - For dialog icons >!!!ONLY!!!< - 
> DO_NOT_USE_ANYWHERE_ELSE - Color
> [status/64]
> Size=64
> Context=Status
> Type=Fixed

Whereas in Adwaita multiple sizes are provided.

Perhaps we could just make it scalable since it is already a svg?

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 386895] dialog-password grossly oversized in gtk3

[Andrew Chen]

https://bugs.kde.org/show_bug.cgi?id=386895

--- Comment #1 from Andrew Chen <andrew.chuanye.c...@gmail.com> ---
Actually now that I think about it again, maybe the icon should've never been
used in a taskbar in the first place. Although Adwaita's version of this icons
is in-line with the other toolbar icon sizes.

Could you let me know what you think about this. If this is indeed a misuse of
the icon, I'll go file a bug with blueman instead.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 386895] New: dialog-password grossly oversized in gtk3

[Andrew Chen]

https://bugs.kde.org/show_bug.cgi?id=386895

Bug ID: 386895
   Summary: dialog-password grossly oversized in gtk3
   Product: Breeze
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: andrew.chuanye.c...@gmail.com
CC: kain...@gmail.com
  Target Milestone: ---

Created attachment 108856
  --> https://bugs.kde.org/attachment.cgi?id=108856=edit
example screenshot

Gtk3 applications that use the `dialog-password` icon have them displayed much
larger than other icons.

`blueman-manager` is used as an example here. In the screenshot, notice the 3rd
icon from the left in the taskbar.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-qqc2-desktop-style] [Bug 386289] QQC2 Causes QtQuickControls 2.2 Slider to fail to load QML with component version error

[Yaohan Chen]

https://bugs.kde.org/show_bug.cgi?id=386289

Yaohan Chen <yaohan.c...@gmail.com> changed:

   What|Removed |Added

 CC||yaohan.c...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 379749] Crash when saving/closing a PDF with forms

[Andrew Chen]

https://bugs.kde.org/show_bug.cgi?id=379749

Andrew Chen <andrew.chuanye.c...@gmail.com> changed:

   What|Removed |Added

 CC||andrew.chuanye.chen@gmail.c
   ||om

--- Comment #7 from Andrew Chen <andrew.chuanye.c...@gmail.com> ---
Looks like a qt bug to me. The destructor of QSyntaxHighlighter should not emit
a QTextEdit::textChanged signal.

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 317346] Okular overwrites PDF form data without asking

[Andrew Chen]

https://bugs.kde.org/show_bug.cgi?id=317346

Andrew Chen <andrew.chuanye.c...@gmail.com> changed:

   What|Removed |Added

 CC||andrew.chuanye.chen@gmail.c
   ||om

--- Comment #4 from Andrew Chen <andrew.chuanye.c...@gmail.com> ---
Related bugs:
https://bugs.kde.org/show_bug.cgi?id=362996
https://bugs.kde.org/show_bug.cgi?id=267350

In my opinion okular should save form data out of band only for recovery
purposes, and when exiting prompt the user to either save the in the pdf itself
or discard the data.

I'm happy to work on this if no one else is.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 374574] New: Plasma crash

[CHEN Xiangyu]

https://bugs.kde.org/show_bug.cgi?id=374574

Bug ID: 374574
   Summary: Plasma crash
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: xiangyu.c...@aol.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.1.36-41-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
OS: opensuse 42.1.20161207
Description:
When I check the device information, the plasma crash.
Attached the core dump, wish it was helpful.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fee5a0a07c0 (LWP 2020))]

Thread 7 (Thread 0x7fed947dd700 (LWP 2103)):
#0  0x7fee4fc791c0 in  () at /usr/lib64/libglib-2.0.so.0
#1  0x7fee4fc7b44b in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fee4fc7bd80 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fee4fc7bf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fee53ecbd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fee53e72d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fee53c9461a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fed95e29cf7 in KCupsConnection::run() () at
/usr/lib64/libkcupslib.so
#8  0x7fee53c9932f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fee52da80a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7fee535a702d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7fed9700 (LWP 2100)):
#0  0x7fee5359accd in read () at /lib64/libc.so.6
#1  0x7fee4fcbcb60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fee4fc7b999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fee4fc7bdf8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7fee4fc7bf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7fee53ecbd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7fee53e72d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7fee53c9461a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7fee57b44282 in  () at /usr/lib64/libQt5Quick.so.5
#9  0x7fee53c9932f in  () at /usr/lib64/libQt5Core.so.5
#10 0x7fee52da80a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7fee535a702d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7fee27fff700 (LWP 2070)):
#0  0x7fee52dac03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fee5977786b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7fee59777899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7fee52da80a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fee535a702d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7fee2df6f700 (LWP 2064)):
#0  0x7fee4fc7b458 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#1  0x7fee4fc7bd80 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fee4fc7bf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fee53ecbd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fee53e72d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fee53c9461a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fee56fa8e18 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fee53c9932f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fee52da80a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fee535a702d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fee2f6f1700 (LWP 2045)):
#0  0x7fee4fcbd8c1 in g_private_get () at /usr/lib64/libglib-2.0.so.0
#1  0x7fee4fca1400 in g_thread_self () at /usr/lib64/libglib-2.0.so.0
#2  0x7fee4fc7bf6d in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fee53ecbd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fee53e72d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fee53c9461a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fee56fa8e18 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fee53c9932f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fee52da80a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fee535a702d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fee40c22700 (LWP 2044)):
#0  0x7fee5359ebfd in poll () at /lib64/libc.so.6
#1  0x7fee4fc7be64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fee4fc7bf7c in g_main_context_iteration () at

[Akonadi] [Bug 328636] Calendar event isn't syncronized with google calendar after resume from sleep

[Rick W . Chen via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=328636

Rick W. Chen <stuffcor...@archlinux.us> changed:

   What|Removed |Added

 CC|stuffcor...@archlinux.us|

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 322975] desktop render will twisted when the opengl application is closed.

[Rick W . Chen via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=322975

Rick W. Chen <stuffcor...@archlinux.us> changed:

   What|Removed |Added

 CC|stuffcor...@archlinux.us|

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 362647] New: Can't search with Chinese characters

[Ray Chen via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362647

Bug ID: 362647
   Summary: Can't search with Chinese characters
   Product: frameworks-baloo
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: m...@vhanda.in
  Reporter: swy...@gmail.com
CC: pinak.ah...@gmail.com

files are indexed, you can search with English part of filename, But you get
nothing when searching the Chinese part of filename.

Reproducible: Always

Steps to Reproduce:
1.creat some files with Chinese characters, example: touch 測試testcase.txt
測試: means test
2.baloosearch testcase, you can see this file in list
/home/**/test/測試testcase.txt
Elapsed: 0.706571 msecs
3.baloosearch 測試 or baloosearch "測試" you only get 
Elapsed: 0.368735 msecs

Actual Results:  
baloosearch 測試
Elapsed: 0.368735 msecs
can't find my test file

Expected Results:  
should list 測試testcase.txt

this bug affect dolphin search , Desktop search and krunner
so All KF5 system can't search any Chinese characters
may affect Japanese , Korean characters search (maybe, not sure)

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 361179] New: two radio buttons (right handed and left handed) to one check box (switch right/left click)

[Chen Meng via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361179

Bug ID: 361179
   Summary: two radio buttons (right handed and left handed) to
one check box (switch right/left click)
   Product: systemsettings
   Version: 5.6.1
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: kcm_mouse
  Assignee: unassigned-b...@kde.org
  Reporter: observerc...@gmail.com
CC: unassigned-b...@kde.org

Some mouse have already switch right and left keys physically.
So it will be more accurate like the summary title I said. 

Sorry my bad English.

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 360930] New: Plasma crashed after connect to my VPN

[Mike Chen via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360930

Bug ID: 360930
   Summary: Plasma crashed after connect to my VPN
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: kdy...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.1.15-8-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

Just when I enable connect to vpn...then it's crashed !

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4aad9e47c0 (LWP 1519))]

Thread 7 (Thread 0x7f4a8700 (LWP 1531)):
#0  0x7f4aa6eedc8d in read () at /lib64/libc.so.6
#1  0x7f4aa3613b60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f4aa35d2999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f4aa35d2df8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f4aa35d2f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f4aa781cd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f4aa77c3d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f4aa75e561a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f4aaa8f7df8 in  () at /usr/lib64/libQt5Qml.so.5
#9  0x7f4aa75ea32f in  () at /usr/lib64/libQt5Core.so.5
#10 0x7f4aa66fb0a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7f4aa6ef9fed in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f4a83087700 (LWP 1563)):
#0  0x7f4aa6ef1bbd in poll () at /lib64/libc.so.6
#1  0x7f4aa35d2e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f4aa35d2f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f4aa781cd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f4aa77c3d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f4aa75e561a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f4aaa8f7df8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f4aa75ea32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f4aa66fb0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f4aa6ef9fed in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f4a818fb700 (LWP 1567)):
#0  0x7f4aa35d01f2 in  () at /usr/lib64/libglib-2.0.so.0
#1  0x7f4aa35d283f in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f4aa35d2df8 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f4aa35d2f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f4aa781cd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f4aa77c3d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f4aa75e561a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f4aaa8f7df8 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7f4aa75ea32f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f4aa66fb0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f4aa6ef9fed in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f4a7bdf7700 (LWP 1586)):
#0  0x7f4aa66ff03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f4aad0bf86b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f4aad0bf899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f4aa66fb0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f4aa6ef9fed in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f49f3fff700 (LWP 1587)):
#0  0x7f4aa3614cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f4aa35d2028 in g_main_context_release () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f4aa35d2e0e in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f4aa35d2f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f4aa781cd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f4aa77c3d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f4aa75e561a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f4aab491282 in  () at /usr/lib64/libQt5Quick.so.5
#8  0x7f4aa75ea32f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f4aa66fb0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f4aa6ef9fed in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f49ea0e4700 (LWP 1600)):
#0  0x7f4aa3614cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f4aa35d24b9 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f4aa35d2d80 in  () at /usr/lib64/libglib-2.0.so.0
#3  

[dolphin] [Bug 356235] Dolphin unable to change file associations

[Shimi Chen via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356235

--- Comment #5 from Shimi Chen <shimi.c...@gmail.com> ---
Workaround:
rm ~/.config/mimeapps.list

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 359486] New: Plasma crashed when I uninstall a software and drag the link to the recycle bin on the desktop

[Chen Yifan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359486

Bug ID: 359486
   Summary: Plasma crashed when I uninstall a software and drag
the link to the recycle bin on the desktop
   Product: plasmashell
   Version: 5.5.4
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: xingqibache...@qq.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.4)

Qt Version: 5.5.1
Operating System: Linux 4.3.5-300.fc23.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:
I uninstall a software and drag the link to the recycle bin on the desktop

The crash does not seem to be reproducible.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7efdcce5c940 (LWP 2255))]

Thread 8 (Thread 0x7efdacf26700 (LWP 2260)):
#0  0x7efdc483bfdd in poll () at /lib64/libc.so.6
#1  0x7efdcacf2272 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7efdcacf3ee7 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7efdaeeb0da9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7efdc54443de in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7efdc3b7f60a in start_thread () at /lib64/libpthread.so.0
#6  0x7efdc4847a4d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7efda61dc700 (LWP 2322)):
#0  0x7ffcec388bbf in clock_gettime ()
#1  0x7efdc4855cc6 in clock_gettime () at /lib64/libc.so.6
#2  0x7efdc54f4956 in qt_gettime() () at /lib64/libQt5Core.so.5
#3  0x7efdc5679949 in QTimerInfoList::updateCurrentTime() () at
/lib64/libQt5Core.so.5
#4  0x7efdc5679eb5 in QTimerInfoList::timerWait(timespec&) () at
/lib64/libQt5Core.so.5
#5  0x7efdc567b2ae in timerSourcePrepare(_GSource*, int*) () at
/lib64/libQt5Core.so.5
#6  0x7efdbfd5f70d in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#7  0x7efdbfd6009b in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#8  0x7efdbfd6027c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#9  0x7efdc567becb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#10 0x7efdc5622eca in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#11 0x7efdc543f434 in QThread::exec() () at /lib64/libQt5Core.so.5
#12 0x7efdc978a9b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#13 0x7efdc54443de in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#14 0x7efdc3b7f60a in start_thread () at /lib64/libpthread.so.0
#15 0x7efdc4847a4d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7efd9938a700 (LWP 2347)):
#0  0x7ffcec388bbf in clock_gettime ()
#1  0x7efdc4855cc6 in clock_gettime () at /lib64/libc.so.6
#2  0x7efdc54f4956 in qt_gettime() () at /lib64/libQt5Core.so.5
#3  0x7efdc5679949 in QTimerInfoList::updateCurrentTime() () at
/lib64/libQt5Core.so.5
#4  0x7efdc5679eb5 in QTimerInfoList::timerWait(timespec&) () at
/lib64/libQt5Core.so.5
#5  0x7efdc567b2ae in timerSourcePrepare(_GSource*, int*) () at
/lib64/libQt5Core.so.5
#6  0x7efdbfd5f70d in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#7  0x7efdbfd6009b in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#8  0x7efdbfd6027c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#9  0x7efdc567becb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#10 0x7efdc5622eca in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#11 0x7efdc543f434 in QThread::exec() () at /lib64/libQt5Core.so.5
#12 0x7efdc978a9b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#13 0x7efdc54443de in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#14 0x7efdc3b7f60a in start_thread () at /lib64/libpthread.so.0
#15 0x7efdc4847a4d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7efd93879700 (LWP 2366)):
#0  0x7efdc483bfdd in poll () at /lib64/libc.so.6
#1  0x7efdbfd6016c in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7efdbfd6027c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7efdc567becb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7efdc5622eca in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7efdc543f434 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7efdc978a9b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7efdc54443de in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7efdc3b7f60a in start_thread () at /lib64/libpthread.so.0
#9  0x7efdc4847a4d in clone ()