[Discover] [Bug 445000] Application crashes at clicking on "Settings" button

2021-11-10 Thread Markus Schmits
https://bugs.kde.org/show_bug.cgi?id=445000

Markus Schmits  changed:

   What|Removed |Added

 CC||marsh.exhe...@gmail.com

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

[dolphin] [Bug 444747] automatically remove newlines from filenames when renaming

2021-11-10 Thread Thomas Surrel
https://bugs.kde.org/show_bug.cgi?id=444747

Thomas Surrel  changed:

   What|Removed |Added

 CC||thomas.sur...@protonmail.co
   ||m

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

[plasmashell] [Bug 444014] Plasma crashes on logging into 21.10 Kubuntu Wayland desktop, every time

2021-11-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=444014

--- Comment #4 from ironman...@naver.com ---
Created attachment 143443
  --> https://bugs.kde.org/attachment.cgi?id=143443=edit
New crash information added by DrKonqi

plasmashell (5.22.5) using Qt 5.15.2

- What I was doing when the application crashed:
I just booted my pc, after installing NVIDIA 495 driver and choosing wayland on
login screen
- Unusual behavior I noticed:
As soon as I logged in, I saw my bios screen for brief amount of time. after
that I was booting animation, and then wallpaper. but the wallpaper quickly
turned black. and it turned back to wallpaper, and to black again. and it's now
only black screen

-- Backtrace (Reduced):
#4  __pthread_kill_implementation (no_tid=0, signo=6, threadid=139751705782656)
at pthread_kill.c:44
#5  __pthread_kill_internal (signo=6, threadid=139751705782656) at
pthread_kill.c:80
#6  __GI___pthread_kill (threadid=139751705782656, signo=signo@entry=6) at
pthread_kill.c:91
#7  0x7f1a7ed11476 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#8  0x7f1a7ecf77b7 in __GI_abort () at abort.c:79

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

[plasmashell] [Bug 445236] All Qt5 applications have their font sizes way bigger than they are supposed to be in an X11 session in Plasma 5.23.3-1. This affects all components and I am not sure what c

2021-11-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=445236

--- Comment #11 from sid.kak...@tutanota.com ---
Thanks for the quick respose
How do i fix?

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

[Discover] [Bug 445000] Application crashes at clicking on "Settings" button

2021-11-10 Thread Markus Schmits
https://bugs.kde.org/show_bug.cgi?id=445000

Markus Schmits  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |FIXED

--- Comment #2 from Markus Schmits  ---
Application: Discover (plasma-discover), signal: Segmentation fault

[New LWP 1379745]
[New LWP 1379746]
[New LWP 1379747]
[New LWP 1379748]
[New LWP 1379749]
[New LWP 1379750]
[New LWP 1379755]
[New LWP 1379756]
[New LWP 1379817]
[New LWP 1379818]
[New LWP 1379819]
[New LWP 1379823]
[New LWP 1379829]
[New LWP 1379830]
[New LWP 1379831]
[New LWP 1379832]
[New LWP 1379833]
[New LWP 1379937]
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/usr/x86_64-pc-linux-gnu/lib/libthread_db.so.1".
0x7f812d577abf in poll () from /usr/x86_64-pc-linux-gnu/lib/libc.so.6
__preamble__
[Current thread is 1 (Thread 0x7f8126d85100 (LWP 1379744))]

