[plasmashell] [Bug 413104] Left-click mouse actions on Desktop don't work

2020-01-02 Thread dale
https://bugs.kde.org/show_bug.cgi?id=413104

dale  changed:

   What|Removed |Added

 CC||rdalek1...@gmail.com

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

[kdeconnect] [Bug 401366] New: I get duplicate notifications for wifi connection to KDEConnect and phone calls.

2018-11-24 Thread Dale
https://bugs.kde.org/show_bug.cgi?id=401366

Bug ID: 401366
   Summary: I get duplicate notifications for wifi connection to
KDEConnect and phone calls.
   Product: kdeconnect
   Version: 1.3.3
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: loki...@outlook.com
  Target Milestone: ---

SUMMARY
When I receive a phone call it shows on my desktop sometimes up to a dozen
times.  Also.  When I come home and my phone connects to my wifi.  I see
multiple notifications on my desktop of my app connecting to my desktop app. 
When I receive email, sms, messenger notifications.  I do not see any duplicate
notifications on my desktop.

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT
I don't need dozens of duplicate notifications.

SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: 5.14
(available in About System)
KDE Plasma Version: 5.14.3
KDE Frameworks Version: 5.52.0
Qt Version: 5.11.2

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 368838] plasmashell memory leak when slideshow is used for wallpaper/media frame/photo widget

2018-01-10 Thread dale
https://bugs.kde.org/show_bug.cgi?id=368838

dale  changed:

   What|Removed |Added

 CC||rdalek1...@gmail.com

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

[krita] [Bug 375524] New: Ambiguous Shortcut - Ctrl+W

2017-01-24 Thread Dale
https://bugs.kde.org/show_bug.cgi?id=375524

Bug ID: 375524
   Summary: Ambiguous Shortcut - Ctrl+W
   Product: krita
   Version: 3.1.1
  Platform: Windows CE
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: shortcuts
  Assignee: krita-bugs-n...@kde.org
  Reporter: dale...@yahoo.com
  Target Milestone: ---

Doesn't work.

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

[plasmashell] [Bug 386844] High Memory Usage with Qt 5.9.1 Image memory leak

2017-11-13 Thread dale
https://bugs.kde.org/show_bug.cgi?id=386844

dale  changed:

   What|Removed |Added

 CC||rdalek1...@gmail.com

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

[kdeconnect] [Bug 401366] I get duplicate notifications for wifi connection to KDEConnect and phone calls.

2018-11-25 Thread Dale
https://bugs.kde.org/show_bug.cgi?id=401366

--- Comment #1 from Dale  ---
I noticed today that my SMS messages are now getting duplicated.  I just
received one SMS on my phone.  My desktop app shows about 6 of the same
message.  What is odd is a message before that wasn't duplicated.

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

[krita] [Bug 375524] Ambiguous Shortcut - Ctrl+W

2017-02-22 Thread Dale
https://bugs.kde.org/show_bug.cgi?id=375524

--- Comment #2 from Dale  ---
Many shortcut keys fail to work in "photoshop emulation" mode.
In default mode it is fine.

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

[plasmashell] [Bug 385970] Plasmashell high memory usage when using slideshow for desktop backgrounds

2017-10-28 Thread dale
https://bugs.kde.org/show_bug.cgi?id=385970

dale  changed:

   What|Removed |Added

 CC||rdalek1...@gmail.com

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

[plasmashell] [Bug 385970] Plasmashell high memory usage when using slideshow for desktop backgrounds

2017-10-28 Thread dale
https://bugs.kde.org/show_bug.cgi?id=385970

--- Comment #1 from dale  ---
I'm having the same issue when the slideshow is used.  Usually I kill
plasmashell when I'm not going to be around the computer for a while but once I
forgot.  It kept increasing until the OOM-killer killed it.  I have 16GBs of
memory so it got real hungry.  Some info on what I have, using OP as a guide on
what to provide. 

Gentoo
plasma-5.39.0
plasma-desktop-5.11.2
plasma-workspace
dev-qt/qtcore-5.9.2  

If a dev needs more info, let me know.

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

[plasmashell] [Bug 385970] Plasmashell high memory usage when using slideshow for desktop backgrounds

