[kwin] [Bug 490140] On X11, pressing alt+shift+r isn't registered in Konsole or Tastenbrett

[zyf0330]

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

--- Comment #9 from zyf0330  ---
I find a common solution.
I write a program to occupy shortcut globally before that app starts, and exit
after it starts.
That app is Feishu.
https://github.com/zyf0330/listen-key-press

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

[kwin] [Bug 490140] On X11, pressing alt+shift+r isn't registered in Konsole or Tastenbrett

[zyf0330]

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

zyf0330  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |NOT A BUG
 Status|NEEDSINFO   |RESOLVED

--- Comment #8 from zyf0330  ---
Thanks

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

[kwin] [Bug 490140] On X11, pressing alt+shift+r isn't registered in Konsole or Tastenbrett

[zyf0330]

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

--- Comment #6 from zyf0330  ---
Hello, thanks for your prompt, I have find the app grabbing this shortcut.
And after learning Xlib development, I know that how to grab shortcut globally.
But I must use that app, and I want to know how to prevent that app to do that.
 I tried XUngrabKey within myself program, it doesn't work.
Can you help me?

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

[kwin] [Bug 490140] On X11, pressing alt+shift+r isn't registered in Konsole or Tastenbrett

[zyf0330]

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

--- Comment #5 from zyf0330  ---
(In reply to cwo from comment #4)
> Do you have a global shortcut set for Alt+Shift+R, or an application that
> listens for this shortcut running? If another application grabs this
> combination, it will not be sent to the application that has focus.

Hi.
I have inspected System Settings Shortcuts and Custom Shortcuts, and there is
no alt+shift+r shortcut binding.
I don't think any application listens for this shortcut too, but how to
troubleshoot it?

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

[kde] [Bug 490140] alt+shift+r doesn't work like other shortcut

[zyf0330]

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

--- Comment #3 from zyf0330  ---
I try it on Wayland, and this problem doesn't appear.

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

[kde] [Bug 490140] alt+shift+r doesn't work like other shortcut

[zyf0330]

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

--- Comment #2 from zyf0330  ---
Created attachment 171597
  --> https://bugs.kde.org/attachment.cgi?id=171597&action=edit
Situation In Keyboard layout viewer

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

[kde] [Bug 490140] alt+shift+r doesn't work like other shortcut

[zyf0330]

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

--- Comment #1 from zyf0330  ---
Created attachment 171596
  --> https://bugs.kde.org/attachment.cgi?id=171596&action=edit
Situation In terminal

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

[kde] [Bug 490140] alt+shift+r doesn't work like other shortcut

[zyf0330]

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

zyf0330  changed:

   What|Removed |Added

 CC||zyf034...@gmail.com

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

[kde] [Bug 490140] New: alt+shift+r doesn't work like other shortcut

[zyf0330]

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

Bug ID: 490140
   Summary: alt+shift+r doesn't work like other shortcut
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: zyf034...@gmail.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
***

SUMMARY
Recently, I find that alt+shift+r shortcut doesn't work anymore. In the
Keyboard layout viewer, alt+shift+r doesn't active corresponding button. 
In the tty which I switch into by press ctrl+alt+F3, alt+shift+r works which
outputs "^[R".

STEPS TO REPRODUCE
1. boot into KDE desktop
2. alt+shift+r doesn't work
3. 

OBSERVED RESULT
Nothing happened when press.

EXPECTED RESULT
Keyboard layout viewer reacts.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 24.04
(available in About System)
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13

ADDITIONAL INFORMATION
I notice that after press alt+shift+r in the System Settings window like
Keyboard, UI elements blink like they are refreshed.

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

[KScreen] [Bug 466149] On Xorg, Plasma's idea of the monitor configuration differs from xrandr's

[zyf0330]

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

--- Comment #19 from zyf0330  ---
(In reply to Tupac from comment #18)
> (In reply to zyf0330 from comment #17)
> > What is your `xrandr` output
> 
> Screen 0: minimum 16 x 16, current 3532 x 1080, maximum 32767 x 32767
> XWAYLAND0 connected 1600x900+0+90 (normal left inverted right x axis y axis)
> 380mm x 210mm
>1600x900  74.89*+
>1152x864  74.82  
>1024x768  74.90  
>800x600   74.91  
>640x480   74.77  
>320x240   73.82  
>1440x900  74.98  
>1280x800  74.93  
>720x480   74.51  
>640x400   74.23  
>320x200   73.70  
>1368x768  74.90  
>1280x720  74.78  
>1024x576  74.80  
>864x486   74.45  
>720x400   74.23  
>640x350   74.53  
> XWAYLAND1 connected 1920x1080+1612+0 (normal left inverted right x axis y
> axis) 530mm x 300mm
>1920x1080 74.91*+
>1440x1080 74.92  
>1400x1050 74.87  
>1280x1024 74.90  
>1280x960  74.86  
>1152x864  74.82  
>1024x768  74.90  
>800x600   74.91  
>640x480   74.77  
>320x240   73.82  
>1680x1050 74.89  
>1440x900  74.98  
>1280x800  74.93  
>720x480   74.51  
>640x400   74.23  
>320x200   73.70  
>1600x900  74.89  
>1368x768  74.90  
>1280x720  74.78  
>1024x576  74.80  
>864x486   74.45  
>720x400   74.23  
>640x350   74.53

It seems that, screen number is opposite in the Wayland to Xserver.

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

[KScreen] [Bug 466149] On Xorg, Plasma's idea of the monitor configuration differs from xrandr's

[zyf0330]

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

--- Comment #17 from zyf0330  ---
(In reply to Tupac from comment #16)
> I still have this problem on Fedora 38 with 5.27.5 (Zawertun copr).
> My main monitor in the kde conf is the right (➡️) one but xrandr thinks it's
> the left (⬅️) one, so the relevant apps open in the wrong monitor. 
> Noted this is from a fresh Fedora install so I only had 5.27.4 and 2.27.5 if
> that's any relevant.

What is your `xrandr` output

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

[kdeconnect] [Bug 461083] KDE Connect doesn't reconnect to device after powering the PC on

[zyf0330]

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

zyf0330  changed:

   What|Removed |Added

 CC||zyf034...@gmail.com
 Resolution|FIXED   |---
 Status|RESOLVED|REPORTED

--- Comment #6 from zyf0330  ---
I never meet this problem on the Linux platform. But I always meet this problem
on Windows platform, it have been several years, from daily-built exe to
Windows Store App.

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

[kdeconnect] [Bug 466285] Click the notification popup button doesn't work

[zyf0330]

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

zyf0330  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #6 from zyf0330  ---
I don't know what is updated or changed, but this problem has gone.

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

[KScreen] [Bug 466149] On Xorg, Plasma's idea of the monitor configuration differs from xrandr's

[zyf0330]

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

--- Comment #14 from zyf0330  ---
Hello, when can I receive plasma 5.27.5 update on Ubuntu?
It was supposed to have been released on May 9, wasn't it?

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

[plasmashell] [Bug 469090] After screen is dim or switch off, primary becomes laptop internal monitor.

[zyf0330]

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

--- Comment #8 from zyf0330  ---
Created attachment 159062
  --> https://bugs.kde.org/attachment.cgi?id=159062&action=edit
Tilix Quake monitor setting

Another thing, I have set Tilix Quake to display on Primary Monitor. And after
this problem appears, Tilix Quake window appears on laptop monitor which is set
as non-primary monitor.
And if I set it to display on Monitor 0, it still displays on laptop monitor.
If I set as Monitor 1, it displays on external primary monitor.

So I can guess that when this problem occurs, monitor 0 and 1 is swapped.

This is config in the .config/plasmashellrc.
```
[ScreenConnectors]
0=HDMI-A-0
1=eDP
```

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

[plasmashell] [Bug 469090] After screen is dim or switch off, primary becomes laptop internal monitor.

[zyf0330]

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

--- Comment #7 from zyf0330  ---
This is xrandr output
```
Screen 0: minimum 320 x 200, current 4480 x 1440, maximum 16384 x 16384
eDP connected primary 1920x1200+0+120 (normal left inverted right x axis y
axis) 301mm x 188mm
   2880x1800 90.01 +
   1920x1200 90.01* 
   1920x1080 90.01  
   1600x1200 90.01  
   1680x1050 90.01  
   1280x1024 90.01  
   1440x900  90.01  
   1280x800  90.01  
   1280x720  90.01  
   1024x768  90.01  
   800x600   90.01  
   640x480   90.01  
HDMI-A-0 connected 2560x1440+1920+0 (normal left inverted right x axis y axis)
597mm x 336mm
   2560x1440 59.95*+
   1920x1200 59.95  
   1920x1080 60.0050.0059.94  
   1600x1200 59.95  
   1280x1440 59.91  
   1680x1050 59.88  
   1280x1024 75.0260.02  
   1440x900  59.90  
   1280x960  60.00  
   1280x800  59.95  
   1280x720  60.0050.0059.94  
   1024x768  75.0370.0760.00  
   832x624   74.55  
   800x600   72.1975.0060.3256.25  
   720x576   50.00  
   720x480   60.0059.94  
   640x480   75.0072.8166.6760.0059.94  
   720x400   70.08  
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1 disconnected (normal left inverted right x axis y axis)
DisplayPort-2 disconnected (normal left inverted right x axis y axis)
DisplayPort-3 disconnected (normal left inverted right x axis y axis)
DisplayPort-4 disconnected (normal left inverted right x axis y axis)
DisplayPort-5 disconnected (normal left inverted right x axis y axis)
DisplayPort-6 disconnected (normal left inverted right x axis y axis)
```

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

[kwin] [Bug 469828] New: Plasmashell crash when set window rule for KAlarm alert Message window

[zyf0330]

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

Bug ID: 469828
   Summary: Plasmashell crash when set window rule for KAlarm
alert Message window
Classification: Plasma
   Product: kwin
   Version: 5.27.4
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: zyf034...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.27.4)

Qt Version: 5.15.8
Frameworks Version: 5.104.0
Operating System: Linux 6.2.0-20-generic x86_64
Windowing System: X11
Distribution: Ubuntu 23.04
DrKonqi: 5.27.4 [KCrashBackend]

-- Information about the crash:
I set for Message window to force placed at screen 0, and plasmashell crashs

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault

[KCrash Handler]
#4  0x7f64478eb1b5 in KWin::Window::finishCompositing(KWin::ReleaseReason)
() at /lib/x86_64-linux-gnu/libkwin.so.5
#5  0x7f64477bf7c5 in KWin::Compositor::stop() () at
/lib/x86_64-linux-gnu/libkwin.so.5
#6  0x7f64477b83e7 in KWin::Compositor::reinitialize() () at
/lib/x86_64-linux-gnu/libkwin.so.5
#7  0x7f6445ef39af in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f644790a812 in KWin::Workspace::slotReconfigure() () at
/lib/x86_64-linux-gnu/libkwin.so.5
#9  0x7f6445ef39af in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f6445ef798e in QTimer::timeout(QTimer::QPrivateSignal) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f6445ee7bf5 in QObject::event(QEvent*) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f644536bf92 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x7f6445ebae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f6445f14201 in QTimerInfoList::activateTimers() () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7f6445f14b34 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7f64437d349d in g_main_context_dispatch () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x7f644382e178 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x7f64437d21b0 in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x7f6445f14e7a in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7f6445eb97cb in
QEventLoop::exec(QFlags) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x7f6445ec1c1a in QCoreApplication::exec() () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x55fc4ce4fb65 in  ()
#23 0x7f6444a23a90 in __libc_start_call_main
(main=main@entry=0x55fc4ce4f500, argc=argc@entry=3,
argv=argv@entry=0x7ffdfcbc44b8) at ../sysdeps/nptl/libc_start_call_main.h:58
#24 0x7f6444a23b49 in __libc_start_main_impl (main=0x55fc4ce4f500, argc=3,
argv=0x7ffdfcbc44b8, init=, fini=,
rtld_fini=, stack_end=0x7ffdfcbc44a8) at ../csu/libc-start.c:360
#25 0x55fc4ce50fd5 in  ()
[Inferior 1 (process 942554) detached]

Reported using DrKonqi

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

[plasmashell] [Bug 469090] After screen is dim or switch off, primary becomes laptop internal monitor.

[zyf0330]

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

--- Comment #6 from zyf0330  ---
I forgot to mention one thing. I have create a window rule to force KRunner is
placed at screen 0.

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

[plasmashell] [Bug 469090] After screen is dim or switch off, primary becomes laptop internal monitor.

[zyf0330]

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

--- Comment #4 from zyf0330  ---
Created attachment 158760
  --> https://bugs.kde.org/attachment.cgi?id=158760&action=edit
kscreen-doctor -o output

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

[kdeconnect] [Bug 466285] Click the notification popup button doesn't work

[zyf0330]

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

--- Comment #5 from zyf0330  ---
After first boot into system, this problem doesn't exists.
And after execute `plasmashell --replace`, this problem appears.
This is log after execute `plasmashell --replace`

```
Omitting both --window and --windowclass arguments is not recommended
Checking screens: available: (QScreen(0x55cd4857a9a0, name="HDMI-A-0"),
QScreen(0x55cd4857aa90, name="eDP")) redundant: QHash() fake: QSet() all:
(QScreen(0x55cd4857a9a0, name="HDMI-A-0"), QScreen(0x55cd4857aa90, name="eDP"))
QObject::connect: No such slot DesktopProtocol::_k_slotRedirection(KIO::Job *,
QUrl)
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:534:9:
QML Label: Binding loop detected for property "height"
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:499:13:
QML Label: Binding loop detected for property "height"
Using KRun from QML is deprecated (since 5.88). Use Qt.openUrlExternally, or
the KIO::OpenUrlJob/KIO::ApplicationLauncherJob classes from C++ instead.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Trying to use rootObject before initialization is completed, whilst using
setInitializationDelayed. Forcing completion
Trying to use rootObject before initialization is completed, whilst using
setInitializationDelayed. Forcing completion
QFont::setPointSizeF: Point size <= 0 (0.00), must be greater than 0
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Cyclic dependency detected between
"file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml"
and
"file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/ThumbnailStrip.qml"
Cyclic dependency detected between
"file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml"
and
"file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationHeader.qml"
file:///usr/share/plasma/plasmoids/org.kde.plasma.networkmanagement/contents/ui/main.qml:95:
TypeError: Cannot read property 'airplaneModeAvailable' of null
QFont::setPointSizeF: Point size <= 0 (0.00), must be greater than 0
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both p

[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update

[zyf0330]

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

zyf0330  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |---
 Status|RESOLVED|REPORTED

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

[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update

[zyf0330]

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

zyf0330  changed:

   What|Removed |Added

 CC||zyf034...@gmail.com

--- Comment #41 from zyf0330  ---
https://bugs.kde.org/show_bug.cgi?id=466285
Is this a similar issue?

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

[plasmashell] [Bug 469090] After screen is dim or switch off, primary becomes laptop internal monitor.

[zyf0330]

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

--- Comment #2 from zyf0330  ---
These two screens work normally for everything, just the primary screen is
switched to another one.

On Sat, Apr 29, 2023, 02:58 Nate Graham  wrote:

> https://bugs.kde.org/show_bug.cgi?id=469090
>
> Nate Graham  changed:
>
>What|Removed |Added
>
> 
>  Status|REPORTED|NEEDSINFO
>  CC||n...@kde.org
>  Resolution|--- |WAITINGFORINFO
>
> --- Comment #1 from Nate Graham  ---
> When this happens, can you move the mouse pointer onto the area the
> disabled
> screen occupied? Or is it stuck on the laptop screen?
>
> When this happens, can you run `kscreen-doctor -o` in a terminal window and
> paste the output?
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[plasmashell] [Bug 469090] New: After screen is dim or switch off, primary becomes laptop internal monitor.

[zyf0330]

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

Bug ID: 469090
   Summary: After screen is dim or  switch off, primary becomes
laptop internal monitor.
Classification: Plasma
   Product: plasmashell
   Version: 5.27.4
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: generic-multiscreen
  Assignee: plasma-b...@kde.org
  Reporter: zyf034...@gmail.com
CC: aleix...@kde.org, notm...@gmail.com
  Target Milestone: 1.0

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

My laptop has dual-monitors, one is laptop internal monitor, one is external
monitor connected by HDMI as primary screen.
I set dim and switch off strategy in the Advanced Power Settings. And after
lunch break in which I doesn't touch my laptop, when I use laptop, I find that
krunner appears at the internal monitor screen, and popup window of WebStorm
appears at the internal monitor screen too.
I check Display Configuration, and primariy monitor setting is still external
monitor. And I must change it to internal monitor and apply and then change
back to external monitor and apply, to make krunner and popup window appearing
at the external monitor.

STEPS TO REPRODUCE
1. not be sure how to into this situation

OBSERVED RESULT
The krunner and popup window of WebStorm appear at the laptop internal monitor
screen, which is not primary screen.

EXPECTED RESULT
The krunner and popup window of WebStorm appear at the external HDMI connected
monitor screen, which is primary screen by Display Configuration Setting.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Ubuntu with KDE
(available in About System)
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
use X11

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

[kdeconnect] [Bug 466285] Click the notification popup button doesn't work

[zyf0330]

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

--- Comment #4 from zyf0330  ---
I see this error info when execute `notify-send alert -A button=button` after
execute `plasmashell --replace`

```
Could not find the Plasmoid for Plasma::FrameSvgItem(0x5568590eb530)
QQmlContext(0x556857a54ef0)
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
```

This file is exist.

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

[kdeconnect] [Bug 466285] Click the notification popup button doesn't work

[zyf0330]

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

--- Comment #3 from zyf0330  ---
I don't know if it is true. It seems that after execute `kwin --replace` this
problem appears.

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

[kdeconnect] [Bug 466285] Click the notification popup button doesn't work

[zyf0330]

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

zyf0330  changed:

   What|Removed |Added

 CC||zyf034...@gmail.com

--- Comment #2 from zyf0330  ---
Created attachment 156663
  --> https://bugs.kde.org/attachment.cgi?id=156663&action=edit
demo

I don't think this problem is related to kdeconnect, at least part of.
Please see my attachment video.
I use `notify-send` to show a notification with a button. When I click button,
notify-send should exit and print button, but it doesn't. And when I click
notification, it blinks and hide.

This problem doesn't exist when I boot into Ubuntu. But after some time, it
occurs. I don't know what happened.

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

[kwin] [Bug 444243] On X11, Notifications disappear below current window on click

[zyf0330]

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

zyf0330  changed:

   What|Removed |Added

 Status|CONFIRMED   |REPORTED
 Ever confirmed|1   |0

--- Comment #18 from zyf0330  ---
(In reply to zyf0330 from comment #17)
> Created attachment 155759 [details]
> notification disappears
> 
> I meet this problem too.

It seems this problem is gone.

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

[frameworks-knotifications] [Bug 466285] Click the notification popup button doesn't work

[zyf0330]

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

--- Comment #1 from zyf0330  ---
related to https://bugs.kde.org/show_bug.cgi?id=444243

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

[frameworks-knotifications] [Bug 466285] New: Click the notification popup button doesn't work

[zyf0330]

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

Bug ID: 466285
   Summary: Click the notification popup button doesn't work
Classification: Frameworks and Libraries
   Product: frameworks-knotifications
   Version: 5.98.0
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: zyf034...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

Created attachment 156629
  --> https://bugs.kde.org/attachment.cgi?id=156629&action=edit
demo

SUMMARY 
The KdeConnect app displays a popup box for Android app notifications, but it
does not respond when the button in the popup is clicked.


STEPS TO REPRODUCE
1. there is a notification from KDEConnect
2. click button

OBSERVED RESULT
Nothing happened.

EXPECTED RESULT
The action related to button is executed, and notification popup diesappears.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 22.10
KDE Plasma Version: 5.25.5
KDE Frameworks Version:  5.98.0
Qt Version: 5.15.6

ADDITIONAL INFORMATION

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

[kwin] [Bug 444243] On X11, Notifications disappear below current window on click

[zyf0330]

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

zyf0330  changed:

   What|Removed |Added

 CC||zyf034...@gmail.com

--- Comment #17 from zyf0330  ---
Created attachment 155759
  --> https://bugs.kde.org/attachment.cgi?id=155759&action=edit
notification disappears

I meet this problem too.

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

[yakuake] [Bug 392081] white line appears intervally

[zyf0330]

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

zyf0330  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

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

[yakuake] [Bug 392081] white line appears intervally

[zyf0330]

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

zyf0330  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED

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

[kde] [Bug 461931] New: After resume from hibernate or sleep, Xorg process uses high cpu

[zyf0330]

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

Bug ID: 461931
   Summary: After resume from hibernate or sleep, Xorg process
uses high cpu
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: zyf034...@gmail.com
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. hibernate
2. wake up after one night

OBSERVED RESULT
Xorg use about 30% cpu, and UI lags a little.

EXPECTED RESULT
Normally, Xorg should use 3-7% cpu.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 22.10
(available in About System)
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6

ADDITIONAL INFORMATION
After upgrade from Ubuntu 22.04 to 22.10, this problem occurs.
And, after call `kwin --replace`, Xorg cpu usage is back to normal.

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

[xdg-desktop-portal-kde] [Bug 459204] Invalid zip file causes Open File dialog window freezes

[zyf0330]

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

--- Comment #2 from zyf0330  ---
I install Chrome using apt.
I cannot reproduce using Chrome too, but I find logs at the time.
```
xdg-desktop-portal-kde[5507]: xdp-kde-file-chooser: OpenFile called with
parameters:
xdg-desktop-portal-kde[5507]: xdp-kde-file-chooser: handle: 
"/org/freedesktop/portal/desktop/request/1_7823/handle_5"
xdg-desktop-portal-kde[5507]: xdp-kde-file-chooser: parent_window: 
"x11:0x2a000b8"
xdg-desktop-portal-kde[5507]: xdp-kde-file-chooser: title:  "Open Files"
xdg-desktop-portal-kde[5507]: xdp-kde-file-chooser: options: 
QMap(("filters", QVariant(QDBusArgument, ))("multiple", QVariant(bool, true)))
xdg-desktop-portal-kde[5507]: KCrash: crashing... crashRecursionCounter = 2
xdg-desktop-portal-kde[5507]: KCrash: Application Name = xdg-desktop-portal-kde
path = /usr/lib/x86_64-linux-gnu/libexec pid = 5507
xdg-desktop-portal-kde[5507]: KCrash: Arguments:
/usr/lib/x86_64-linux-gnu/libexec/xdg-desktop-portal-kde
xdg-desktop-portal-kde[5507]: KCrash: Attempting to start
/usr/lib/x86_64-linux-gnu/libexec/drkonqi
xdg-desktop-portal-kde[5507]: Unable to start Dr. Konqi
xdg-desktop-portal-kde[5507]: Re-raising signal for core dump handling.
xdg-desktop-por[5456]: Backend call failed: Message recipient disconnected from
message bus without replying


systemd[3323]: plasma-xdg-desktop-portal-kde.service: Main process exited,
code=killed, status=11/SEGV
systemd[3323]: plasma-xdg-desktop-portal-kde.service: Failed with result
'signal'.
systemd[3323]: plasma-xdg-desktop-portal-kde.service: Consumed 1min 1.959s CPU
time.

```

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

[xdg-desktop-portal-kde] [Bug 459204] New: Invalid zip file causes Open File dialog window freezes

[zyf0330]

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

Bug ID: 459204
   Summary: Invalid zip file causes Open File dialog window
freezes
   Product: xdg-desktop-portal-kde
   Version: 5.24.6
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: zyf034...@gmail.com
CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. `touch foo.zip` in the directory A
2. In Chrome browser, open Open File Dialog to pick file, and enter directory A
3. Single click foo.zip

OBSERVED RESULT
Open File Dialog window freezes

EXPECTED RESULT
nothing happens

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Ubuntu 22.04
(available in About System)
KDE Plasma Version: 5.24.6
KDE Frameworks Version: 5.24.6
Qt Version: 

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 435113] certain mouse settings resets after restart/resume from suspend/dock/undock

[zyf0330]

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

zyf0330  changed:

   What|Removed |Added

 CC||zyf034...@gmail.com

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

[kdeconnect] [Bug 442967] Cannot share file between phone And computer

[zyf0330]

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

zyf0330  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #13 from zyf0330  ---
Anyway, the original isue is resolved.

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

[kdeconnect] [Bug 442967] Cannot share file between phone And computer

[zyf0330]

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

--- Comment #12 from zyf0330  ---
(In reply to Alban BROWAEYS from comment #10)
> Sorry I am lost. Do you mean you tried to set download folder as and
> authorize it i. "Share and receive".
> I only talked about "Filesystem Expose" because it is the only area where I
> jave issue with kdeconnect (and only on Android 11, 10 is fine).
> To send from or to the phone this is not related. Only authorize in "Share
> and receive" does.
> Do you mean you the authorize access button at the bottom is greyed out when
> you select the download folder in "Share and receive" folder location ?

Sorry. I read it wrong.
I mean Download is grayed out in Filesystem expose.

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

[kdeconnect] [Bug 442967] Cannot share file between phone And computer

[zyf0330]

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

--- Comment #11 from zyf0330  ---
(In reply to Alban BROWAEYS from comment #10)
> Sorry I am lost. Do you mean you tried to set download folder as and
> authorize it i. "Share and receive".
> I only talked about "Filesystem Expose" because it is the only area where I
> jave issue with kdeconnect (and only on Android 11, 10 is fine).
> To send from or to the phone this is not related. Only authorize in "Share
> and receive" does.
> Do you mean you the authorize access button at the bottom is greyed out when
> you select the download folder in "Share and receive" folder location ?

Yes

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

[kdeconnect] [Bug 442967] Cannot share file between phone And computer

[zyf0330]

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

--- Comment #9 from zyf0330  ---
At now, I can send files from android phone to Ubuntu successfully. And I don't
need to do filesystem expose.
I think Filesystem expose is needed for browser files in the phone from
computer. And I don't know why I cannot set Download folder as storage
location, just folders inside Download.

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

[kwin] [Bug 426412] Kwin laggy after pausing and un-pausing compositing

[zyf0330]

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

--- Comment #12 from zyf0330  ---
I just have one Intel integrated GPU card, and choose to use OpenGL backend is
laggy, switch to Xrender is smooth. Once I switch to OpenGL 3.1 or 2.0 in
compositor, screen is laggy.

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

[kwin] [Bug 426412] Kwin laggy after pausing and un-pausing compositing

[zyf0330]

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

zyf0330  changed:

   What|Removed |Added

 CC||zyf034...@gmail.com

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

[plasmashell] [Bug 425271] XembedSNIProxy causes "high" cpu usage

[zyf0330]

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

--- Comment #40 from zyf0330  ---
(In reply to zyf0330 from comment #38)
> Created attachment 145829 [details]
> Compositor settings
> 
> I use Ubuntu 21.10 with KDE Plasma, and SDDM compositor whose settings is in
> attachment.
> 
> After do that workground, there are three tray icons appearing in separate
> window. They are emojione-picker, xpad, wine.

It is weired, I try to retry but this problem disappears.
I try to disable all these three applications autostart, and enable one by one,
at the same time I switch Render Backend between OpenGL 3.1 and Xrender, but
XembedSNIProxy doesn't use high cpu every reboot. AND, I resume all these
settings, this problem doesn't appear too!

The only variable is, I changed kernel version from 5.13.0-22-generic to
5.13.0-27-generic before do this. But switch Render Backend to OpenGL is still
lag, unless I set OpenGL and reboot and doesn't touch Compositor settings.

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

[plasmashell] [Bug 425271] XembedSNIProxy causes "high" cpu usage

[zyf0330]

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

--- Comment #39 from zyf0330  ---
Another related thing is, after change compositor settings (when use OpenGL 3.1
or OpenGL 2.0) and apply, the whole screen is lag, except I use Xrender. My
previous computer has no this problem, current computer is too old which is MSI
GE60 2PG. So Maybe it is a hardware compatibility problem.

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

[plasmashell] [Bug 425271] XembedSNIProxy causes "high" cpu usage

[zyf0330]

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

--- Comment #38 from zyf0330  ---
Created attachment 145829
  --> https://bugs.kde.org/attachment.cgi?id=145829&action=edit
Compositor settings

I use Ubuntu 21.10 with KDE Plasma, and SDDM compositor whose settings is in
attachment.

After do that workground, there are three tray icons appearing in separate
window. They are emojione-picker, xpad, wine.

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

[plasmashell] [Bug 425271] XembedSNIProxy causes "high" cpu usage

[zyf0330]

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

--- Comment #36 from zyf0330  ---
I have this problem too. And I must kill xembedsniproxy. After xembedsniproxy
is killed, nothing happens but some windows start to have a white thin border.

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

[plasmashell] [Bug 425271] XembedSNIProxy causes "high" cpu usage

[zyf0330]

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

zyf0330  changed:

   What|Removed |Added

 CC||zyf034...@gmail.com

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

[kdeconnect] [Bug 442967] Cannot share file between phone And computer

[zyf0330]

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

--- Comment #5 from zyf0330  ---
(In reply to lpcornel from comment #4)

> The version referenced (8.8p1-1) is for openssh (in Arch), not kdeconnect.
> kdeconnect has not been revised to be compatible with the new version of
> openssh. I don't know what version of openssh applies to Ubuntu.

Sorry, I misunderstand. I use Ubuntu 21.04 and my openssl version is 8.4p1-5

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

[kwin] [Bug 443002] KWin crash when manually disable laptop screen

[zyf0330]

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

--- Comment #2 from zyf0330  ---
Thanks for your reply!
So how could I upgrade my plasmashell, wait for new version or use KDE neon
ppa?

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

[kdeconnect] [Bug 442967] Cannot share file between phone And computer

[zyf0330]

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

--- Comment #2 from zyf0330  ---
(In reply to lpcornel from comment #1)
> Confirmed. Flagged out of date at
> https://archlinux.org/packages/extra/x86_64/kdeconnect/
> 
> Upgrade of openssh (8.7p1-2 -> 8.8p1-1) causes kdeconnect to fail connect.

But why kdeconnect on Ubuntu is still 20.12.3

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

[kwin] [Bug 443002] New: KWin crash when manually disable laptop screen

[zyf0330]

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

Bug ID: 443002
   Summary: KWin crash when manually disable laptop screen
   Product: kwin
   Version: 5.21.5
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: zyf034...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.21.5)

Qt Version: 5.15.2
Frameworks Version: 5.81.0
Operating System: Linux 5.11.0-36-generic x86_64
Windowing System: X11
Drkonqi Version: 5.21.5
Distribution: Ubuntu 21.04

-- Information about the crash:
- What I was doing when the application crashed:
disable laptop screen in Display Configuration
- Unusual behavior I noticed:
Before disable, I apply Window Rules and UI lags, so I disable laptop screen
and re-enable it, then UI lag disappears.
- Custom settings of the application:

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault

[KCrash Handler]
#4  0x7fc1a263e9c9 in KWin::Workspace::constrainedStackingOrder() () at
/lib/x86_64-linux-gnu/libkwin.so.5
#5  0x7fc1a26342e0 in KWin::Workspace::updateStackingOrder(bool) () at
/lib/x86_64-linux-gnu/libkwin.so.5
#6  0x7fc1a27059b1 in KWin::X11Client::setFrameGeometry(QRect const&,
KWin::AbstractClient::ForceGeometry_t) () at /lib/x86_64-linux-gnu/libkwin.so.5
#7  0x7fc1a258f14b in KWin::AbstractClient::qt_metacall(QMetaObject::Call,
int, void**) () at /lib/x86_64-linux-gnu/libkwin.so.5
#8  0x7fc1a25aab6a in KWin::X11Client::qt_metacall(QMetaObject::Call, int,
void**) () at /lib/x86_64-linux-gnu/libkwin.so.5
#9  0x7fc19fa61c01 in QQmlPropertyPrivate::write(QObject*, QQmlPropertyData
const&, QVariant const&, QQmlContextData*, QFlags)
() at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#10 0x7fc19f98c1fb in
QV4::QObjectWrapper::setProperty(QV4::ExecutionEngine*, QObject*,
QQmlPropertyData*, QV4::Value const&) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#11 0x7fc19f98cbf7 in
QV4::QObjectWrapper::setQmlProperty(QV4::ExecutionEngine*, QQmlContextData*,
QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, QV4::Value const&)
() at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#12 0x7fc19f98cd95 in QV4::QObjectWrapper::virtualPut(QV4::Managed*,
QV4::PropertyKey, QV4::Value const&, QV4::Value*) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#13 0x7fc19f91d307 in QV4::Lookup::setterFallback(QV4::Lookup*,
QV4::ExecutionEngine*, QV4::Value&, QV4::Value const&) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#14 0x7fc19f9b4a82 in QV4::Runtime::SetLookupStrict::call(QV4::Function*,
QV4::Value const&, int, QV4::Value const&) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#15 0x7fc15d89693d in  ()
#16 0x in  ()
[Inferior 1 (process 4076) detached]

Reported using DrKonqi

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

[kdeconnect] [Bug 442967] New: Cannot share file between phone And computer

[zyf0330]

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

Bug ID: 442967
   Summary: Cannot share file between phone And computer
   Product: kdeconnect
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: zyf034...@gmail.com
  Target Milestone: ---

SUMMARY

Share files From phone to computer or from computer to phone doesn't work

STEPS TO REPRODUCE
1. Use Send files to select file at phone
2. 
3. 

OBSERVED RESULT
Phone shows notification `Failed sending file to computer`, and computer shows
notification `Receiving file from Phone` with pregress and doesn't disappear.

EXPECTED RESULT
Share successfully

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Ubuntu 21.04
(available in About System)
KDE Plasma Version: 5.21.5
KDE Frameworks Version:  5.81.0-0ubuntu1~ubuntu21.04~ppa2
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Share from computer to phone doesn't work too, and there is no alert.

I don't find infomation in adb logcat.

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[zyf0330]

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

zyf0330  changed:

   What|Removed |Added

 CC|zyf034...@gmail.com |

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

[plasmashell] [Bug 430524] Windows and Kickoff / KRunner opens in the wrong monitor

[zyf0330]

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

zyf0330  changed:

   What|Removed |Added

 CC||zyf034...@gmail.com

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

[klipper] [Bug 410773] Increase the size of the clipboard

[zyf0330]

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

zyf0330  changed:

   What|Removed |Added

 CC||zyf034...@gmail.com

--- Comment #10 from zyf0330  ---
Hello, I want to increase max history size to exceed 2048. Someone mentioned
max size is decided by memory, but I cannot understand. I find old history by
search textbox, but not hover on More item and check next page, I don't think
this operation will consume memory.

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[zyf0330]

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

zyf0330  changed:

   What|Removed |Added

 CC||zyf034...@gmail.com

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

[kdeconnect] [Bug 426706] New: kdeconnectd.exe exits after running sometime

[zyf0330]

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

Bug ID: 426706
   Summary: kdeconnectd.exe exits after running sometime
   Product: kdeconnect
   Version: unspecified
  Platform: Compiled Sources
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: zyf034...@gmail.com
  Target Milestone: ---

SUMMARY
After start kdeconnect on windows, it works normally. But after sometime,
kdeconnectd.exe exits in background. I don't know what happened.

STEPS TO REPRODUCE
1. open kdeconnect
2. wait some time, maybe few hours with using computer normally
3. 

OBSERVED RESULT

kdeconnectd exits and device connected to disconnects
EXPECTED RESULT
kdeconnectd keeps running in background

SOFTWARE/OS VERSIONS
Windows: 10 20H2 19042.508



ADDITIONAL INFORMATION

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