Thread 19 (Thread 0x7f80fa55c640 (LWP 1379937)):
#0  0x7f812d573c6c in read () at /usr/x86_64-pc-linux-gnu/lib/libc.so.6
#1  0x7f812c1ed05f in g_wakeup_acknowledge (wakeup=0x7f8087887120) at
../glib-2.68.4/glib/gwakeup.c:210
#2  0x7f812c1a2a9e in g_main_context_check
(context=context@entry=0x563943b35800, max_priority=2147483647,
fds=fds@entry=0x563943b35400, n_fds=n_fds@entry=1) at
../glib-2.68.4/glib/gmain.c:3883
#3  0x7f812c1a2ec5 in g_main_context_iterate
(context=context@entry=0x563943b35800, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
../glib-2.68.4/glib/gmain.c:4128
#4  0x7f812c1a302f in g_main_context_iteration
(context=context@entry=0x563943b35800, may_block=may_block@entry=1) at
../glib-2.68.4/glib/gmain.c:4196
#5  0x7f80fa568f1d in dconf_gdbus_worker_thread (user_data=0x563943b35800)
at ../dconf-0.40.0/gdbus/dconf-gdbus-thread.c:82
#6  0x7f812c1caa5d in g_thread_proxy (data=0x7f80875ab460) at
../glib-2.68.4/glib/gthread.c:826
#7  0x7f812d5020bf in start_thread () at
/usr/x86_64-pc-linux-gnu/lib/libc.so.6
#8  0x7f812d584440 in clone3 () at /usr/x86_64-pc-linux-gnu/lib/libc.so.6

Thread 18 (Thread 0x7f80b6ffd640 (LWP 1379833)):
#0  0x7f812d573c6c in read () at /usr/x86_64-pc-linux-gnu/lib/libc.so.6
#1  0x7f812c1ed05f in g_wakeup_acknowledge (wakeup=0x7f80a0001600) at
../glib-2.68.4/glib/gwakeup.c:210
#2  0x7f812c1a2a9e in g_main_context_check
(context=context@entry=0x7f80ac20, max_priority=2147483647,
fds=fds@entry=0x7f80a0011d30, n_fds=n_fds@entry=1) at
../glib-2.68.4/glib/gmain.c:3883
#3  0x7f812c1a2ec5 in g_main_context_iterate
(context=context@entry=0x7f80ac20, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
../glib-2.68.4/glib/gmain.c:4128
#4  0x7f812c1a302f in g_main_context_iteration (context=0x7f80ac20,
may_block=1) at ../glib-2.68.4/glib/gmain.c:4196
#5  0x7f812db8a84b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/x86_64-pc-linux-gnu/lib/libQt5Core.so.5
#6  0x7f812db35c53 in
QEventLoop::exec(QFlags) () at
/usr/x86_64-pc-linux-gnu/lib/libQt5Core.so.5
#7  0x7f812d96971e in QThread::exec() () at
/usr/x86_64-pc-linux-gnu/lib/libQt5Core.so.5
#8  0x7f812d96a6bf in QThreadPrivate::start(void*) () at
/usr/x86_64-pc-linux-gnu/lib/libQt5Core.so.5
#9  0x7f812d5020bf in start_thread () at
/usr/x86_64-pc-linux-gnu/lib/libc.so.6
#10 0x7f812d584440 in clone3 () at /usr/x86_64-pc-linux-gnu/lib/libc.so.6

Thread 17 (Thread 0x7f80b77fe640 (LWP 1379832)):
#0  0x7f812c1a24b7 in g_main_context_prepare
(context=context@entry=0x7f80ac000c20, priority=priority@entry=0x7f80b77fda78)
at ../glib-2.68.4/glib/gmain.c:3648
#1  0x7f812c1a2e4b in g_main_context_iterate
(context=context@entry=0x7f80ac000c20, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
../glib-2.68.4/glib/gmain.c:4111
#2  0x7f812c1a302f in g_main_context_iteration (context=0x7f80ac000c20,
may_block=1) at ../glib-2.68.4/glib/gmain.c:4196
#3  0x7f812db8a84b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/x86_64-pc-linux-gnu/lib/libQt5Core.so.5
#4  0x7f812db35c53 in
QEventLoop::exec(QFlags) () at
/usr/x86_64-pc-linux-gnu/lib/libQt5Core.so.5
#5  0x7f812d96971e in QThread::exec() () at
/usr/x86_64-pc-linux-gnu/lib/libQt5Core.so.5
#6  0x7f812d96a6bf in QThreadPrivate::start(void*) () at
/usr/x86_64-pc-linux-gnu/lib/libQt5Core.so.5
#7  0x7f812d5020bf in start_thread () at
/usr/x86_64-pc-linux-gnu/lib/libc.so.6
#8  0x7f812d584440 in clone3 () at /usr/x86_64-pc-linux-gnu/lib/libc.so.6

Thread 16 (Thread 0x7f80b7fff640 (LWP 1379831)):
#0  0x7f812c1a0fc2 in g_source_iter_next (iter=iter@entry=0x7f80b7ffea00,
source=source@entry=0x7f80b7ffe9f8) at ../glib-2.68.4/glib/gmain.c:1035
#1  0x7f812c1a240b in g_main_context_prepare
(context=context@entry=0x7f80a8000c20, priority=priority@entry=0x7f80b7ffea78)
at ../glib-2.68.4/glib/gmain.c:3631
#2  0x7f812c1a2e4b in g_main_context_iterate
(context=context@entry=0x7f80a8000c20, 

[plasmashell] [Bug 444815] App 'Plasma' consisting of a 1px line with a completely blank app when resized

2021-11-10 Thread strangequark
https://bugs.kde.org/show_bug.cgi?id=444815

--- Comment #4 from strangequark  ---
(In reply to strangequark from comment #3)
> (In reply to Nate Graham from comment #2)
> > When it's not already visible, can you make it reliably appear when you
> > switch activities?
> 
> Not reliably. It does seem to pop up only when switching activities/virtual
> desktops, but it doesn't appear every time.

(I am not sure about the virtual desktop part, I switch activities a lot more
frequently than virtual desktops)

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

[plasmashell] [Bug 444815] App 'Plasma' consisting of a 1px line with a completely blank app when resized

2021-11-10 Thread strangequark
https://bugs.kde.org/show_bug.cgi?id=444815

--- Comment #3 from strangequark  ---
(In reply to Nate Graham from comment #2)
> When it's not already visible, can you make it reliably appear when you
> switch activities?

Not reliably. It does seem to pop up only when switching activities/virtual
desktops, but it doesn't appear every time.

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

[lattedock] [Bug 445309] Icons became enlarged when I logged in

2021-11-10 Thread Antonio Rojas
https://bugs.kde.org/show_bug.cgi?id=445309

Antonio Rojas  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |DUPLICATE
 Status|NEEDSINFO   |RESOLVED
 CC||aro...@archlinux.org

--- Comment #3 from Antonio Rojas  ---


*** This bug has been marked as a duplicate of bug 445236 ***

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

[plasmashell] [Bug 445236] All Qt5 applications have their font sizes way bigger than they are supposed to be in an X11 session in Plasma 5.23.3-1. This affects all components and I am not sure what c

2021-11-10 Thread Antonio Rojas
https://bugs.kde.org/show_bug.cgi?id=445236

Antonio Rojas  changed:

   What|Removed |Added

 CC||sid.kak...@tutanota.com

--- Comment #10 from Antonio Rojas  ---
*** Bug 445309 has been marked as a duplicate of this bug. ***

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

[konsole] [Bug 378152] The SemiCondensed Fixed font isn't handled correctly by Konsole

2021-11-10 Thread Ahmad Samir
https://bugs.kde.org/show_bug.cgi?id=378152

--- Comment #8 from Ahmad Samir  ---
Commenting out that line breaks the "draw intense colours in bold fonts"
option, very tricky stuff :)

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

[plasmashell] [Bug 427945] Plasma Crashes when plugging in or unplugging removable drive

2021-11-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=427945

--- Comment #22 from samping...@gmail.com ---
I am having the issue where when I unmount a mounted USB using GUI method i.e.,
Systray Applet or through Dolphin, the plasmashell crashes and then replaces
itself. Here is the video showcasing this issue :-
https://www.youtube.com/watch?v=WfIZxLBrRLE

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

[kwin] [Bug 438312] Restarting kwin_x11 forgets activities assigned to windows

2021-11-10 Thread Know Zero
https://bugs.kde.org/show_bug.cgi?id=438312

Know Zero  changed:

   What|Removed |Added

 CC||knowz...@pokemail.net

--- Comment #2 from Know Zero  ---
(In reply to Oded Arbel from comment #0)
> SUMMARY
> When kwin is restarted (due to crash or on purpose - I some times need to do
> that on X11 to fixed kwin display issues), the assignment of windows to
> virtual desktop is retained, but assignment of activities is lost and all
> windows become "show on all activities".

I can also confirm it. And still continues to be an issue in 5.23.2

Yes, this it is really annoying and makes activities hard to use as they start
getting in your way when the windows just hang there.

It was so annoying I made a script to fix it manually:
https://github.com/KnowZero/Rebind-KWin-Activities

But an official fix would be nice.

PS I fix most window display issues by just switching the compositor from
opengl 2 to 3 and back. Fixes most issues without restarting kwin. But
sometimes kwin just crashes, especially when developing.

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

[ksmserver] [Bug 428795] Powerdevil won't launch anymore since 5.20.0

2021-11-10 Thread Bart Ribbers
https://bugs.kde.org/show_bug.cgi?id=428795

--- Comment #5 from Bart Ribbers  ---
Powerdevil has the same problem as kwin does for me in
https://bugs.kde.org/show_bug.cgi?id=417227, and the workaround from there
worked here too. Meaning I have had a working Powerdevil for quite a while
again, but by removing Powerdevil's capabilities (most notably CAP_WAKE_ALARM).

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

[plasmashell] [Bug 445316] On Wayland containments are randomly moved between screens on login, often resulting in disappearing panel

2021-11-10 Thread Bart Ribbers
https://bugs.kde.org/show_bug.cgi?id=445316

--- Comment #1 from Bart Ribbers  ---
I tried without the VR headset connected just to be sure, and it (sadly) made
no difference. I don't think it's related to my particular display setup, just
the fact that I have more than 1 screen.

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

[digikam] [Bug 445307] Unable to recover digiKam data on ubuntu 20.04 with Mysql server 8.0.27

2021-11-10 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=445307

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com
   Severity|crash   |normal

--- Comment #1 from Maik Qualmann  ---
You can delete your digiKam configuration file in order to restart with a First
Run Wizard. This is probably under "~/.config/digikamrc". Otherwise, of course,
a log from the terminal with an active debug variable would be helpful to
isolate the problem first. How the log is created can be found here: 

https://www.digikam.org/contribute/

Maik

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

[plasmashell] [Bug 445316] New: On Wayland containments are randomly moved between screens on login, often resulting in disappearing panel

2021-11-10 Thread Bart Ribbers
https://bugs.kde.org/show_bug.cgi?id=445316

Bug ID: 445316
   Summary: On Wayland containments are randomly moved between
screens on login, often resulting in disappearing
panel
   Product: plasmashell
   Version: 5.23.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Multi-screen support
  Assignee: aleix...@kde.org
  Reporter: bribbers+kdebugzi...@disroot.org
CC: plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY
On (practically) every login in a Wayland session, the containments are moved
around between screens. This means the panel moves and wallpapers switch
around. Often it means the panel appears on an unconnected screen connector,
forcing me to recreate the panel from scratch on basically every login. When I
then login to a X11 session, all panels show on top of each other and I can
remove them one by one till I only have my original left. Then logging in to a
Wayland session again, if I'm lucky it shows the panel but most often it's gone
again.

This has only started happening from Plasma 5.22.90 and onwards (currently
experiencing this on Plasma 5.23.3), but because of this bug has been the
buggiest release so far for me.

My setup is 2 120hz 1080p screens, one of which has FreeSync enabled, a 60hz
1080p TV set to mirror my left 120hz 1080p screen, and a VR headset (Valve
Index).

STEPS TO REPRODUCE
1. Have a multi-screen setup
2. Login to a Wayland session

OBSERVED RESULT
Containments get moved around meaning moved panel and wallpapers, and if you're
unlucky your containment moved to a not-connected connector meaning you have to
recreate your panel from scratch.

EXPECTED RESULT
Containments not to move around and remember what screen they're supposed to be
displayed on

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Alpine Linux edge
KDE Plasma Version: 5.23.3 currently, but has been happening since 5.22.90
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.3 with KDE patches

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

[plasmashell] [Bug 445315] New: Plasma crashed after exiting standby

2021-11-10 Thread Dmitry
https://bugs.kde.org/show_bug.cgi?id=445315

Bug ID: 445315
   Summary: Plasma crashed after exiting standby
   Product: plasmashell
   Version: 5.23.3
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: nedimo...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.23.3)

Qt Version: 5.15.3
Frameworks Version: 5.87.0
Operating System: Linux 5.11.0-40-generic x86_64
Windowing System: X11
Distribution: KDE neon User - Plasma 25th Anniversary Edition
DrKonqi: 5.23.3 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
Plasma crashed after exiting standby. 2 monitors are connected, some windows
have moved from the second screen to the first

The crash can be reproduced every time.

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

[New LWP 3044]
[New LWP 3135]
[New LWP 3259]
[New LWP 3384]
[New LWP 3385]
[New LWP 3387]
[New LWP 3405]
[New LWP 3408]
[New LWP 5958]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f54519ebaff in __GI___poll (fds=0x7ffc16262fb8, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
__preamble__
[Current thread is 1 (Thread 0x7f544db409c0 (LWP 3025))]

Thread 10 (Thread 0x7f54231ee700 (LWP 5958)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x55a8990a9d60) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55a8990a9d10,
cond=0x55a8990a9d38) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x55a8990a9d38, mutex=0x55a8990a9d10) at
pthread_cond_wait.c:638
#3  0x7f5451d805cb in QWaitConditionPrivate::wait (deadline=...,
this=0x55a8990a9d10) at thread/qwaitcondition_unix.cpp:146
#4  QWaitCondition::wait (this=this@entry=0x55a8984b1598,
mutex=mutex@entry=0x55a8984b1590, deadline=...) at
thread/qwaitcondition_unix.cpp:225
#5  0x7f54539e9c24 in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0x55a8984b1588) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qdeadlinetimer.h:68
#6  QSGRenderThread::processEventsAndWaitForMore
(this=this@entry=0x55a8984b14f0) at scenegraph/qsgthreadedrenderloop.cpp:936
#7  0x7f54539ea099 in QSGRenderThread::run (this=0x55a8984b14f0) at
scenegraph/qsgthreadedrenderloop.cpp:1053
#8  0x7f5451d7a45c in QThreadPrivate::start (arg=0x55a8984b14f0) at
thread/qthread_unix.cpp:329
#9  0x7f5450cc9609 in start_thread (arg=) at
pthread_create.c:477
#10 0x7f54519f8293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 9 (Thread 0x7f53f220e700 (LWP 3408)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x55a898133590) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55a898133540,
cond=0x55a898133568) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x55a898133568, mutex=0x55a898133540) at
pthread_cond_wait.c:638
#3  0x7f5451d805cb in QWaitConditionPrivate::wait (deadline=...,
this=0x55a898133540) at thread/qwaitcondition_unix.cpp:146
#4  QWaitCondition::wait (this=this@entry=0x55a897f51d98,
mutex=mutex@entry=0x55a897f51d90, deadline=...) at
thread/qwaitcondition_unix.cpp:225
#5  0x7f54539e9c24 in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0x55a897f51d88) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qdeadlinetimer.h:68
#6  QSGRenderThread::processEventsAndWaitForMore
(this=this@entry=0x55a897f51cf0) at scenegraph/qsgthreadedrenderloop.cpp:936
#7  0x7f54539ea099 in QSGRenderThread::run (this=0x55a897f51cf0) at
scenegraph/qsgthreadedrenderloop.cpp:1053
#8  0x7f5451d7a45c in QThreadPrivate::start (arg=0x55a897f51cf0) at
thread/qthread_unix.cpp:329
#9  0x7f5450cc9609 in start_thread (arg=) at
pthread_create.c:477
#10 0x7f54519f8293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 8 (Thread 0x7f54109e9700 (LWP 3405)):
#0  0x7f54519ebaff in __GI___poll (fds=0x7f53ec0071b0, nfds=1,
timeout=2143159) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f545029736e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f54502974a3 in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f5451fbb61b in QEventDispatcherGlib::processEvents
(this=0x7f53ec045210, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f5451f5f8ab in QEventLoop::exec (this=this@entry=0x7f54109e8ba0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#5  0x7f5451d792c2 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#6  0x7f542036b07c in KCupsConnection::run() () from

[Spam] [Bug 445145] *** Removed by KDE Sysadmin for violation of community policies ***

2021-11-10 Thread preethitien254
https://bugs.kde.org/show_bug.cgi?id=445145

preethitien254  changed:

   What|Removed |Added

URL||https://xyp7.com
 CC||preethitien...@gmail.com

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

[lattedock] [Bug 445309] Icons became enlarged when I logged in

2021-11-10 Thread Michail Vourlakos
https://bugs.kde.org/show_bug.cgi?id=445309

Michail Vourlakos  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #2 from Michail Vourlakos  ---
latte has nothing to do with desktop icons sizes. You should contact plasma
devs or ask for help at: https://www.reddit.com/r/kde/

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

[frameworks-ktexteditor] [Bug 444883] Autocomplete / suggestion is very slow and insert random result once I hit ENTER

2021-11-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=444883

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

--- Comment #25 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/frameworks/ktexteditor/-/merge_requests/224

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

[lattedock] [Bug 445309] Icons became enlarged when I logged in

2021-11-10 Thread Michail Vourlakos
https://bugs.kde.org/show_bug.cgi?id=445309

--- Comment #1 from Michail Vourlakos  ---
you mean at the desktop ?

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

[plasmashell] [Bug 421700] Plasma crashed in QScreen::name()/ShellCorona::addOutput()/ShellCorona::load()/KActivities::Consumer::serviceStatusChanged after I've switched from main laptop to external m

2021-11-10 Thread hluk
https://bugs.kde.org/show_bug.cgi?id=421700

--- Comment #52 from hluk  ---
(In reply to Nate Graham from comment #51)
> Thanks for that valuable observation, hluk! Any idea how we could fix this?
> Would you be interested in submitting a fix to either Plasma or Qt?

Patch posted here:
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1192

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

[plasmashell] [Bug 445314] New: X11: 2x (HiDPI) scaling even when scaling is set to 100%, regardless of GPU driver

2021-11-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=445314

Bug ID: 445314
   Summary: X11: 2x (HiDPI) scaling even when scaling is set to
100%, regardless of GPU driver
   Product: plasmashell
   Version: master
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: aa1...@vivaldi.net
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 143441
  --> https://bugs.kde.org/attachment.cgi?id=143441=edit
Corresponding attachment for OBSERVED RESULT

SUMMARY
Plasma workspace on X11 scaled to 200% even though scaling was set to 100% on
system settings, please help! This happened even though I use an open-source
driver.

STEPS TO REPRODUCE
1. Update to latest Plasma version and reboot

OBSERVED RESULT
Scaling goes 200% (see attachment)

EXPECTED RESULT
Scaling should be 100%

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2

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

[digikam] [Bug 444056] Rotating 10 images takes 4 minutes

2021-11-10 Thread Jan van Bekkum
https://bugs.kde.org/show_bug.cgi?id=444056

--- Comment #23 from Jan van Bekkum  ---
If I do the same operations on images that are on my NAS, which has a much
lower access speed than the computer memory, the operation works as expected.

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

[kdeplasma-addons] [Bug 433377] Add UK Met Office as a data source for weather

2021-11-10 Thread Bharadwaj Raju
https://bugs.kde.org/show_bug.cgi?id=433377

Bharadwaj Raju  changed:

   What|Removed |Added

 CC||bharadwaj.raju777@protonmai
   ||l.com
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Bharadwaj Raju  ---
Linked bug has been fixed, plus more search improvements with
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1191.

Closing.

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

[kdeplasma-addons] [Bug 429506] Weather applet search does not work

2021-11-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=429506

Bug Janitor Service  changed:

   What|Removed |Added

 Status|REPORTED|ASSIGNED
 Ever confirmed|0   |1

--- Comment #1 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1191

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

[konsole] [Bug 378152] The SemiCondensed Fixed font isn't handled correctly by Konsole

2021-11-10 Thread Jiri Slaby
https://bugs.kde.org/show_bug.cgi?id=378152

--- Comment #7 from Jiri Slaby  ---
Created attachment 143440
  --> https://bugs.kde.org/attachment.cgi?id=143440=edit
workaround patch

(In reply to Ahmad Samir from comment #6)
> I am not sure it's the same issue as that upstream bug; the code in Konsole
> sets the styleName to an empty string

Confirmed. The qt fix doesn't help (obviously; but is a bug too). Commenting
out the line (patch attached) indeed helps.

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

[kdeplasma-addons] [Bug 436974] Weather Report can't find some cities in search, works only when configured manually

2021-11-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=436974

Bug Janitor Service  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|ASSIGNED

--- Comment #1 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1191

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

[baloo-widgets] [Bug 445313] preethi

2021-11-10 Thread preethitien254
https://bugs.kde.org/show_bug.cgi?id=445313

preethitien254  changed:

   What|Removed |Added

URL||https://xyp7.com

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

[baloo-widgets] [Bug 445313] New: preethi

2021-11-10 Thread preethitien254
https://bugs.kde.org/show_bug.cgi?id=445313

Bug ID: 445313
   Summary: preethi
   Product: baloo-widgets
   Version: 21.08.2
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: baloo-bugs-n...@kde.org
  Reporter: preethitien...@gmail.com
  Target Milestone: ---

If you are looking for a safe and secure gambling online site, the answer’s
here. Just visit my website and you’ll see a lot of popular and best casino
sites in Korea. Casino sites that will sure give you memorable fun and
experiences. You can play your assorted casino games like baccarat, keno,
roulette, and even your favorite slot games.

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

[baloo-widgets] [Bug 445312] New: preethi

2021-11-10 Thread preethitien254
https://bugs.kde.org/show_bug.cgi?id=445312

Bug ID: 445312
   Summary: preethi
   Product: baloo-widgets
   Version: 21.08.2
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: baloo-bugs-n...@kde.org
  Reporter: preethitien...@gmail.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. I’m a web developer living in Texarkana
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.

[krita] [Bug 444975] Resources > Workspaces: Can't overwrite different workspace of the same name.

2021-11-10 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=444975

--- Comment #7 from Emmet O'Neill  ---
Just a quick addendum to the last post:

If you copy "Default.kws" to another location, and rename it to "Big
Paint.kws", *and then change the workspace's internal "name" XML attribute to
"Big_Paint"*, and import, it will prompt and overwrite, as you'd expect.

BUT.

There will then be 2 "Animation" workspaces, with one looking like the new
Krita 5.0 animation workspace, and the other looking like the old (pre-5.0)
animation workspace.

This is kind of the missing link between the two behaviors mentioned above.

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

[kde] [Bug 143327] Cursors reset to default system visuals on KDE start

2021-11-10 Thread preethitien254
https://bugs.kde.org/show_bug.cgi?id=143327

preethitien254  changed:

   What|Removed |Added

 CC||preethitien...@gmail.com

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

[krita] [Bug 444975] Resources > Workspaces: Can't overwrite different workspace of the same name.

2021-11-10 Thread Emmet O'Neill
https://bugs.kde.org/show_bug.cgi?id=444975

--- Comment #6 from Emmet O'Neill  ---
I've observed 2 pretty strange behaviors here:

Strange behavior 1:

If you copy "Default.kws" to another location, and rename it to
"Storyboarding.kws" *without changing the workspace's internal "name"
attribute* it will, for some reason, appear in the workspaces list as a second
workspace called "Animation" upon import with overwrite prompt.

This new workspace, that should be named "default" (based on the internal name)
OR "storyboard" (based on the filename), while looking like the default
workspace, actually looks like the OLD (pre-5.0) "animation" workspace...

After restarting Krita, this seems to resolve itself. Specifically, from the
GUI you can only see 1 "animation" workspace (that looks as it should), 2
"default" workspaces (based on the shared internal workspace name XML
attribute) that both correctly look like they should. Finally, there is no
longer any "storyboarding" workspace. That's also expected.

---

Strange behavior 2:

This is similar, but slightly different.

If you copy "Default.kws" to another location, and rename it to
"Animation.kws", *and then change the workspace's internal "name" XML attribute
to "Animation"*, and import, it will prompt and overwrite, as you'd expect.
There will still be only 1 workspace named "Animation" in the list.

However, the "Animation" workspace, which should look like the default
workspace that we copied, will for some reason look like the OLD (pre-5.0)
animation workspace instead!

After restarting Krita, this also seems to resolve itself! Specifically, there
will be only 1 "Animation" workspace in the list, and it will correctly look
like the default layout that we copied.

---

These are probably the same or similar bug[s].

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

[systemsettings] [Bug 440493] Add an option for whether to enable or disable Bluetooth adapters at session start

2021-11-10 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=440493

--- Comment #28 from Nate Graham  ---
Does it work properly for you only when the config file has
`bluetoothBlocked=true` in it? Or does it also work if the config file has
`bluetoothBlocked=false` in it?

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

[kwin] [Bug 405080] Right-click menus sometimes show titlebars in wayland

2021-11-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=405080

qydwhotm...@gmail.com changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=445311

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

[kwin] [Bug 445311] New: Right-click menus show titlebars when opened by a stylus in wayland

2021-11-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=445311

Bug ID: 445311
   Summary: Right-click menus show titlebars when opened by a
stylus in wayland
   Product: kwin
   Version: 5.23.2
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: wayland
  Severity: normal
  Priority: NOR
 Component: decorations
  Assignee: kwin-bugs-n...@kde.org
  Reporter: qydwhotm...@gmail.com
  Target Milestone: ---

SUMMARY
The menu has a titlebar when clicking with a stylus.

STEPS TO REPRODUCE
1. Open Konsole
2. Click "Help" by using a stylus

OBSERVED RESULT
A menu with a titlebar is shown.

EXPECTED RESULT
Menu without a titlebar

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2

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

[plasmashell] [Bug 445310] New: Kickoff ignores hover events generated by a stylus if it's opened by touch for the first time

2021-11-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=445310

Bug ID: 445310
   Summary: Kickoff ignores hover events generated by a stylus if
it's opened by touch for the first time
   Product: plasmashell
   Version: 5.23.3
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: wayland
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: qydwhotm...@gmail.com
CC: mikel5...@gmail.com, noaha...@gmail.com,
plasma-b...@kde.org
Depends on: 445111
  Target Milestone: 1.0

SUMMARY
If Kickoff (can't reproduce on other applets) is opened by touch for the first
time after plasmashell starts, it will not respond to stylus hover events until
clicking on it. 

STEPS TO REPRODUCE
1. Restart plasmashell
2. Touch Kickoff icon
3. Touch to open a program
4. Open Kickoff using a stylus

OBSERVED RESULT
Kickoff ignores hover events generated by the stylus (No highlight)

EXPECTED RESULT
Highlight appears when hovering on an item.

SOFTWARE/OS VERSIONS
In a Wayland session


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=445111
[Bug 445111] Kickoff does not react to graphics tablet left click anymore
-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 445111] Kickoff does not react to graphics tablet left click anymore

2021-11-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=445111

qydwhotm...@gmail.com changed:

   What|Removed |Added

 Blocks||445310
   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=445310


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=445310
[Bug 445310] Kickoff ignores hover events generated by a stylus if it's opened
by touch for the first time
-- 
You are receiving this mail because:
You are watching all bug changes.

[lattedock] [Bug 445309] New: Icons became enlarged when I logged in

2021-11-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=445309

Bug ID: 445309
   Summary: Icons became enlarged when I logged in
   Product: lattedock
   Version: 0.10.3
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: plasmoid
  Assignee: mvourla...@gmail.com
  Reporter: sid.kak...@tutanota.com
  Target Milestone: ---

Created attachment 143439
  --> https://bugs.kde.org/attachment.cgi?id=143439=edit
Look at the enlarged items

SUMMARY
Ions became enlarged when I logged in

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.

[kmymoney] [Bug 444374] Exclusive UI language change is not applied.

2021-11-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=444374

--- Comment #7 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[plasmashell] [Bug 444415] On wayland, panel shadow doesn't show where system tray is

2021-11-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=15

--- Comment #4 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[systemsettings] [Bug 432093] KCM title is displayed above the sidebar

2021-11-10 Thread EDeadLock
https://bugs.kde.org/show_bug.cgi?id=432093

--- Comment #8 from EDeadLock  ---
I would like to add that this issue isnt random and that it also shows up in
other settings items other than Workspace Behavior. 

The issue only appears the first time you "visit" a settings page (e.g. Screen
Edges page). Each time you revisit the page (by clicking on a different page
and then going back to the original page) issue doesnt show up. To get the page
to show the issue again you have to either go back to the main settings page or
exit and reopen the settings app altogether.

Something else I noticed. After revisiting a page and making the issue go away.
It doesn't really go away. Well, it does go away but it shows a different
issue. This is better explained with the screenshots I provided. On the tittles
there are supposed to be a line that covers the entire page. The padding is not
the same as the working pages (You will notice the working page titles are
slightly more centered). And I also think the font is slightly smaller? but I
cant confirm that

I would love to help fix this issue but I dont know where to start. I managed
to set up the neon docker container. How can I enable logging on the settings
app or edit the code and test?

One thing that I can try to do is going back to earlier versions because I know
this issue wasnt here at some point (i cant remember when though lol or maybe
im  imagining things)

As mentioned earlier, this issue also shows up in other settings items and
under specific pages. Here is a painstakingly long list:
Workspace Behavior:
* Screen Edges
* Touch Screen
* Activities
Window Management:
* Window Behavior
* Task Switcher
* KWin Scripts
Search:
* Krunner
* Web Search Keywords
Regional Settings:
* Spell Check
* Date & Time
Applications:
* File Associations
* Locations
Settings: (Side rant: "Settings" should reeally be renamed to something
else like "Advanced Network Settings")
* Connection Preferences
* SSL Preferences
* Cookies
Input devices:
* Keyboard
* Touchpad
Display and Monitor:
* Compositor
Power Management: (This one would be a good place to start debugging as all the
pages here have the issue)
* Energy Savings
* Active Power Settings
* Advanced Power Settings
Removable Storage:
* Removable Devices

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

[systemsettings] [Bug 432093] KCM title is displayed above the sidebar

2021-11-10 Thread EDeadLock
https://bugs.kde.org/show_bug.cgi?id=432093

--- Comment #7 from EDeadLock  ---
Created attachment 143438
  --> https://bugs.kde.org/attachment.cgi?id=143438=edit
Normal page

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

[systemsettings] [Bug 432093] KCM title is displayed above the sidebar

2021-11-10 Thread EDeadLock
https://bugs.kde.org/show_bug.cgi?id=432093

EDeadLock  changed:

   What|Removed |Added

 CC||maicolgabr...@hotmail.com

--- Comment #6 from EDeadLock  ---
Created attachment 143437
  --> https://bugs.kde.org/attachment.cgi?id=143437=edit
Revisited page still with issues

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

[krita] [Bug 445308] New: Document Name is outdated

2021-11-10 Thread keyth_qcfx2
https://bugs.kde.org/show_bug.cgi?id=445308

Bug ID: 445308
   Summary: Document Name is outdated
   Product: krita
   Version: 5.0.0-beta2
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Scripting
  Assignee: krita-bugs-n...@kde.org
  Reporter: keyth2363...@gmail.com
  Target Milestone: ---

SUMMARY
File Name is outdated when asking Python the documents name.

STEPS TO REPRODUCE
1. Create a new file
2. Save new file as “test_AAA.kra”
3. now save file again as “test_BBB.kra”
4. Close file
5. Open file “test_BBB.kra”
6. Go to: Tools > Scripts > Scripter
7. Run the following code:
"""
import krita
name = Krita.instance().activeDocument().name()
print(str(name))
"""

OBSERVED RESULT
Result file name will always be the first saved name “test_AAA” being outdate
regardless of the version of the file.

EXPECTED RESULT
should output "test_BBB" as the file name "test_BBB.kra" indicates.

SOFTWARE/OS VERSIONS
Windows: 10
Qt Version: 5.12

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

[kdenlive] [Bug 445214] OpenTimelinIO Export/Import Fails: OTIO kdenlive/mlt adapter is out of date?

2021-11-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=445214

david.johanna...@gmail.com changed:

   What|Removed |Added

 CC||david.johanna...@gmail.com

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

[krita] [Bug 445043] Attempting to rename a tag to the same name causes the tag to be deleted

2021-11-10 Thread Eoin O'Neill
https://bugs.kde.org/show_bug.cgi?id=445043

Eoin O'Neill  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap
   |hics/krita/commit/19340fcd2 |hics/krita/commit/a034950bb
   |e7cb0f1df4d66a02036d0a7107c |400da73ced6135cf85bbe2f13cd
   |897b|d413

--- Comment #2 from Eoin O'Neill  ---
Git commit a034950bb400da73ced6135cf85bbe2f13cdd413 by Eoin O'Neill.
Committed on 11/11/2021 at 04:17.
Pushed by eoinoneill into branch 'krita/5.0'.

Prevent deletion of tag when renaming to same name.

We should just skip renaming the tag in the off chance
that someone types in the same name as the currently
selected tag.
(cherry picked from commit 19340fcd2e7cb0f1df4d66a02036d0a7107c897b)

M  +1-1libs/resourcewidgets/KisTagChooserWidget.cpp

https://invent.kde.org/graphics/krita/commit/a034950bb400da73ced6135cf85bbe2f13cdd413

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

[krita] [Bug 445043] Attempting to rename a tag to the same name causes the tag to be deleted

2021-11-10 Thread Eoin O'Neill
https://bugs.kde.org/show_bug.cgi?id=445043

Eoin O'Neill  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/grap
   ||hics/krita/commit/19340fcd2
   ||e7cb0f1df4d66a02036d0a7107c
   ||897b

--- Comment #1 from Eoin O'Neill  ---
Git commit 19340fcd2e7cb0f1df4d66a02036d0a7107c897b by Eoin O'Neill.
Committed on 11/11/2021 at 04:16.
Pushed by eoinoneill into branch 'master'.

Prevent deletion of tag when renaming to same name.

We should just skip renaming the tag in the off chance
that someone types in the same name as the currently
selected tag.

M  +1-1libs/resourcewidgets/KisTagChooserWidget.cpp

https://invent.kde.org/graphics/krita/commit/19340fcd2e7cb0f1df4d66a02036d0a7107c897b

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

[plasmashell] [Bug 445261] A transparent ghost of window appear on my desktop when I leave off.

2021-11-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=445261

--- Comment #3 from miclei...@hotmail.com ---
在 2021/11/10 17:47, Paul Worrall 写道:
> https://bugs.kde.org/show_bug.cgi?id=445261
>
> Paul Worrall  changed:
>
> What|Removed |Added
> 
>   CC||p.r.worr...@gmail.com
>
> --- Comment #1 from Paul Worrall  ---
> Sorry but please could you clarify what you mean by "leave off"
> Also are you referring to a "Desktop Effect" (in System Settings=>Workspace
> Behaviour)?  If so, which Desktop Effect do you have to close to close the
> ghost window?
>
Dear Paul,

Sorry for my rough explain.That is,when I minmize even close my program 
window,the program window was not be "closed", it looks like a 
waterprint or a ghost print sticking on my wallpaper area.But actually 
the program was closed.

The effect may be these.

If some of you know Chinese,I will say this may be easier:

最小化或关闭窗口时,该窗口的半透明特效会留在桌面上。而我确实已经把程序关掉了,并在任务管理器里面检查过。只有注销或重启它才会消失。

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

[krita] [Bug 445043] Attempting to rename a tag to the same name causes the tag to be deleted

2021-11-10 Thread Eoin O'Neill
https://bugs.kde.org/show_bug.cgi?id=445043

Eoin O'Neill  changed:

   What|Removed |Added

   Assignee|krita-bugs-n...@kde.org |eoinoneill1...@gmail.com

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

[krita] [Bug 445265] Animation cache not updated correctly

2021-11-10 Thread Eoin O'Neill
https://bugs.kde.org/show_bug.cgi?id=445265

Eoin O'Neill  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap
   |hics/krita/commit/014f33b51 |hics/krita/commit/f7bd2832f
   |7fe4b8b83e518dbd7445bf1e9cf |3414f4222f1f0e8812dbf8919b4
   |7e4c|579b

--- Comment #3 from Eoin O'Neill  ---
Git commit f7bd2832f3414f4222f1f0e8812dbf8919b4579b by Eoin O'Neill.
Committed on 11/11/2021 at 03:58.
Pushed by eoinoneill into branch 'krita/5.0'.

Fix caching bug when scrubbing from cached to uncached frame.

An optimization to prevent unnecessary refreshes was causing a
regression. Since scrubbing on cached frames doesn't trigger a
time change, but uncached frames do, an optimization where
we check if the last frame and the current frame exist within
the same "timeframe" would lock users out from seeing the
uncached frames properly when scrubbing.

We now force at least one time switch call when switching from
uncached to cached frames to prevent this issue. Now, it will
properly recognize that the last frame and the 'current frame'
are different and refresh their contents.
(cherry picked from commit 014f33b517fe4b8b83e518dbd7445bf1e9cf7e4c)

M  +23   -6plugins/dockers/animation/KisTimeBasedItemModel.cpp
M  +1-0plugins/dockers/animation/KisTimeBasedItemModel.h

https://invent.kde.org/graphics/krita/commit/f7bd2832f3414f4222f1f0e8812dbf8919b4579b

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

[krita] [Bug 445265] Animation cache not updated correctly

2021-11-10 Thread Eoin O'Neill
https://bugs.kde.org/show_bug.cgi?id=445265

Eoin O'Neill  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/grap
   ||hics/krita/commit/014f33b51
   ||7fe4b8b83e518dbd7445bf1e9cf
   ||7e4c
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Eoin O'Neill  ---
Git commit 014f33b517fe4b8b83e518dbd7445bf1e9cf7e4c by Eoin O'Neill.
Committed on 11/11/2021 at 03:51.
Pushed by eoinoneill into branch 'master'.

Fix caching bug when scrubbing from cached to uncached frame.

An optimization to prevent unnecessary refreshes was causing a
regression. Since scrubbing on cached frames doesn't trigger a
time change, but uncached frames do, an optimization where
we check if the last frame and the current frame exist within
the same "timeframe" would lock users out from seeing the
uncached frames properly when scrubbing.

We now force at least one time switch call when switching from
uncached to cached frames to prevent this issue. Now, it will
properly recognize that the last frame and the 'current frame'
are different and refresh their contents.

M  +23   -6plugins/dockers/animation/KisTimeBasedItemModel.cpp
M  +1-0plugins/dockers/animation/KisTimeBasedItemModel.h

https://invent.kde.org/graphics/krita/commit/014f33b517fe4b8b83e518dbd7445bf1e9cf7e4c

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

[krita] [Bug 445265] Animation cache not updated correctly

2021-11-10 Thread Eoin O'Neill
https://bugs.kde.org/show_bug.cgi?id=445265

Eoin O'Neill  changed:

   What|Removed |Added

   Assignee|krita-bugs-n...@kde.org |eoinoneill1...@gmail.com
 CC||eoinoneill1...@gmail.com

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

[frameworks-kdeclarative] [Bug 417636] Title rows of QML KCMs fade in and out, but others don't

2021-11-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=417636

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

--- Comment #10 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/frameworks/kirigami/-/merge_requests/418

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

[kinfocenter] [Bug 400079] kinfocenter should show more information about your hardware from `dmidecode`

2021-11-10 Thread Brian Kaye
https://bugs.kde.org/show_bug.cgi?id=400079

--- Comment #8 from Brian Kaye  ---
In addition to the dmidecode stuff it would be nice to have some basic power
supply/battery information

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

[digikam] [Bug 445307] New: Unable to recover digiKam data on ubuntu 20.04 with Mysql server 8.0.27

2021-11-10 Thread Gerry Matte
https://bugs.kde.org/show_bug.cgi?id=445307

Bug ID: 445307
   Summary: Unable to recover digiKam data on ubuntu 20.04 with
Mysql server 8.0.27
   Product: digikam
   Version: 7.3.0
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Bundle-AppImage
  Assignee: digikam-bugs-n...@kde.org
  Reporter: ge...@gerrymatte.ca
  Target Milestone: ---

When I first ran the Linux AppImage I went through the "First Run" wizard and
eventually succeeded in configuring digiKam to use the local MySql database. 
Over a few weeks I processed all of my Pictures folders mainly completing
facial recognition.

Reasonably frequently I have been using the MySql backup facility to export the
Pictures database.

A few days ago, I suffered a major failure on my boot drive and after I managed
to boot I reloaded my Ubuntu System using a Timeshift Backup I created about a
month ago.  The system then operated correctly.

However, I realised that the MySql server databases had their data restored
back to the date I last backed up Ubuntu. 
 So, I have been reloading the MySql databases from their MySql backups. 
Everything seemed to proceed well - I restored my gnucash database and there
were no problems at all.

However, after I restored my digiKam "Pictures" database the application would
not start.  The splash screen appeared followed by an error window indicating
digiKam was unable to connect to the MySql database - with no indication what I
could do.  I tried deleting the database and recreating it with no data but
that made no difference.  So I deleted the "Pictures" database hoping digiKam
would execute its "First Run" wizard but that did not happen. 

Is there a way to execute digiKam and force it to run the "First Run" wizard ?  
Or can I delete digiKam settings and trigger the "First Run" wizard to run
again ?

I believe that the MySql server ugraded itself from 8.0.26 to 8.0.27 at some
point  that may be why my restored database was preventing digiKam from
starting.

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

[plasmashell] [Bug 445306] New: Grouped tasks in Icons-only Task Manager are sometimes missing plus icon

2021-11-10 Thread nyanpasu64
https://bugs.kde.org/show_bug.cgi?id=445306

Bug ID: 445306
   Summary: Grouped tasks in Icons-only Task Manager are sometimes
missing plus icon
   Product: plasmashell
   Version: 5.23.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Task Manager and Icons-Only Task Manager
  Assignee: h...@kde.org
  Reporter: nyanpas...@tuta.io
CC: plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY
Sometimes when I open more than 1 window of an app, and they're grouped
together in the Icons-only Task Manager, the task manager icon is missing a
green plus icon.

STEPS TO REPRODUCE
1. Open more than 1 of an app. (Didn't find an exact procedure.)

OBSERVED RESULT
There is no plus icon on the task manager. It does not appear when closing
windows (forgot to test opening windows). Hovering the icon in the task manager
shows multiple previews as expected.

EXPECTED RESULT
Whenever multiple windows of an app are open, a plus icon is shown.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.14.16-zen1-1-zen (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: NVIDIA GeForce GT 730/PCIe/SSE2

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 445302] Detect and notify for missing drivers or codecs

2021-11-10 Thread Alex
https://bugs.kde.org/show_bug.cgi?id=445302

Alex  changed:

   What|Removed |Added

 CC||alex...@protonmail.com

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

[plasmashell] [Bug 445236] All Qt5 applications have their font sizes way bigger than they are supposed to be in an X11 session in Plasma 5.23.3-1. This affects all components and I am not sure what c

2021-11-10 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=445236

Nicolas Fella  changed:

   What|Removed |Added

 CC||faizahna...@gmail.com

--- Comment #9 from Nicolas Fella  ---
*** Bug 445305 has been marked as a duplicate of this bug. ***

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

[systemsettings] [Bug 445305] global scale turn UI bigger than it has, its like set 100% but looks 200%

2021-11-10 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=445305

Nicolas Fella  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||nicolas.fe...@gmx.de
 Resolution|--- |DUPLICATE

--- Comment #1 from Nicolas Fella  ---


*** This bug has been marked as a duplicate of bug 445236 ***

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

[systemsettings] [Bug 445224] Short date format preview not visible on Time page

2021-11-10 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=445224

--- Comment #11 from Nate Graham  ---
If you set `reserveSpaceForSubtitle: true` on the list items on the Time page,
they will be tall enough to accommodate a two-line trailing item.

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

[systemsettings] [Bug 445305] New: global scale turn UI bigger than it has, its like set 100% but looks 200%

2021-11-10 Thread Faiz Ahnaf Samudra Azis
https://bugs.kde.org/show_bug.cgi?id=445305

Bug ID: 445305
   Summary: global scale turn UI bigger than it has, its like set
100% but looks 200%
   Product: systemsettings
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: kcm_kscreen
  Assignee: kscreen-bugs-n...@kde.org
  Reporter: faizahna...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

Created attachment 143434
  --> https://bugs.kde.org/attachment.cgi?id=143434=edit
global scale is not the same than what it do, its 100% scale but UI looks
bigger

SUMMARY
after updating to latest version, from aur package, my icon and other is
getting bigger, i turn my display global scale to the lowest which is 100%, but
is looks like its turned into 200% scale. i've reinstall and same result, even
i reinstall using live usb with distro from endeavor (arch distro) and use
latest kde and still no changes

STEPS TO REPRODUCE
1. update to latest kde, my repo is aur and arch package
2. restart system
3. check all your icon, window decoration, and app launcher get bigger without 
you changing the scaling from 100 but turned to 200 i think

OBSERVED RESULT
display global scale got bigger

EXPECTED RESULT
normal size for scaling

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.23 3-1
(available in About System)
KDE Plasma Version:  5.23.3
KDE Frameworks Version:  5.87.0
Qt Version: 5.15.2

thank you, im 17 y/o and my first time doing this, thank you

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

[systemsettings] [Bug 445224] Short date format preview not visible on Time page

2021-11-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=445224

--- Comment #10 from hanyo...@protonmail.com ---
(In reply to Nate Graham from comment #9)
> Why not use two lines, like on the main page?

It's implemented as trailing, so for it to properly display, the height of the
ListItem must be larger than the trailing. But on PinePhone this isn't the
case, resulting in trailing overlapping the next listitem. On main menu the
listitem is large enough.

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

[systemsettings] [Bug 445224] Short date format preview not visible on Time page

2021-11-10 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=445224

--- Comment #9 from Nate Graham  ---
Why not use two lines, like on the main page?

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

[plasma-systemmonitor] [Bug 434039] Memory details are missing

2021-11-10 Thread Nicolas Werner
https://bugs.kde.org/show_bug.cgi?id=434039

--- Comment #4 from Nicolas Werner  ---
I'm sorry that I didn't reply originally. I had my email set to an old address
and forgot about it.  I'm very happy to see, that the memory view was kept
though! So I think my reply is not really necessary, but I'll add it anyway:

I do agree, that a dedicated application would probably make more sense, but I
haven't found one yet, that displays that information in such a concise and
easy to access manner. I usually use it to quickly figure out, where an
application is using memory, since I have a lot of applications, that memory
map files and seeing what is dirty, what are libraries, etc is very useful to
me. It is also very useful, that one can see what files an application has
loaded into memory, which can be used to figure out what libraries an
application has still loaded into memory, what database it has open and more.
It mostly became a habit to look there, because I am used to that view
existing. I know, there are other ways to do that, but they are either not as
convenient or I don't have the muscle memory for it. Thank you very much for
keeping it around, I hope it isn't too big of a burden to maintain!

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

[systemsettings] [Bug 445224] Short date format preview not visible on Time page

2021-11-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=445224

--- Comment #8 from hanyo...@protonmail.com ---
I excluded short format on Time page because otherwise it's too long to fit in
one line. There will be short time format examples after Language & Formats
merge done.

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

[plasmashell] [Bug 445284] Keyboard layout switcher not working properly after 5.23.3 update

2021-11-10 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=445284

Nate Graham  changed:

   What|Removed |Added

 Resolution|LATER   |NOT A BUG

--- Comment #8 from Nate Graham  ---
Yeah, IBus and FCITX will conflict, and you should use only one. And they have
to be configured properly, too.

Not sure what we can do here in KDE code to improve this situation. I'm not
very knowledgeable about input methods. Do you have any ideas Andrey?

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

[Discover] [Bug 445228] Discover flatpak "System Updates" section disappears after doing a non-Update All

2021-11-10 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=445228

--- Comment #5 from Nate Graham  ---
`plasma-discover --listbackends` will tell you what backends you have.

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

[krita] [Bug 445152] When the drawing angle is locked, the drawing angle of the nib will still change

2021-11-10 Thread killy
https://bugs.kde.org/show_bug.cgi?id=445152

--- Comment #6 from killy <80536...@qq.com> ---
Yes, my test results are the same

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

[plasmashell] [Bug 445286] Hide the on-screen volume adjustment indicator when adjusting from system tray with mouse scroll wheel

2021-11-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=445286

--- Comment #4 from yiz...@kulodgei.com ---
(In reply to Nate Graham from comment #3)
> > The user has to click on the volume icon (where the visual indicator 
> > already exists)
> > and then use the mouse scroll wheel up or down. 
> They do not. It is enough to roll the wheel while hovering over the tray
> icon; no need to click on it first.

I got to admit that is pretty cool. I was not aware of that.

In this case. I am not sure if users can hide the "tool tip" style bubbles that
show when you hover over the volume icon in which case it would be useful. But
if you cannot hide those tool tip style pop ups, you still run into the same
thing with the volume % being shown in two times close to each other.

It shows while hovering over the volume icon and scrolling up down and also
shows from the visual indicator. They aren't even that far apart depending on
how big your screen is.

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

[kwin] [Bug 443224] Kwin puts titlebar wrongly in some java apps

2021-11-10 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=443224

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|REOPENED|NEEDSINFO

--- Comment #8 from Nate Graham  ---
Oh you must be talking about the splash screens.

I also see the Wayland logo, so you must be using the Plasma Wayland session.
Do the splash screens look correct in the X11 session?

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

[kwin] [Bug 443224] Kwin puts titlebar wrongly in some java apps

2021-11-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=443224

lucbo...@gmail.com changed:

   What|Removed |Added

 Resolution|WORKSFORME  |---
 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1

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

[krunner] [Bug 445304] New: KRunner does not find KInfoCenter KCMs by their X-KDE-Keywords

2021-11-10 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=445304

Bug ID: 445304
   Summary: KRunner does not find KInfoCenter KCMs by their
X-KDE-Keywords
   Product: krunner
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: alexander.loh...@gmx.de
  Reporter: n...@kde.org
CC: plasma-b...@kde.org
  Target Milestone: ---

The Device Info KCM's .desktop file has:

X-KDE-Keywords=device,devices,disk,drive,processor,cpu

However if I search for any of these terms, KRunner does not find it--except
for when I search for "device", but I assume that's because it appears in the
KCM's name.

This works fine for System Settings KCMs, but appears to not work for
KInfoCenter KCMs.

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

[kwin] [Bug 443224] Kwin puts titlebar wrongly in some java apps

2021-11-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=443224

--- Comment #7 from lucbo...@gmail.com ---
Created attachment 143433
  --> https://bugs.kde.org/attachment.cgi?id=143433=edit
IntelliJ Idea Community

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

[kwin] [Bug 443224] Kwin puts titlebar wrongly in some java apps

2021-11-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=443224

--- Comment #6 from lucbo...@gmail.com ---
Created attachment 143432
  --> https://bugs.kde.org/attachment.cgi?id=143432=edit
Eclipse IDE

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

[plasmashell] [Bug 445303] New: Focus conflicts in Task Manager and System Tray and right click crashes Plasma

2021-11-10 Thread José Alberto González
https://bugs.kde.org/show_bug.cgi?id=445303

Bug ID: 445303
   Summary: Focus conflicts in Task Manager and System Tray and
right click crashes Plasma
   Product: plasmashell
   Version: 5.23.3
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: josealbertogonza...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.23.3)

Qt Version: 5.15.3
Frameworks Version: 5.88.0
Operating System: Linux 5.4.0-53-lowlatency x86_64
Windowing System: X11
Distribution: KDE neon Testing Edition
DrKonqi: 5.23.3 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed: when right click over an app (
anydesk) crashed plasma, same when dragged an mp3 file over audacious player
icon

The reporter is unsure if this crash is reproducible.

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

[New LWP 1749]
[New LWP 1766]
[New LWP 1771]
[New LWP 1772]
[New LWP 1773]
[New LWP 1774]
[New LWP 1927]
[New LWP 1960]
[New LWP 1961]
[New LWP 1988]
[New LWP 1996]
[New LWP 2034]
[New LWP 2035]
[New LWP 8511]
[New LWP 10057]
[New LWP 11462]
[New LWP 11463]
[New LWP 11466]
[New LWP 11467]
[New LWP 11468]
[New LWP 11469]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
futex_wait_cancelable (private=, expected=0,
futex_word=0x55a039bf6c40) at ../sysdeps/nptl/futex-internal.h:183
__preamble__
[Current thread is 1 (Thread 0x7fd18ff4e380 (LWP 1738))]

Thread 22 (Thread 0x7fd1277fe700 (LWP 11469)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x55a0353a4f70) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55a0353a4f20,
cond=0x55a0353a4f48) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x55a0353a4f48, mutex=0x55a0353a4f20) at
pthread_cond_wait.c:647
#3  0x7fd1941c25cb in QWaitConditionPrivate::wait(QDeadlineTimer)
(deadline=..., this=0x55a0353a4f20) at thread/qwaitcondition_unix.cpp:146
#4  QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=,
mutex=0x55a03da40a00, deadline=...) at thread/qwaitcondition_unix.cpp:225
#5  0x7fd168154fe0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7fd168158cfe in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7fd1681541a2 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7fd168156c53 in ThreadWeaver::Thread::run() () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7fd1941bc45c in QThreadPrivate::start(void*) (arg=0x55a035a10d90) at
thread/qthread_unix.cpp:329
#10 0x7fd193106609 in start_thread (arg=) at
pthread_create.c:477
#11 0x7fd193e3a293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 21 (Thread 0x7fd127fff700 (LWP 11468)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x55a0353a4f70) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55a0353a4f20,
cond=0x55a0353a4f48) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x55a0353a4f48, mutex=0x55a0353a4f20) at
pthread_cond_wait.c:647
#3  0x7fd1941c25cb in QWaitConditionPrivate::wait(QDeadlineTimer)
(deadline=..., this=0x55a0353a4f20) at thread/qwaitcondition_unix.cpp:146
#4  QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=,
mutex=0x55a03da40a00, deadline=...) at thread/qwaitcondition_unix.cpp:225
#5  0x7fd168154fe0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7fd168158cfe in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7fd1681541a2 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7fd168158d59 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7fd1681541a2 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#10 0x7fd168156c53 in ThreadWeaver::Thread::run() () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#11 0x7fd1941bc45c in QThreadPrivate::start(void*) (arg=0x55a03534e200) at
thread/qthread_unix.cpp:329
#12 0x7fd193106609 in start_thread (arg=) at
pthread_create.c:477
#13 0x7fd193e3a293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 20 (Thread 0x7fd13ca50700 (LWP 11467)):
#0  futex_wait_cancelable (private=, expected=0,