2017-10-28 Thread dale
https://bugs.kde.org/show_bug.cgi?id=385970

--- Comment #2 from dale  ---
To add a little more info.  Someone posted elsewhere that maybe it was loading
the wallpaper images into memory for some reason.  To test that, I used a
directory that was large enough to see the difference but small enough to also
know if that is what it is doing.  I used one that is about 1.6GBs.  After a
few hours, it was well past what would be needed to load the wallpapers in
memory plus what plasmashell usually uses by almost 1GB.  If it is loading the
wallpapers into memory, it is also doing something else with memory as well. 
I'm not sure what.  

Also, while on this slideshow topic.  Is there a way to tell it not to
randomize the images?  I have a lot of images that are designed to be shown as
a slideshow but not in random order.  They are made to be shown in sequence.  

If I can provide any more info, let me know.

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

[plasmashell] [Bug 385970] Plasmashell high memory usage when using slideshow for desktop backgrounds

2017-11-01 Thread dale
https://bugs.kde.org/show_bug.cgi?id=385970

--- Comment #7 from dale  ---
(In reply to David Edmundson from comment #4)
> Known issue with Qt5.9.1, 5.9.2 fixes it. 
> 
> See attached bug, (which has morphed into talking about some other bug for
> some reason)
> 
> *** This bug has been marked as a duplicate of bug 381000 ***


I have 5.9.2 installed here and still have this problem.  QTcore-5.9.2 has been
installed here since the first part of October.  This is the 5.9.2 versions I
have installed.

dev-qt/qtconcurrent-5.9.2
dev-qt/qtcore-5.9.2
dev-qt/qtdbus-5.9.2
dev-qt/qtdeclarative-5.9.2
dev-qt/qtgraphicaleffects-5.9.2
dev-qt/qtgui-5.9.2
dev-qt/qtimageformats-5.9.2
dev-qt/qtmultimedia-5.9.2
dev-qt/qtnetwork-5.9.2
dev-qt/qtopengl-5.9.2
dev-qt/qtpaths-5.9.2
dev-qt/qtpositioning-5.9.2
dev-qt/qtprintsupport-5.9.2
dev-qt/qtquickcontrols-5.9.2
dev-qt/qtquickcontrols2-5.9.2
dev-qt/qtscript-5.9.2
dev-qt/qtsql-5.9.2
dev-qt/qtsvg-5.9.2
dev-qt/qttest-5.9.2
dev-qt/qtvirtualkeyboard-5.9.2
dev-qt/qtwayland-5.9.2
dev-qt/qtwebchannel-5.9.2
dev-qt/qtwebengine-5.9.2
dev-qt/qtwidgets-5.9.2
dev-qt/qtx11extras-5.9.2
dev-qt/qtxml-5.9.2
dev-qt/qtxmlpatterns-5.9.2

Is one of those supposed to have the fix?  If so, it still does the same thing
here.

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

[plasmashell] [Bug 381000] [Regression] High CPU when background is set to slideshow

2017-11-06 Thread dale
https://bugs.kde.org/show_bug.cgi?id=381000

dale  changed:

   What|Removed |Added

 CC||rdalek1...@gmail.com

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

[systemsettings] [Bug 484609] New: Unable to see all information in KDE System Settings while using fractional scaling. No scroll bar function to allow access when it exceeds display window.

2024-03-27 Thread Dale Krebs
https://bugs.kde.org/show_bug.cgi?id=484609

Bug ID: 484609
   Summary: Unable to see all information in KDE System Settings
while using fractional scaling.  No scroll bar
function to allow access when it exceeds display
window.
Classification: Applications
   Product: systemsettings
   Version: 6.0.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: dalekr...@yahoo.com
  Target Milestone: ---

Created attachment 167852
  --> https://bugs.kde.org/attachment.cgi?id=167852&action=edit
screenshot of settins (printer) and not able to see top most information

SUMMARY
Unable to see all information in KDE System Settings while using fractional
scaling. 
No scroll bar function to allow access when it exceeds display window.


STEPS TO REPRODUCE
1. change fractional scaling to 125% or more
2. open settings
3. open Printers section
4. select an installed printer (install printer if not already done) and click
on "configure" icon

OBSERVED RESULT
the window contents of my  window are more than can be shown on my display -
but there is no scroll bar to allow me to scroll up or down to unshown areas of
the configure window.

EXPECTED RESULT
all configure information be scaled to fit inside window or have a scroll bar
to allow access to ALL information

SOFTWARE/OS VERSIONS

Linux/KDE Plasma:  Fedora 40 / KDE
KDE Plasma Version: 6.02
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
I have limited vision and fractional scaling is a must use feature that I need

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

[valgrind] [Bug 475650] New: DRD does not work with C11 threads

2023-10-15 Thread Dale Weiler
https://bugs.kde.org/show_bug.cgi?id=475650

Bug ID: 475650
   Summary: DRD does not work with C11 threads
Classification: Developer tools
   Product: valgrind
   Version: unspecified
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: drd
  Assignee: bart.vanassche+...@gmail.com
  Reporter: weilercd...@gmail.com
  Target Milestone: ---

SUMMARY
DRD does not appear to support C11 threads.

STEPS TO REPRODUCE
Just create a thread in C with `thrd_create`

OBSERVED RESULT
==2451066== Process terminating with default action of signal 11 (SIGSEGV):
dumping core
==2451066==  Access not within mapped region at address 0x7
==2451066==at 0x4934634: pthread_attr_getdetachstate
(pthread_attr_getdetachstate.c:29)
==2451066==by 0x484ED7D: pthread_create_intercept
(drd_pthread_intercepts.c:609)
==2451066==by 0x484ED7D: pthread_create@* (drd_pthread_intercepts.c:640)
==2451066==by 0x493F689: thrd_create@@GLIBC_2.34 (thrd_create.c:28)

EXPECTED RESULT
Should not crash

ADDITIONAL INFORMATION
I did some digging and it appears glibcs ntpl implements thrd_create by calling
__pthread_create with an attr of ATTR_C11_THREAD which is just a macro for 
((void*)(uintptr_t)-1). Since this is not a null pointer, the check inside
DRD's pthread_create_intercept succeeds then calls pthread_attr_getdetachstate
with ((void*)(uintptr_t)-1) as the address of a valid attr struct.

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

[Spectacle] [Bug 431059] Chinese input method does not work properly in the annotation tool

2021-01-02 Thread Dale Wang
https://bugs.kde.org/show_bug.cgi?id=431059

Dale Wang  changed:

   What|Removed |Added

 CC||w.zhaok...@gmail.com

--- Comment #4 from Dale Wang  ---
(In reply to Nicolas Fella from comment #3)
> Thank you :)

The bug will be fixed in kImageAnnotator v0.4.1. 

https://github.com/ksnip/kImageAnnotator/issues/186

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

[rsibreak] [Bug 375931] New: Actions configuration can not be remembered

2017-02-02 Thread Dale Wang
https://bugs.kde.org/show_bug.cgi?id=375931

Bug ID: 375931
   Summary: Actions configuration can not be remembered
   Product: rsibreak
   Version: 0.12.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aa...@kde.org
  Reporter: w.zhaok...@gmail.com
  Target Milestone: ---

Created attachment 103784
  --> https://bugs.kde.org/attachment.cgi?id=103784&action=edit
"Actions" configuration of RSIBreak

The configuration of "Actions" of RSIBreak can not be remembered.
If you configured it and restart the RSIBreak, you will find that your
configuration are lost.

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

[rsibreak] [Bug 375931] Actions configuration can not be remembered

2017-02-02 Thread Dale Wang
https://bugs.kde.org/show_bug.cgi?id=375931

Dale Wang  changed:

   What|Removed |Added

 CC||w.zhaok...@gmail.com

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

[rsibreak] [Bug 375931] Actions configuration can not be remembered

2017-02-08 Thread Dale Wang
https://bugs.kde.org/show_bug.cgi?id=375931

--- Comment #3 from Dale Wang  ---
(In reply to Albert Astals Cid from comment #2)
> Git commit 27af2e51986b13882e3d4488cd24cb32e8b50a3f by Albert Astals Cid.
> Committed on 03/02/2017 at 23:05.
> Pushed by aacid into branch 'master'.
> 
> Save the changes made to the notifications ^_^
> 
> M  +1-0src/setup.cpp
> M  +8-3src/setupnotifications.cpp
> M  +7-0src/setupnotifications.h
> 
> https://commits.kde.org/rsibreak/27af2e51986b13882e3d4488cd24cb32e8b50a3f

Thanks Albert~ Looking forward to the new version!

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

[systemsettings] [Bug 394685] New: System Settings Closed Unexpectedly when selecting Displays

2018-05-25 Thread Dale Roberts
https://bugs.kde.org/show_bug.cgi?id=394685

Bug ID: 394685
   Summary: System Settings Closed Unexpectedly when selecting
Displays
   Product: systemsettings
   Version: 5.12.5
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: drealmobs...@gmail.com
  Target Milestone: ---

Application: systemsettings5 (5.12.5)

Qt Version: 5.10.0
Frameworks Version: 5.46.0
Operating System: Linux 4.13.0-43-generic x86_64
Distribution: KDE neon User Edition 5.12

-- Information about the crash:
- What I was doing when the application crashed Unexpectedly when selecting
Displays, cannot change display settings, laptop docked and my usual primary
monitor is not displaying desktop after upgrade to 5.12.5.

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f46df8398c0 (LWP 1923))]