[kwin] [Bug 443224] Kwin puts titlebar wrongly in some java apps

2021-11-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=443224

--- Comment #5 from lucbo...@gmail.com ---
Created attachment 143431
  --> https://bugs.kde.org/attachment.cgi?id=143431=edit
Dbeaver CE

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

[plasmashell] [Bug 437808] Desktop freezes after sleep on fresh upgrade to Fedora 34/KDE

2021-11-10 Thread gfunk
https://bugs.kde.org/show_bug.cgi?id=437808

gfunk  changed:

   What|Removed |Added

 CC||trist...@posteo.net

--- Comment #15 from gfunk  ---
For me, on Arch, this is now fixed in Plasma 5.23.3

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

[plasmashell] [Bug 445302] Detect and notify for missing drivers or codecs

2021-11-10 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=445302

Nate Graham  changed:

   What|Removed |Added

   Keywords||usability

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

[plasmashell] [Bug 445302] New: Detect and notify for missing drivers or codecs

2021-11-10 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=445302

Bug ID: 445302
   Summary: Detect and notify for missing drivers or codecs
   Product: plasmashell
   Version: 5.23.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: n...@kde.org
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Some distros ship with media codecs out of the box or offer an option to
install them during installation... and some don't. Some distros make it easy
to install the drivers for your NVIDIA GPU during installation... and some
don't. The result is a fragmented experience containing landmines for new users
who don't yet know the intricacies of these sorts of things. These users will
tend to blame KDE for the problems because they don't know that it's their
distro's fault, or even their own fault.

Plasma could detect these kinds of conditions on first boot or after a system
upgrade, and show a notification telling the user about it, with a nice
friendly button they can click on to fix it. The button could open Discover to
the right page for media codecs or the NVIDIA GPU drivers or whatever.

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

[KSystemLog] [Bug 445301] New: blue text not well readable in dark mode.

2021-11-10 Thread Jonas
https://bugs.kde.org/show_bug.cgi?id=445301

Bug ID: 445301
   Summary: blue text not well readable in dark mode.
   Product: KSystemLog
   Version: 21.08.2
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: nicolas.ternis...@gmail.com
  Reporter: jonas...@gmail.com
  Target Milestone: ---

Created attachment 143430
  --> https://bugs.kde.org/attachment.cgi?id=143430=edit
screenshot displaying badly readable text on dark background

I'm using kubuntu 21.10 with the breeze dark theme, and the blue text in the
log view is very hard to read on my screen. see attached screenshot. 

would it be possible to either use a shade of blue that is well visible on both
light and dark background, or have different color themes depending on light vs
dark mode?

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

[systemsettings] [Bug 445136] Crashes in KCMKWinDecoration::borderSizeIndexToString() while setting theme

2021-11-10 Thread Michael
https://bugs.kde.org/show_bug.cgi?id=445136