Thread 4 (Thread 0x7f46ad159700 (LWP 1929)):
#0  0x7f46d52efa79 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f46d52aaf16 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f46d52ab3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f46d52ab49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f46dbc755db in QEventDispatcherGlib::processEvents
(this=0x7f46a80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f46dbc1c65a in QEventLoop::exec (this=this@entry=0x7f46ad158ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f46dba3c554 in QThread::exec (this=) at
thread/qthread.cpp:522
#7  0x7f46d9576a35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f46dba416eb in QThreadPrivate::start (arg=0x13e3f80) at
thread/qthread_unix.cpp:376
#9  0x7f46d77c76ba in start_thread (arg=0x7f46ad159700) at
pthread_create.c:333
#10 0x7f46db34e41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f46b6b2c700 (LWP 1928)):
#0  0x7f46db33e27d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f46d52ee6f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f46d52aae74 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f46d52ab330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f46d52ab49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f46dbc755db in QEventDispatcherGlib::processEvents
(this=0x7f46b8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7f46dbc1c65a in QEventLoop::exec (this=this@entry=0x7f46b6b2bce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#7  0x7f46dba3c554 in QThread::exec (this=) at
thread/qthread.cpp:522
#8  0x7f46d9576a35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#9  0x7f46dba416eb in QThreadPrivate::start (arg=0x10bd2f0) at
thread/qthread_unix.cpp:376
#10 0x7f46d77c76ba in start_thread (arg=0x7f46b6b2c700) at
pthread_create.c:333
#11 0x7f46db34e41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f46c3062700 (LWP 1926)):
#0  0x7f46db33e27d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f46d52ee6f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f46d52aae74 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f46d52ab330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f46d52ab49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f46dbc755db in QEventDispatcherGlib::processEvents
(this=0x7f46bc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7f46dbc1c65a in QEventLoop::exec (this=this@entry=0x7f46c3061cd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#7  0x7f46dba3c554 in QThread::exec (this=) at
thread/qthread.cpp:522
#8  0x7f46dd5552c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#9  0x7f46dba416eb in QThreadPrivate::start (arg=0x7f46dd7c9d60) at
thread/qthread_unix.cpp:376
#10 0x7f46d77c76ba in start_thread (arg=0x7f46c3062700) at
pthread_create.c:333
#11 0x7f46db34e41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f46df8398c0 (LWP 1923)):
[KCrash Handler]
#6  KScreen::BackendManager::loadBackendInProcess (this=0x403e870, name=...) at
/workspace/build/src/backendmanager.cpp:247
#7  0x7f46a665f021 in KScreen::ConfigOperationPrivate::loadBackend
(this=this@entry=0x405f860) at /workspace/build/src/configoperation.cpp:138
#8  0x7f46a665fcce in KScreen::GetConfigOperation