--- Comment #5 from Michael  ---
Thank you for the assistance!

On Wed, Nov 10, 2021 at 12:42 PM Nate Graham 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=445136
>
> Nate Graham  changed:
>
>What|Removed |Added
>
> 
>  Status|NEEDSINFO   |RESOLVED
>  Resolution|WAITINGFORINFO  |WORKSFORME
>
> --- Comment #4 from Nate Graham  ---
> OK, sorry you didn't have a better experience! Closing as I can't
> reproduce the
> issue, and it sounds like like you won't be in a position to test it again.
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[ksysguard] [Bug 442043] ksystemstats: NVMe drive temperature is no longer reported (sensor missing)

2021-11-10 Thread Luca Beltrame
https://bugs.kde.org/show_bug.cgi?id=442043

Luca Beltrame  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Luca Beltrame  ---
Looks fixed with latest master (not sure if it also applies to stable). Both my
NVMe SSDs are shown and with temperature readings.

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

[valgrind] [Bug 445300] New: [PATCH] Fix building tests with Musl

2021-11-10 Thread Alyssa Ross
https://bugs.kde.org/show_bug.cgi?id=445300

Bug ID: 445300
   Summary: [PATCH] Fix building tests with Musl
   Product: valgrind
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: h...@alyssa.is
  Target Milestone: ---

Created attachment 143428
  --> https://bugs.kde.org/attachment.cgi?id=143428=edit
Patches that fix make check on Musl.

SUMMARY

Test suite could not be built on Musl.

STEPS TO REPRODUCE
1. Run ./configure && make && make check on a Musl-based system. 

OBSERVED RESULT

Various compilation errors.

EXPECTED RESULT

Make finishes successfully.

SOFTWARE/OS VERSIONS
Linux: 5.14.15
Musl: 1.2.2 

ADDITIONAL INFORMATION

Attached are three patches in mbox format.  After applying all of them, I was
able to make check successfully.

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

[gwenview] [Bug 441121] gwenview crashes when opening .jpg in X11 Session (wayland not possible on graphics card)

2021-11-10 Thread Jan Rathmann
https://bugs.kde.org/show_bug.cgi?id=441121

--- Comment #15 from Jan Rathmann  ---
For me this seems to be fixed under Kubuntu 21.10 with Gwenview 21.08.2 from
kubuntu-backports-ppa.

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

[frameworks-kio] [Bug 445299] Dolphin and Disks & Devices applet report capacity of removable device as '0 B' after formatting without label

2021-11-10 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=445299

Patrick Silva  changed:

   What|Removed |Added

Summary|Dolphin and Disks & Devices |Dolphin and Disks & Devices
   |applet report capacity of   |applet report capacity of
   |removable device as '0 B'   |removable device as '0 B'
   |after formatting|after formatting without
   ||label

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

[frameworks-kio] [Bug 445299] New: Dolphin and Disks & Devices applet report capacity of removable device as '0 B' after formatting

2021-11-10 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=445299

Bug ID: 445299
   Summary: Dolphin and Disks & Devices applet report capacity of
removable device as '0 B' after formatting
   Product: frameworks-kio
   Version: 5.87.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kio-bugs-n...@kde.org
  Reporter: bugsefor...@gmx.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

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

STEPS TO REPRODUCE
1. open Dolphin
2. connect a removable storage device to usb port (I use a flash drive)
3. format your device without any label (I used Gnome Disks to format my device
with ntfs file system)
4.  observe the capacity of your device in the Places panel of Dolphin
5. click on Disks & Devices applet in system tray and observe the capacity of
your device there

OBSERVED RESULT
as we can see in the attached screenshot, device capacity is incorrectly
reported as '0 B' in the Places panel of Dolphin and Disks & Devices applet

EXPECTED RESULT
the capacity of a device should always be correctly reported

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Graphics Platform: Wayland

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

[kwin] [Bug 445298] [Wayland] unplugging a screen causes some applications to use 100% CPU load

2021-11-10 Thread Germano Massullo
https://bugs.kde.org/show_bug.cgi?id=445298

--- Comment #2 from Germano Massullo  ---
Created attachment 143426
  --> https://bugs.kde.org/attachment.cgi?id=143426=edit
GDB Konsole

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

[kwin] [Bug 445298] [Wayland] unplugging a screen causes some applications to use 100% CPU load

2021-11-10 Thread Germano Massullo
https://bugs.kde.org/show_bug.cgi?id=445298

--- Comment #1 from Germano Massullo  ---
Created attachment 143425
  --> https://bugs.kde.org/attachment.cgi?id=143425=edit
GDB KeepassXC

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

[kwin] [Bug 445298] New: [Wayland] unplugging a screen causes some applications to use 100% CPU load

2021-11-10 Thread Germano Massullo
https://bugs.kde.org/show_bug.cgi?id=445298

Bug ID: 445298
   Summary: [Wayland] unplugging a screen causes some applications
to use 100% CPU load
   Product: kwin
   Version: 5.23.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: germano.massu...@gmail.com
  Target Milestone: ---

My laptop when it's connected to an external screen, disables its screen to
just let me use the external monitor.
The external monitor has various inputs and I have connected various computers
to it.
As soon I selected another video input on the external screen, my laptop
started to behave in a strange way, for example it acted like if the screen has
been unplugged. Moreover the most important thing is that various applications
crashed (Firefox Wayland) or started to use 100% CPU load (Konsole, KeepassXC).
I attach GDB trace of Konsole and KeepassXC while using 100% CPU load

plasma 5.23.2
KDE Frameworks 5.87.0
Qt 5.15.2

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

[plasmashell] [Bug 445286] Hide the on-screen volume adjustment indicator when adjusting from system tray with mouse scroll wheel

2021-11-10 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=445286

--- Comment #3 from Nate Graham  ---
> The user has to click on the volume icon (where the visual indicator already 
> exists)
> and then use the mouse scroll wheel up or down. 
They do not. It is enough to roll the wheel while hovering over the tray icon;
no need to click on it first.

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

[gwenview] [Bug 441121] gwenview crashes when opening .jpg in X11 Session (wayland not possible on graphics card)

2021-11-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=441121

--- Comment #14 from k_d_hud...@yahoo.com ---
Created attachment 143424
  --> https://bugs.kde.org/attachment.cgi?id=143424=edit
New crash information added by DrKonqi

gwenview (20.12.3) using Qt 5.15.2

- What I was doing when the application crashed:

This is a little bizarre. I encountered this while rapidly scrolling through
thumbnails in a directory. One particular image reliably crashes QwenView, but
it isn't the image itself because QwenView opens the image just fine if I copy
it to another directory. If I copy just a few of the images to another
directory, QwenView also works just fine. The directory contents are available
online to replicate this issue. I downloaded and replicated again just to be
sure.

The directory contents are available online inside this archive:
https://downloads.open-tx.org/2.3/release/sdcard/opentx-t16/sdcard-480x272-2.3V0025.zip.
The directory is IMAGES. The image QwenView crashes on is IMAGES/P51.jpg.

To replicate, extract the archive, and start clicking through the images. I
double clicked on in Dolphin to start.

The crash can be reproduced every time.

-- Backtrace (Reduced):
#4  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
#5  0x7f191f393864 in __GI_abort () at abort.c:79
[...]
#12 0x7f191f00a92d in Exiv2::Xmpdatum::write(std::ostream&, Exiv2::ExifData
const*) const () from /lib/x86_64-linux-gnu/libexiv2.so.27
#13 0x7f1921515250 in
Gwenview::ImageMetaInfoModel::setExiv2Image(Exiv2::Image const*) () from
/lib/x86_64-linux-gnu/libgwenviewlib.so.5
#14 0x7f19214dfa70 in
Gwenview::Document::setExiv2Image(std::unique_ptr >) () from
/lib/x86_64-linux-gnu/libgwenviewlib.so.5

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

[gwenview] [Bug 441121] gwenview crashes when opening .jpg in X11 Session (wayland not possible on graphics card)

2021-11-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=441121

k_d_hud...@yahoo.com changed:

   What|Removed |Added

 CC||k_d_hud...@yahoo.com

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

[plasma-systemmonitor] [Bug 445297] Sensor system monitor prints NVMe drive temperature of ~50°C in text but draws graph at absolute zero / 0K / -273°C

2021-11-10 Thread Dennis Schridde
https://bugs.kde.org/show_bug.cgi?id=445297

--- Comment #1 from Dennis Schridde  ---
P.S. I will need some instructions on what information you will need to debug
this.

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

[plasma-systemmonitor] [Bug 445297] New: Sensor system monitor prints NVMe drive temperature of ~50°C in text but draws graph at absolute zero / 0K / -273°C

2021-11-10 Thread Dennis Schridde
https://bugs.kde.org/show_bug.cgi?id=445297

Bug ID: 445297
   Summary: Sensor system monitor prints NVMe drive temperature of
~50°C in text but draws graph at absolute zero / 0K /
-273°C
   Product: plasma-systemmonitor
   Version: 5.23.3
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: devuran...@gmx.net
CC: ahiems...@heimr.nl, plasma-b...@kde.org
  Target Milestone: ---

Created attachment 143423
  --> https://bugs.kde.org/attachment.cgi?id=143423=edit
screenshot of NVMe drive temperature sensor widget

SUMMARY

The graph of NVMe drive temperature sensors shows wrong temperature while the
text shows the correct one (at least something reasonable).

STEPS TO REPRODUCE
1. Have NVMe drive with temperature sensor
2. Set up Plasma applet to monitor it
3. Observe difference between graph and text

OBSERVED RESULT

See attached screenshot of two NVMe drive temperature sensors: The texts say
"47,9°C" and "60,9°C", but the only line in the graph is drawn at absolute zero
/ 0K / -273°C.

EXPECTED RESULT

If the sensor was reporting buggy data, I would at least expect KDE Plasma to
render it consistently in text and graph.

SOFTWARE/OS VERSIONS
Operating System: Gentoo Linux 2.8
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.15.1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × AMD Ryzen 5 2400G with Radeon Vega Graphics
Memory: 13,5 GiB of RAM
Graphics Processor: AMD Radeon™ Vega 11 Graphics

ADDITIONAL INFORMATION

Portage 3.0.28 (python 3.9.8-final-0,
default/linux/amd64/17.1/desktop/plasma/systemd, gcc-11.2.0, glibc-2.33-r7,
5.15.1 x86_64)
=
 System Settings
=
System uname:
Linux-5.15.1-x86_64-AMD_Ryzen_5_2400G_with_Radeon_Vega_Graphics-with-glibc2.33
KiB Mem:14186384 total,742112 free
KiB Swap:7092220 total,   6215480 free
Timestamp of repository gentoo: Wed, 10 Nov 2021 06:45:01 +
Head commit of repository gentoo: 745a5e2a181fbc3b6c4556d209c2913e551ab8fb
Timestamp of repository haskell: Tue, 09 Nov 2021 10:53:03 +
Head commit of repository haskell: c6d68db0123e1d33e466e7193d4f8809ecf7ef1e

Head commit of repository local: 2d87deda70a5e0167d8ba10d68067821a1ce73ae

sh bash 5.1_p8
ld GNU ld (Gentoo 2.37_p1 p0) 2.37
ccache version 4.4.2 [disabled]
app-shells/bash:  5.1_p8::gentoo
dev-java/java-config: 2.3.1::gentoo
dev-lang/perl:5.34.0-r5::gentoo
dev-lang/python:  2.7.18_p13::gentoo, 3.9.8::gentoo, 3.10.0_p1::gentoo
dev-lang/rust:1.56.1::gentoo
dev-util/ccache:  4.4.2::gentoo
dev-util/cmake:   3.21.4::gentoo
sys-apps/baselayout:  2.8::gentoo
sys-apps/sandbox: 2.29::gentoo
sys-devel/autoconf:   2.13-r1::gentoo, 2.71-r1::gentoo
sys-devel/automake:   1.13.4-r2::gentoo, 1.16.5::gentoo
sys-devel/binutils:   2.37_p1::gentoo
sys-devel/gcc:11.2.0::gentoo
sys-devel/gcc-config: 2.4::gentoo
sys-devel/libtool:2.4.6-r6::gentoo
sys-devel/make:   4.3::gentoo
sys-kernel/linux-headers: 5.14::gentoo (virtual/os-headers)
sys-libs/glibc:   2.33-r7::gentoo
Repositories:

gentoo
location: /var/cache/portage/gentoo
sync-type: rsync
sync-uri: rsync://rsync.de.gentoo.org/gentoo-portage
priority: -1000
sync-rsync-verify-metamanifest: yes
sync-rsync-extra-opts: --new-compress
sync-rsync-verify-max-age: 24
sync-rsync-verify-jobs: 1

haskell
location: /var/db/repos/haskell
sync-type: git
sync-uri: https://github.com/gentoo-mirror/haskell.git
masters: gentoo

crossdev
location: /var/cache/portage/crossdev
masters: gentoo
priority: 100

local
location: /var/cache/portage/local
sync-type: git
sync-uri: https://github.com/devurandom/gentoo-overlay.git
masters: gentoo
priority: 1000

ACCEPT_KEYWORDS="amd64 ~amd64"
ACCEPT_LICENSE="@FREE"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-pipe -O2 -march=znver1"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/lib64/libreoffice/program/sofficerc /usr/share/config
/usr/share/gnupg/qualified.txt /usr/share/maven-bin-3.8/conf"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d
/etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild
/etc/sandbox.d /etc/terminfo /etc/texmf/language.dat.d
/etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c"
CXXFLAGS="-pipe -O2 -march=znver1"
DISTDIR="/var/cache/portage/distfiles"
EMERGE_DEFAULT_OPTS="--nospinner"
ENV_UNSET="CARGO_HOME DBUS_SESSION_BUS_ADDRESS DISPLAY GOBIN GOPATH PERL5LIB
PERL5OPT PERLPREFIX PERL_CORE PERL_MB_OPT PERL_MM_OPT 

[krita] [Bug 445296] New: Brush Stroke with "v" mypaint brush

2021-11-10 Thread Hugo
https://bugs.kde.org/show_bug.cgi?id=445296

Bug ID: 445296
   Summary: Brush Stroke with "v" mypaint brush
   Product: krita
   Version: 5.0.0-beta2
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Brush engines
  Assignee: krita-bugs-n...@kde.org
  Reporter: hgmes...@gmail.com
  Target Milestone: ---

SUMMARY
MyPaint brushes using the line tool on Brush (pressing "V" to make line stroke)
doesn't end on the end point.

STEPS TO REPRODUCE
1. select a pencil with Mypaint engine on it
2. Make a stroke with "V"
3. Select a pencil with old version and try the same

OBSERVED RESULT
Brush stroke doesn't end on the cursor

EXPECTED RESULT
Brush stroke should end on the cursor

SOFTWARE/OS VERSIONS
Windows: Yes
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.

[ksysguard] [Bug 442043] ksystemstats: NVMe drive temperature is no longer reported (sensor missing)

2021-11-10 Thread Dennis Schridde
https://bugs.kde.org/show_bug.cgi?id=442043

Dennis Schridde  changed:

   What|Removed |Added

 CC||devuran...@gmx.net

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

[frameworks-kio] [Bug 445294] Dolphin and Disks & Devices applet does not clearly say what is happening when safe device removal fails due to incomplete file copy. File system is sometimes corrupted w

2021-11-10 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=445294

Patrick Silva  changed:

   What|Removed |Added

Summary|Dolphin and Disks & Devices |Dolphin and Disks & Devices
   |applet do not say clearing  |applet does not clearly say
   |what is happening when safe |what is happening when safe
   |removing device fails due   |device removal fails due to
   |to incomplete file copy.|incomplete file copy. File
   |File system is sometimes|system is sometimes
   |corrupted when I try to |corrupted when I try to
   |access the device while |access the device while
   |safe removing is in |safe removing is in
   |progress, causing data  |progress, causing data
   |loss.   |loss.

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

[muon] [Bug 445295] New: sorting by installed size

2021-11-10 Thread Martin Zbořil
https://bugs.kde.org/show_bug.cgi?id=445295

Bug ID: 445295
   Summary: sorting by installed size
   Product: muon
   Version: 5.8.0
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: muon
  Assignee: unassigned-b...@kde.org
  Reporter: kdebugzi...@perfugium.net
CC: echidna...@kubuntu.org, silh...@gmail.com
  Target Milestone: ---

SUMMARY
great replacement of synaptic package manager. in fact, i think it's better,
thank you!
but sorting by Installed Size (clicking on it)  doesn't change order of
installed packages, and it could have been useful feature.. ?

STEPS TO REPRODUCE
1. select 'by status' and pick Installed
2. click on Installed Size and observe no change in packages order.
3. write a report like this :)

OBSERVED RESULT
no change happens when trying to sort installed packages by Installed Size (or
by Available version, which wouldn't be useful anyway)

EXPECTED RESULT
sorting by size so i can make some space on my root partition which is only
64GB.. i (naively) thought that it would have been enough when i formatted this
disk couple years ago..

SOFTWARE/OS VERSIONS
Windows: none
macOS: also none
Linux/KDE Plasma:
(available in About System)
Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.7
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
Kernel Version: 5.4.0-90-generic
OS Type: 64-bit

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

  1   2   3   4   >