[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History

[Philippe ROUBACH]

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

--- Comment #38 from Philippe ROUBACH  ---
same problem with

Samsung S2 Plus
LineageOS 14.1 (android 7.1.2)
kdeconnect android 1.13.6
google messages

openSuse Leap 15.1 Argon
kdeconnect kde 1.4

kde apps 19.12.1
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.0

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

[kwin] [Bug 416368] Wobbly windows effect doesn't work anymore

[Michael K.]

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

Michael K.  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #3 from Michael K.  ---
Don't know why and how but compositor was off!
Thank you!

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

[kmymoney] [Bug 416410] New: Add a recuring transaction - loss of input if we forget the source account

[Philippe Debrabant]

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

Bug ID: 416410
   Summary: Add a recuring transaction - loss of input if we
forget the source account
   Product: kmymoney
   Version: 5.0.7
  Platform: Mint (Ubuntu based)
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: debrabant.phili...@free.fr
  Target Milestone: ---

SUMMARY

STEPS TO REPRODUCE
1. Add a recuring transaction.
2. Enter frequencee, payee, category, date and amount. Don't select the source
account.
3. Validate

OBSERVED RESULT
Once we have validate the dialog box, there's the normal message (french
config) : Impossible d'ajouter l'opération récurrente : Cannot add split that
does not contain an account reference
/.../kmymoney/kmymoney-5.0.7/kmymoney/mymoney/mymoneytransaction.cpp:214

Once validate the error message, the dialog box is re-displayed but all the
input fields are cleared.

EXPECTED RESULT

Once validate the error message, the dialog box is re-displayed with all the
input fields with their user value.


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.

[kmail2] [Bug 416403] During account wizard using @protonmail.com, get "Kmail could not convert value of setting 'Authentication' to required type"

[Laurent Montel]

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

--- Comment #2 from Laurent Montel  ---
Git commit 83ab5326a3d605aaf99b58141ef688a938aa4e12 by Laurent Montel.
Committed on 18/01/2020 at 07:24.
Pushed by mlaurent into branch 'release/19.12'.

Add more debug info

M  +1-0src/resource.cpp

https://commits.kde.org/kmail-account-wizard/83ab5326a3d605aaf99b58141ef688a938aa4e12

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

[neon] [Bug 416361] When is the qt bug fix QTBUG-77826 where certain applications cannot be operated by wacomset added?

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

   Assignee|jazzv...@gmail.com  |neon-b...@kde.org
Product|wacomtablet |neon
  Component|general |general
 CC||j...@jriddell.org,
   ||neon-b...@kde.org,
   ||sit...@kde.org

--- Comment #4 from Christoph Feck  ---
Reassigning to Neon developers. They might have an influence in Qt updates.

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

[plasmashell] [Bug 416409] New: Plasma crash while using

[Tim Richardson]

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

Bug ID: 416409
   Summary: Plasma crash while using
   Product: plasmashell
   Version: 5.17.5
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: t...@tim-richardson.net
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.17.5)

Qt Version: 5.13.2
Frameworks Version: 5.66.0
Operating System: Linux 5.3.13-custom x86_64
Distribution: KDE neon User Edition 5.17

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

had three terminals open, was doing vi editing in one of them. Chromium running
in another. I don't see any link between what I was doing and the crash

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8f85f52e40 (LWP 3144))]

Thread 14 (Thread 0x7f8f03d82700 (LWP 4003)):
#0  0x7f8f7ccc89f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55de590f2b34) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f8f7ccc89f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55de590f2ae0, cond=0x55de590f2b08) at pthread_cond_wait.c:502
#2  0x7f8f7ccc89f3 in __pthread_cond_wait (cond=0x55de590f2b08,
mutex=0x55de590f2ae0) at pthread_cond_wait.c:655
#3  0x7f8f7fd99aeb in QWaitConditionPrivate::wait(QDeadlineTimer)
(deadline=..., this=0x55de590f2ae0) at thread/qwaitcondition_unix.cpp:146
#4  0x7f8f7fd99aeb in QWaitCondition::wait(QMutex*, QDeadlineTimer)
(this=, mutex=0x55de58f26690, deadline=...) at
thread/qwaitcondition_unix.cpp:225
#5  0x7f8f7fd99df9 in QWaitCondition::wait(QMutex*, unsigned long)
(this=this@entry=0x55de58f26698, mutex=mutex@entry=0x55de58f26690,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208
#6  0x7f8f83db9ec8 in QSGRenderThreadEventQueue::takeEvent(bool)
(wait=true, this=0x55de58f26688) at scenegraph/qsgthreadedrenderloop.cpp:245
#7  0x7f8f83db9ec8 in QSGRenderThread::processEventsAndWaitForMore()
(this=this@entry=0x55de58f26610) at scenegraph/qsgthreadedrenderloop.cpp:710
#8  0x7f8f83dba2fa in QSGRenderThread::run() (this=0x55de58f26610) at
scenegraph/qsgthreadedrenderloop.cpp:739
#9  0x7f8f7fd92b52 in QThreadPrivate::start(void*) (arg=0x55de58f26610) at
thread/qthread_unix.cpp:360
#10 0x7f8f7ccc26db in start_thread (arg=0x7f8f03d82700) at
pthread_create.c:463
#11 0x7f8f7f68f88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 13 (Thread 0x7f8f1985e700 (LWP 3588)):
#0  0x7f8f7ccc89f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55de5737d804) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f8f7ccc89f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55de5737d7b0, cond=0x55de5737d7d8) at pthread_cond_wait.c:502
#2  0x7f8f7ccc89f3 in __pthread_cond_wait (cond=0x55de5737d7d8,
mutex=0x55de5737d7b0) at pthread_cond_wait.c:655
#3  0x7f8f7fd99aeb in QWaitConditionPrivate::wait(QDeadlineTimer)
(deadline=..., this=0x55de5737d7b0) at thread/qwaitcondition_unix.cpp:146
#4  0x7f8f7fd99aeb in QWaitCondition::wait(QMutex*, QDeadlineTimer)
(this=, mutex=0x55de57388ab0, deadline=...) at
thread/qwaitcondition_unix.cpp:225
#5  0x7f8f7fd99df9 in QWaitCondition::wait(QMutex*, unsigned long)
(this=this@entry=0x55de57388ab8, mutex=mutex@entry=0x55de57388ab0,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208
#6  0x7f8f83db9ec8 in QSGRenderThreadEventQueue::takeEvent(bool)
(wait=true, this=0x55de57388aa8) at scenegraph/qsgthreadedrenderloop.cpp:245
#7  0x7f8f83db9ec8 in QSGRenderThread::processEventsAndWaitForMore()
(this=this@entry=0x55de57388a30) at scenegraph/qsgthreadedrenderloop.cpp:710
#8  0x7f8f83dba2fa in QSGRenderThread::run() (this=0x55de57388a30) at
scenegraph/qsgthreadedrenderloop.cpp:739
#9  0x7f8f7fd92b52 in QThreadPrivate::start(void*) (arg=0x55de57388a30) at
thread/qthread_unix.cpp:360
#10 0x7f8f7ccc26db in start_thread (arg=0x7f8f1985e700) at
pthread_create.c:463
#11 0x7f8f7f68f88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 12 (Thread 0x7f8f1c617700 (LWP 3584)):
#0  0x7f8f7f682bf9 in __GI___poll (fds=0x7f8f14003ce0, nfds=1,
timeout=2940036) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f8f797fb5c9 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f8f797fb6dc in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f8f7ffd5b9b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f8f14000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f8f7ff7606a in

[kig] [Bug 416037] When I use python scripting, kig crash select the exit menu entry instead closing

[Maurizio Paolini]

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

--- Comment #4 from Maurizio Paolini  ---
Git commit faec9ac0f6f73e312dc051ce34eaf3154d456e96 by Maurizio Paolini.
Committed on 18/01/2020 at 05:47.
Pushed by paolini into branch 'master'.

Going back to original Py_Finalize() to maintain compatibility with pithon2 and
earlier versions of python3

Reviewed By: wbauer
Differential Revision: https://phabricator.kde.org/D26550

M  +2-1scripting/python_scripter.cc

https://commits.kde.org/kig/faec9ac0f6f73e312dc051ce34eaf3154d456e96

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

[krita] [Bug 415788] Transform mask cause file layer to jump all over workplace

[vanyossi]

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

vanyossi  changed:

   What|Removed |Added

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

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

[krita] [Bug 415520] Failed to change language of krita (steam version) on Linux

[bugzilla_noreply]

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

srk888...@qq.com changed:

   What|Removed |Added

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

--- Comment #3 from srk888...@qq.com ---
(In reply to Boudewijn Rempt from comment #1)
> Hi,
> 
> If you change other settings, do they stay changed, or are those reset as
> well?

It seems that everything works well except the language setting.

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

[lattedock] [Bug 414064] Latte dock doesn't start when booting into a single screen from a dual screen configuration

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #6 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now 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

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

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

[unknown] [Bug 414677] Frames bug out when played

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #3 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now 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

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

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

[krita] [Bug 415832] Krita stops responding

[Bug Janitor Service]

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

--- Comment #2 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.

[krita] [Bug 415520] Failed to change language of krita (steam version) on Linux

[Bug Janitor Service]

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

--- Comment #2 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.

[kdenlive] [Bug 411145] Extract Timeline Zone does not work (Shift-X)

[Bug Janitor Service]

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

--- 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.

[plasmashell] [Bug 362206] System tray containment does not have a screen associated with it

[Bug Janitor Service]

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

--- Comment #5 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.

[Breeze] [Bug 376430] Some scrollbars unusable with wacom

[Bug Janitor Service]

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

--- Comment #5 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 365967] Overlapping icons on the system tray with 3rd-party weather widget

[Bug Janitor Service]

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

--- Comment #10 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.

[lattedock] [Bug 407533] Zoom on hover does not always register cursor movement correctly

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #24 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now 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

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 408665] KDE plasma desktop crash while formatting usb drive to ntfs

[bugzilla_noreply]

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

--- Comment #2 from b.raz...@gmail.com ---
I am currently running kubuntu 19.10, which I think isn't running 5.17 yet.
I'll try formatting a drive when I get a chance and I'll let you know asap.

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

[Discover] [Bug 416408] New: Discover crashed after unlocking screen

[bugzilla_noreply]

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

Bug ID: 416408
   Summary: Discover crashed after unlocking screen
   Product: Discover
   Version: 5.16.5
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: lei...@leinir.dk
  Reporter: b.raz...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

Application: plasma-discover (5.16.5)

Qt Version: 5.12.4
Frameworks Version: 5.62.0
Operating System: Linux 5.3.0-26-generic x86_64
Distribution: Ubuntu 19.10

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

I had just unlocked the lock screen (computer was awake, just locked) and
opened the discover software repository application and used the search bar to
look for some software.  The application began to search for software when the
screen changed to 'please check your connection'. It then hung and crashed.  At
the time I was downloading a large file in Mozilla, so perhaps
bandwidth/latency was an issue.  The problem did not persist afterwards, as I
immediately reopened discover and was able to find the software on the 2nd
attempt.  Not really a priority bug, since I can't seem to reproduce it.

The crash does not seem to be reproducible.

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f023be32680 (LWP 10502))]

Thread 9 (Thread 0x7f01ebfff700 (LWP 10537)):
#0  0x7f023f2ad2c6 in futex_wait_cancelable (private=,
expected=0, futex_word=0x563204a3fde0) at
../sysdeps/unix/sysv/linux/futex-internal.h:80
#1  0x7f023f2ad2c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x563204a3fd90, cond=0x563204a3fdb8) at pthread_cond_wait.c:508
#2  0x7f023f2ad2c6 in __pthread_cond_wait (cond=0x563204a3fdb8,
mutex=0x563204a3fd90) at pthread_cond_wait.c:638
#3  0x7f023fed7def in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f023fed7ee1 in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f0241c547b9 in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7f0241c54a1a in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x7f023fed1cc2 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f023f2a6669 in start_thread (arg=) at
pthread_create.c:479
#9  0x7f023fb56323 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 8 (Thread 0x7f0220a0a700 (LWP 10536)):
#0  0x7f023fb49c2f in __GI___poll (fds=0x7f021000e260, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f023e8dca3e in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f023e8dcb73 in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f02400f06c3 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f024009763b in
QEventLoop::exec(QFlags) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f023fed0a75 in QThread::exec() () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f023fed1cc2 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f023f2a6669 in start_thread (arg=) at
pthread_create.c:479
#8  0x7f023fb56323 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 7 (Thread 0x7f0222e81700 (LWP 10510)):
#0  0x7f023fb49c2f in __GI___poll (fds=0x7f0214194bf0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f023e8dca3e in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f023e8dcb73 in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f02400f06c3 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f024009763b in
QEventLoop::exec(QFlags) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f023fed0a75 in QThread::exec() () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f023fed1cc2 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f023f2a6669 in start_thread (arg=) at
pthread_create.c:479
#8  0x7f023fb56323 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7f0223a81700 (LWP 10509)):
#0  0x7f023fb49c2f in __GI___poll (fds=0x7f021c0029e0, nfds=1,
timeout=9167) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f023e8dca3e in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f023e8dcb73 in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f02400f06c3 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f024009763b in
QEventLoop::exec(QFlags) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f023fed0a75 in QThread::exec() () at

[wacomtablet] [Bug 416361] When is the qt bug fix QTBUG-77826 where certain applications cannot be operated by wacomset added?

[ferweer]

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

--- Comment #3 from ferweer  ---
befor > Is the fix for QTBUG-77826 supported?
Fixed title. I thought I could prevent the same from being posted, but sorry if
this wasn't the right fix

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

[wacomtablet] [Bug 416361] When is the qt bug fix QTBUG-77826 where certain applications cannot be operated by wacomset added?

[ferweer]

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

ferweer  changed:

   What|Removed |Added

Summary|Is the fix for QTBUG-77826  |When is the qt bug fix
   |supported?  |QTBUG-77826 where certain
   ||applications cannot be
   ||operated by wacomset added?

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

[wacomtablet] [Bug 416361] Is the fix for QTBUG-77826 supported?

[ferweer]

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

--- Comment #2 from ferweer  ---
(In reply to Valerii Malov from comment #1)
Thanks for the response. It seems that 19.04 users will not be able to update
at least until the end of January, and it seems better for users using the
kdeneon release to stop updating until it can be confirmed whether it was fixed
on January 21. I will keep an eye on this bug fix.

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

[gwenview] [Bug 334847] When reaching the last image and trying to view next, an unergonomic menu is shown

[ferweer]

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

--- Comment #15 from ferweer  ---
I apologize for posting the duplicate first, sorry. Bug 416367 was added as a
duplicate. 
This continues to happen on both Kubuntu 19.04 and 19.10, and it's surprising
that this has happened for solong.
I will commend those who are working on fixing this. I don't know why the fix
https://phabricator.kde.org/D9039 for this is not yet added to gwenview.
However, a bug ticket may occur until the option is added. I hope that the fix
will be added quickly for those who do this.

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

[dolphin] [Bug 416407] New: RTL: alignment in files view and side menu

[Salem Yaslem]

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

Bug ID: 416407
   Summary: RTL: alignment in files view and side menu
   Product: dolphin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: s...@sy.sa
CC: kfm-de...@kde.org
  Target Milestone: ---

Created attachment 125219
  --> https://bugs.kde.org/attachment.cgi?id=125219=edit
Review issue in dolphin and desktop

EXPECTED RESULT
Text alignment should be in right and icons should be in right beside labels
Example
 |   TEXT | ICON |

And Icons view should start from right to left like in desktop (see
attachments)
Example 
 | file3| file2|file1|
 || file5|file4|

Operating System: KDE neon 5.17
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.66.0
Qt Version: 5.13.2

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

[systemsettings] [Bug 416406] New: RTL: sub menu become on left side of main menu in Settings

[Salem Yaslem]

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

Bug ID: 416406
   Summary: RTL: sub menu become on left side of main menu in
Settings
   Product: systemsettings
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: s...@sy.sa
  Target Milestone: ---

Created attachment 125218
  --> https://bugs.kde.org/attachment.cgi?id=125218=edit
Review issue in Settings

EXPECTED RESULT
Should be in right side

OS VERSIONS
Operating System: KDE neon 5.17
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.66.0
Qt Version: 5.13.2

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

[kmix] [Bug 416405] New: kmix controls won't respond to mouse wheel scroll

[fabio]

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

Bug ID: 416405
   Summary: kmix controls won't respond to mouse wheel scroll
   Product: kmix
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: es...@kde.org
  Reporter: slayer.dasi...@gmail.com
  Target Milestone: ---

SUMMARY
Volume controls will not respond to mouse wheel. 

STEPS TO REPRODUCE
1. click on kmix
2. try to change the volume with the mouse wheel scroll
3. 

OBSERVED RESULT
a sound efect is played but volume levels won't change

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.

[kdeconnect] [Bug 415424] sms send, historic refresh fails

[Simon Redman]

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

--- Comment #6 from Simon Redman  ---
Thank you for taking the time to report this.
Unfortunately this is a known issue with Samsung phones because Samsung has not
complied with the way Android says messages should be stored.

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

[kdenlive] [Bug 416404] New: Kdenlive parsing error on opening certain MP4 files

[Sandor]

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

Bug ID: 416404
   Summary: Kdenlive parsing error on opening certain MP4 files
   Product: kdenlive
   Version: 19.12.1
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: life.san...@gmail.com
  Target Milestone: ---

Created attachment 125217
  --> https://bugs.kde.org/attachment.cgi?id=125217=edit
Opening Mp4 file from nautilus context menu.

SUMMARY


STEPS TO REPRODUCE
1. Opening Mp4 file from nautilus context menu.
2. Opening same Mp4 file in project bin says "Cannot open file"
3. Same files can be opened in any other video player (VLC, Olive etc.)

OBSERVED RESULT
Files are coming from security camera ftp upload. About 5-10% of the files do
produce the same error. Tried to change file size or saving the files at other
ftp location, the randomness did not change.

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.

[kdeconnect] [Bug 409814] Reply-to SMS box is incorrectly opened when a single-sign-on SMS with a "Copy" button is clicked

[Simon Redman]

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

Simon Redman  changed:

   What|Removed |Added

 CC||matejm98m...@gmail.com

--- Comment #2 from Simon Redman  ---
*** Bug 416326 has been marked as a duplicate of this bug. ***

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

[kdeconnect] [Bug 416326] 'Reply' and 'Like' buttons have switched functionality

[Simon Redman]

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

Simon Redman  changed:

   What|Removed |Added

   Assignee|si...@ergotech.com  |albertv...@gmail.com
  Component|messaging-application   |common

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

[kdeconnect] [Bug 416326] 'Reply' and 'Like' buttons have switched functionality

[Simon Redman]

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

Simon Redman  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #2 from Simon Redman  ---
Thank you for taking the time to report this. It's something I noticed awhile
ago but I guess it hasn't been looked in to yet.

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

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

[krunner] [Bug 414804] Krunner does not reliably find windows

[Luke-Jr]

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

Luke-Jr  changed:

   What|Removed |Added

 CC||luke-jr+kdeb...@utopios.org

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

[krunner] [Bug 416062] The Windows plugin in KRunner stoped working after upgrading from 19.04->19.10

[Luke-Jr]

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

--- Comment #4 from Luke-Jr  ---
Probable duplicate of #414804

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

[krunner] [Bug 416062] The Windows plugin in KRunner stoped working after upgrading from 19.04->19.10

[Luke-Jr]

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

Luke-Jr  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||luke-jr+kdeb...@utopios.org
 Status|REPORTED|CONFIRMED

--- Comment #3 from Luke-Jr  ---
Confirmed on Gentoo. Also still affects 5.66.0.

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

[kmail2] [Bug 416403] During account wizard using @protonmail.com, get "Kmail could not convert value of setting 'Authentication' to required type"

[bugzilla_noreply]

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

--- Comment #1 from snar...@protonmail.com ---
Note that it seems this may not be limited to ProtonMail and may be a recent
bug. A search during my efforts to resolve prior to filing the bug I came
across this from two days ago:
https://forum.manjaro.org/t/kmail-account-setup-fails-on-authentication/119483

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

[kdeconnect] [Bug 415531] KDE Connect mistakenly thinks a conversation is a group if the latest message was a received RCS message

[Simon Redman]

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

--- Comment #1 from Simon Redman  ---
On pondering, I'm pretty sure this should be resolved in the Android app by
checking for duplicate addresses when collecting those for the conversation

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

[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History

[Simon Redman]

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

Simon Redman  changed:

   What|Removed |Added

 CC||philippe.roub...@free.fr

--- Comment #37 from Simon Redman  ---
*** Bug 415424 has been marked as a duplicate of this bug. ***

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

[kdeconnect] [Bug 415424] sms send, historic refresh fails

[Simon Redman]

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

Simon Redman  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED
 CC||si...@ergotech.com

--- Comment #5 from Simon Redman  ---


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

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

[kdeconnect] [Bug 415424] sms send, historic refresh fails

[Simon Redman]

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

Simon Redman  changed:

   What|Removed |Added

   Assignee|albertv...@gmail.com|si...@ergotech.com
  Component|common  |messaging-application

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

[kmail2] [Bug 416403] New: During account wizard using @protonmail.com, get "Kmail could not convert value of setting 'Authentication' to required type"

[bugzilla_noreply]

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

Bug ID: 416403
   Summary: During account wizard using @protonmail.com, get
"Kmail could not convert value of setting
'Authentication' to required type"
   Product: kmail2
   Version: 5.13.1
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: snar...@protonmail.com
  Target Milestone: ---

Created attachment 125216
  --> https://bugs.kde.org/attachment.cgi?id=125216=edit
Screenshot of error

SUMMARY


STEPS TO REPRODUCE
1. Get paying ProtonMail account (7 day trial is possible), install
ProtonBridge via AUR or other means, initialize Bridge 
2. Launch Account Wizard in Kmail via Settings > Add Account
3. Enter name, @protonmail.com email address, and the **Bridge** password (not
the ProtonMail password)
4. Hit 'next' on Secure you Communication'
5. On 'Failed to set up account' screen click 'Details'

OBSERVED RESULT

Step 5 should show an error message "Kmail could not convert value of setting
'Authentication' to required type", proceeds not to add IMAP instance (see
screenshot)



EXPECTED RESULT

Account gets setup, folders start synchronizing, etc

SOFTWARE/OS VERSIONS

Operating System: Manjaro Linux 
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.0
Kernel Version: 5.4.12-1-MANJARO
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz
Memory: 62.8 GiB of RAM


ADDITIONAL INFORMATION

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

[kdeconnect] [Bug 414894] kdeconnectd segfaults in Device::name() when I try to pair my phone

[Nate Graham]

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

--- Comment #3 from Nate Graham  ---
I did; no help. :(

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

[i18n] [Bug 416402] New: dolphin: missing translations

[bugzilla_noreply]

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

Bug ID: 416402
   Summary: dolphin: missing translations
   Product: i18n
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: fr
  Assignee: kde-francoph...@kde.org
  Reporter: grouchomarx...@gmail.com
CC: an...@kde.org
  Target Milestone: ---

Hello,
some menu entries have a translation but they appear in English.
For example "show previews", "show additional informations", "show panels",
"Add 'x' to place", ...

It seems they are all tagged as "fuzzy". Maybe it is the issue.

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

[valgrind] [Bug 416387] finit_module and bpf syscalls are unhandled on arm64

[Mark Wielaard]

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

Mark Wielaard  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||m...@klomp.org
 Resolution|--- |FIXED

--- Comment #1 from Mark Wielaard  ---
Thanks, looks correct. Applied to git master:

commit 7d4071fe8530fa1c217bb775b0e19fd97d871502
Author: Alexandra Hajkova 
Date:   Fri Jan 17 06:59:11 2020 -0500

arm64: hook up finit_module and bpf syscalls

This fixes "WARNING: unhandled arm64-linux syscall" in
delete_module01 and bpf_prog01 tests in the LTP test suite.

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

[systemsettings] [Bug 416397] After I remove the shortcut to lock the screen via standalone "Screen locking" KCM, System Settings started to crash every time I double-click on "Workspace behavior"

[Patrick Silva]

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

Patrick Silva  changed:

   What|Removed |Added

Summary|After I remove the shortcut |After I remove the shortcut
   |to lock the screen via  |to lock the screen via
   |standalone "Screen locking" |standalone "Screen locking"
   |KCM, System Settings|KCM, System Settings
   |atarted to crash every time |started to crash every time
   |I double-click on   |I double-click on
   |"Workspace behavior"|"Workspace behavior"

--- Comment #2 from Patrick Silva  ---
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff7c5061100 (LWP 6622))]

Thread 8 (Thread 0x7ff7a789b700 (LWP 6682)):
#0  0x7ff7c976e42c in read () at /usr/lib/libc.so.6
#1  0x7ff7c5c449f0 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7ff7c5c929e1 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7ff7c5c940c8 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7ff7c5c941f1 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7ff7c9d2dcdc in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7ff79c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7ff7c9cd439c in
QEventLoop::exec(QFlags)
(this=this@entry=0x7ff7a789ad40, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:136
#7  0x7ff7c9af9e62 in QThread::exec() (this=this@entry=0x55f80a1e3ed0) at
../../include/QtCore/../../src/corelib/global/qflags.h:118
#8  0x7ff7c8da0249 in QQmlThreadPrivate::run() (this=0x55f80a1e3ed0) at
/tmp/makepkg/qt5-declarative-debug/src/qtdeclarative-everywhere-src-5.14.0/src/qml/qml/ftw/qqmlthread.cpp:155
#9  0x7ff7c9afafd6 in QThreadPrivate::start(void*) (arg=0x55f80a1e3ed0) at
thread/qthread_unix.cpp:342
#10 0x7ff7c835c4cf in start_thread () at /usr/lib/libpthread.so.0
#11 0x7ff7c977d2d3 in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7ff7ba7fc700 (LWP 6668)):
#0  0x7ff7c8362c45 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7ff7c0e01dcc in  () at /usr/lib/dri/i965_dri.so
#2  0x7ff7c0e019c8 in  () at /usr/lib/dri/i965_dri.so
#3  0x7ff7c835c4cf in start_thread () at /usr/lib/libpthread.so.0
#4  0x7ff7c977d2d3 in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7ff7baffd700 (LWP 6667)):
#0  0x7ff7c8362c45 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7ff7c0e01dcc in  () at /usr/lib/dri/i965_dri.so
#2  0x7ff7c0e019c8 in  () at /usr/lib/dri/i965_dri.so
#3  0x7ff7c835c4cf in start_thread () at /usr/lib/libpthread.so.0
#4  0x7ff7c977d2d3 in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7ff7bb7fe700 (LWP )):
#0  0x7ff7c8362c45 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7ff7c0e01dcc in  () at /usr/lib/dri/i965_dri.so
#2  0x7ff7c0e019c8 in  () at /usr/lib/dri/i965_dri.so
#3  0x7ff7c835c4cf in start_thread () at /usr/lib/libpthread.so.0
#4  0x7ff7c977d2d3 in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7ff7bbfff700 (LWP 6665)):
#0  0x7ff7c8362c45 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7ff7c0e01dcc in  () at /usr/lib/dri/i965_dri.so
#2  0x7ff7c0e019c8 in  () at /usr/lib/dri/i965_dri.so
#3  0x7ff7c835c4cf in start_thread () at /usr/lib/libpthread.so.0
#4  0x7ff7c977d2d3 in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7ff7c2eae700 (LWP 6664)):
#0  0x7ff7c976e42c in read () at /usr/lib/libc.so.6
#1  0x7ff7c5c449f0 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7ff7c5c929e1 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7ff7c5c940c8 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7ff7c5c941f1 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7ff7c9d2dcdc in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7ff7b4000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7ff7c9cd439c in
QEventLoop::exec(QFlags)
(this=this@entry=0x7ff7c2eadd30, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:136
#7  0x7ff7c9af9e62 in QThread::exec() (this=this@entry=0x7ff7ca002080
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
../../include/QtCore/../../src/corelib/global/qflags.h:118
#8  0x7ff7c9f7db28 in QDBusConnectionManager::run() (this=0x7ff7ca002080
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:179
#9  0x7ff7c9afafd6 in QThreadPrivate::start(void*) (arg=0x7ff7ca002080
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:342
#10 0x7ff7c835c4cf in start_thread 

[kdiff3] [Bug 416380] kdiff3 Segmentation fault (core dumped) when used to diff 2 files

[michael]

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

michael  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |REMIND

--- Comment #7 from michael  ---
Thanks f1d89a50afb92cb2596f827f1d0e2e30ebee3d6b will definitely fix the
valgrind warnings inside kdiff3 OptionNum. However, the crash itself seems to
be an issue inside QtWaylandClient.

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

[kwin] [Bug 416401] New: KWin crashes after turning on monitor and unlocking KDE Plasma

[bugzilla_noreply]

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

Bug ID: 416401
   Summary: KWin crashes after turning on monitor and unlocking
KDE Plasma
   Product: kwin
   Version: 5.17.5
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: poperi...@tuta.io
  Target Milestone: ---

Application: kwin_x11 (5.17.5)

Qt Version: 5.14.0
Frameworks Version: 5.66.0
Operating System: Linux 5.4.11-arch1-1 x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:
I turned on my monitor and unlocked KDE Plasma.

- Unusual behavior I noticed:
When clicking on the Steam icon, the window preview was invisible.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f857a88b880 (LWP 664))]

Thread 7 (Thread 0x7f8570ca7700 (LWP 63931)):
#0  0x7f85800d3c45 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f8580f32cc4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt5Core.so.5
#2  0x7f8580f32da2 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#3  0x7f857fb8618b in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f857fb8641b in  () at /usr/lib/libQt5Quick.so.5
#5  0x7f8580f2cfd6 in  () at /usr/lib/libQt5Core.so.5
#6  0x7f85800cd4cf in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f858271b2d3 in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f84cdb88700 (LWP 63930)):
#0  0x7f8582710ae6 in ppoll () at /usr/lib/libc.so.6
#1  0x7f858115bcc3 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f858115d2dd in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f858110639c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f8580f2be62 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f857f7ec249 in QHashedStringRef::indexOf(QChar const&, int) const ()
at /usr/lib/libQt5Qml.so.5
#6  0x7fff43b6c2ff in  ()
#7  0x000a in  ()
#8  0x5653f5d993f0 in  ()
#9  0x7f8580f2cfd6 in  () at /usr/lib/libQt5Core.so.5
#10 0x7f85800cd4cf in start_thread () at /usr/lib/libpthread.so.0
#11 0x7f858271b2d3 in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f8573fff700 (LWP 17686)):
#0  0x7f8582710ae6 in ppoll () at /usr/lib/libc.so.6
#1  0x7f858115bcc3 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f858115d2dd in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f858110639c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f8580f2be62 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f8580f2cfd6 in  () at /usr/lib/libQt5Core.so.5
#6  0x7f85800cd4cf in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f858271b2d3 in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f8572591700 (LWP 923)):
#0  0x7f85800d3c45 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f8580a26f3c in  () at /usr/lib/libQt5Script.so.5
#2  0x7f8580a26f59 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f85800cd4cf in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f858271b2d3 in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f85737fe700 (LWP 752)):
#0  0x7f8582710ae6 in ppoll () at /usr/lib/libc.so.6
#1  0x7f858115bcc3 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f858115d2dd in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f858110639c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f8580f2be62 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f857f7ec249 in QHashedStringRef::indexOf(QChar const&, int) const ()
at /usr/lib/libQt5Qml.so.5
#6  0x7fff43b6c23f in  ()
#7  0x000a in  ()
#8  0x5653f5444a90 in  ()
#9  0x7f8580f2cfd6 in  () at /usr/lib/libQt5Core.so.5
#10 0x7f85800cd4cf in start_thread () at /usr/lib/libpthread.so.0
#11 0x7f858271b2d3 in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f8579467700 (LWP 693)):
#0  0x7f8582710ae6 in ppoll () at /usr/lib/libc.so.6
#1  0x7f858115bcc3 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f858115d2dd in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f858110639c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f8580f2be62 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f857f16bb28 in  () at 

[systemsettings] [Bug 416397] After I remove the shortcut to lock the screen via standalone "Screen locking" KCM, System Settings atarted to crash every time I double-click on "Workspace behavior"

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk

--- Comment #1 from David Edmundson  ---
>/usr/lib/qt/plugins/screenlocker_kcm.so

could you get debug symbols for this please

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

[kdeconnect] [Bug 414894] kdeconnectd segfaults in Device::name() when I try to pair my phone

[Albert Vaca]

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

--- Comment #2 from Albert Vaca  ---
Can you try deleting the config? Maybe there is something stored as a name
which is not valid.

The config is in the directory ~/.config/kdeconnect

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

[plasmashell] [Bug 416400] App launched while system tray settings is open has no icon in "Entries" section of system tray settings

[Patrick Silva]

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

Patrick Silva  changed:

   What|Removed |Added

Version|master  |5.17.90
   Platform|Other   |Archlinux Packages

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

[plasmashell] [Bug 416400] New: App launched while system tray settings is open has no icon in "Entries" section of system tray settings

[Patrick Silva]

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

Bug ID: 416400
   Summary: App launched while system tray settings is open has no
icon in "Entries" section of system tray settings
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: bugsefor...@gmx.com
  Target Milestone: 1.0

STEPS TO REPRODUCE
1. open system tray settings
2. open an app with systray icon (I tested VLC, Juk player and Deluge torrent
client)
3. 

OBSERVED RESULT
app launched in the step 2 has no icon in "Entries" section of systray
settings.
Close and reopen systray settings: now the app launched in the step 2 has an
icon in "Entries" section. 

EXPECTED RESULT
apps with systray icon always have an icon in "Entries" section of systray
settings.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.17.90
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.0

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

[frameworks-knewstuff] [Bug 415541] i18n: downloadNewWhat text used in different contexts, cannot be translated correctly

[Victor Ryzhykh]

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

--- Comment #15 from Victor Ryzhykh  ---
(In reply to Albert Astals Cid from comment #13)
> Do not post patches on bugzilla, use phabricator for patches.

https://phabricator.kde.org/D26544#596301

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

[okular] [Bug 416399] Okular can't be uninstalled on Windows 7.

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 CC||aa...@kde.org,
   ||kde-wind...@kde.org

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

[frameworks-knewstuff] [Bug 415541] i18n: downloadNewWhat text used in different contexts, cannot be translated correctly

[Victor Ryzhykh]

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

--- Comment #14 from Victor Ryzhykh  ---
Created attachment 125215
  --> https://bugs.kde.org/attachment.cgi?id=125215=edit
plasma-desktop-5.17.90-tr.patch

I also made this patch for plasma-desktop-5.17.90.
And one more small patch for plasma-workspace-5.17.90.
Now I have no errors on my plasma.
I will wait for a solution to this problem in git.
Sincerely, Victor.

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

[frameworks-knewstuff] [Bug 415541] i18n: downloadNewWhat text used in different contexts, cannot be translated correctly

[Albert Astals Cid]

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

--- Comment #13 from Albert Astals Cid  ---
Do not post patches on bugzilla, use phabricator for patches.

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

[okular] [Bug 416399] New: Okular can't be uninstalled on Windows 7.

[Alexander]

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

Bug ID: 416399
   Summary: Okular can't be uninstalled on Windows 7.
   Product: okular
   Version: unspecified
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: kos...@koshka.ddns.net
  Target Milestone: ---

Created attachment 125214
  --> https://bugs.kde.org/attachment.cgi?id=125214=edit
okular refuses to leave

A couple of times I tried to use windows builds of Okular from here:
https://binary-factory.kde.org/view/Windows%2064-bit/

Okular installs without an error and basically works but can't be uninstalled
using "Programs and Features" (see screenshot).
I get message "Access to the path is denied" and an offer to kill some unknown
and unnamed processes.
Both buttons "Yes" and "No" have the same result - dialog message appears
again.

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

[frameworks-knewstuff] [Bug 415541] i18n: downloadNewWhat text used in different contexts, cannot be translated correctly

[Victor Ryzhykh]

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

--- Comment #12 from Victor Ryzhykh  ---
Created attachment 125213
  --> https://bugs.kde.org/attachment.cgi?id=125213=edit
knewstuff-5.66-tr.patch

I made this patch for knewstuff

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

[frameworks-knewstuff] [Bug 416398] New: Global theme GHNS dialog is too large and can't be resized

[Antonio Rojas]

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

Bug ID: 416398
   Summary: Global theme GHNS dialog is too large and can't be
resized
   Product: frameworks-knewstuff
   Version: 5.66.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jpwhit...@kde.org
  Reporter: aro...@archlinux.org
CC: kdelibs-b...@kde.org
  Target Milestone: ---

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

The new Global Theme GHNS dialog used in Plasma 5.18 beta is too large,
overflows the screen and can't be downsized. Also, maximizing it makes it be
cut off at the bottom.

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

[frameworks-knewstuff] [Bug 415541] i18n: downloadNewWhat text used in different contexts, cannot be translated correctly

[Albert Astals Cid]

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

--- Comment #11 from Albert Astals Cid  ---
(In reply to Victor Ryzhykh from comment #10)
> No need to do part of the phrase in the knewstuff package.
> Leave it only calls 
> title: i18n("%1", component.downloadNewWhat)
> or
> title: "%1", component.downloadNewWhat

You realize 
title: "%1", component.downloadNewWhat
is just not valid QML right?

> And transfer all the text to plasma packages.
> NewStuff.Button {
> downloadNewWhat: i18n("Get New Global Themes...")
> 
> This will eliminate problems in other localizations.
> In which not all words of the text are written in uppercase.
> 
> For example, now "Download New Global Themes...",
> Which consists of two parts of the text, from different packages.
> And the translation should be "Загрузить новые темы оформеления...".
> This cannot be obtained if a two-part text is compiled.
> 
> In addition, the translation of the phrase "i18n ("Download New %1",
> component.downloadNewWhat)" 
> in the package knewstuff does not work.

The problem here is you're speaking about different things and they have
different solutions.

The first issue is a translation puzzle, that's bad and should be fixed.

The second issue seems to be a as far as i understand your text a bug that
makes things not show translated.

They are not linked at all one to eachother and should not be discussed in the
same bugzilla issue.

Would you think it would be a good idea to close this one and then open a new
issue for each of the problems, explaining in each of the issue what the
problem is and just talking about one problem in each issue?

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

[systemsettings] [Bug 414396] KCM can't read settings file (kde_settings.conf)

[Filip Fila]

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

--- Comment #18 from Filip Fila  ---
(In reply to Filip Fila from comment #17)
> (In reply to Filip Fila from comment #16)
> > Sorry for the wrong lead, I can now reproduce this in Manjaro as well.
> > 
> > It appears this code isn't working for kde_settings.conf:
> > https://github.com/KDE/sddm-kcm/blob/master/sddmauthhelper.cpp#L39
> 
> It seems the conditional 'if(!file.exists())' is preventing permissions from
> being set, which should mean kde_setting.conf is being created prematurely.

Correction, when removing the 'file.exists' check, any change generated within
the Theme tab will still create an unreadable file, while any change in the
Advanced tab will create a readable file. 

This is a bit more complicated that I thought...

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

[systemsettings] [Bug 416397] After I remove the shortcut to lock the screen via standalone "Screen locking" KCM, System Settings atarted to crash every time I double-click on "Workspace behavior"

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[Discover] [Bug 416394] After I remove a flatpak remote via CLI, Discover always crashes while checking for updates

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[frameworks-ktexteditor] [Bug 416393] Emboldening of fonts is applied inconsistently

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||n...@kde.org
 Status|REPORTED|RESOLVED

--- Comment #1 from Nate Graham  ---


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

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

[frameworks-kwidgetsaddons] [Bug 378523] KFontRequester: Fonts are saved with face name preventing bold/italic from working

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||k...@happyjack.org

--- Comment #76 from Nate Graham  ---
*** Bug 416393 has been marked as a duplicate of this bug. ***

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

[kate] [Bug 416320] External tool needs "Working directory" set to something to work

[Dominik Haumann]

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

--- Comment #1 from Dominik Haumann  ---
I will have a look.

Out of curiosity, what other external tools do you use?

PS: many of the other external tools may also not work in Windows, since I only
tested on Linux for now. That's why feedback would be great.

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

[kate] [Bug 416356] Missing "Bookmark Toolview"

[Dominik Haumann]

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

--- Comment #1 from Dominik Haumann  ---
This is a nice idea. Currently, bookmarks are only added to the Bookmarks menu.

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

[kdevelop] [Bug 416051] Crash deep in Qt when showing completion

[Aleix Pol]

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

--- Comment #3 from Aleix Pol  ---
The commit is already reverted in 5.14.
Also the test case from the bug report doesn't trigger on me.

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

[kinfocenter] [Bug 300265] keyboard navigation doesn't update the device info on the right

[Gregor Mi]

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

--- Comment #6 from Gregor Mi  ---
(In reply to Harald Sitter from comment #5)
> As for the pane update on enter:
> USB Devices is different it does start out completely expanded

Being expanded or not seems to be an aspect which can be treated separately of
having to press the Enter key or not to update the panel on the right side.
Browsing through the device information by just using cursor keys feels more
easy to me. This would make this ticket a "wishlist" item, though.

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

[systemsettings] [Bug 414396] KCM can't read settings file (kde_settings.conf)

[Filip Fila]

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

--- Comment #17 from Filip Fila  ---
(In reply to Filip Fila from comment #16)
> Sorry for the wrong lead, I can now reproduce this in Manjaro as well.
> 
> It appears this code isn't working for kde_settings.conf:
> https://github.com/KDE/sddm-kcm/blob/master/sddmauthhelper.cpp#L39

It seems the conditional 'if(!file.exists())' is preventing permissions from
being set, which should mean kde_setting.conf is being created prematurely.

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

[kinfocenter] [Bug 359159] File Indexer Monitor: "Start File Indexer" button has no effect

[Gregor Mi]

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

--- Comment #3 from Gregor Mi  ---
On Tumbleweed 20191023 still the same error:

 ~  kcmshell5 kcm_fileindexermonitor  
   
 org.kde.kcoreaddons: Error loading plugin
"kcm_fileindexermonitor" "The shared library was not found." 
Plugin search paths are ("/usr/lib64/qt5/plugins", "/usr/bin") 
The environment variable QT_PLUGIN_PATH might be not correctly set

Could this still be a packaging error?

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

[kinfocenter] [Bug 362102] Tooltips contain no (visible) text

[Gregor Mi]

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

Gregor Mi  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Gregor Mi  ---
I cannot reproduce it either, because it shows the message "This type of
history is currently not available for this device" instead of the application
list. Bug can be closed.

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

[kmail2] [Bug 416318] As soon as I click on a certain line in the Message list Kmail crashes in a flash - every time!

[Ruth]

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

--- Comment #5 from Ruth  ---
Thank you, Laurent,

I've found that file, however I'm not able to delete it in Dolphin. Is that
something I need to do at the command line? What is the exact command to give?

Oh, wait. I could try the Super User file manager because this is down in the
root area.



I paused to try that and sure enough, I've been able to delete that plugin.
Then I went into KMail, and it took two tries, but now I've been able to delete
that email! 

Wonderful! Thanks ever so much!



I will save this information in case I ever need it again - hopefully not, eh?



Blessings & Thanks,

Ruth





 On Thu, 16 Jan 2020 23:57:49 -0600 Laurent Montel
 wrote 


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

--- Comment #4 from Laurent Montel  --- 
You can remove this plugin 
/usr/lib64/qt5/plugins/messageviewer/bodypartformatter/messageviewer_bodypartformatter_semantic.so
 

=> it will not crash. 

it was fixed in new version but for your version the better workaround is 
removing it. 

Regards

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

[kinfocenter] [Bug 313860] Misuse of i18n calls in global namespace

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from Albert Astals Cid  ---
Yes, TRANSLATION_DOMAIN helps here

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

[krita] [Bug 415213] Transform Tool Crashing Program After resizing

[Stacey]

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

Stacey  changed:

   What|Removed |Added

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

--- Comment #12 from Stacey  ---
(In reply to Tymond from comment #11)
> @Stacey our developer made another fixes to the transform tool. Can you
> please download Krita Next version (the newest one available on the website)
> and see if you have any trouble with transform tool there?

Hi there,
Thanks for the reply. After I obtained the DebugView and Krita log, I saw the
report pointing out the version of OpenGL 2.0 when OpenGL 3.1 seemed to be
required. I have ran Krita on OpenGL 2.0 before so I don't know what's changed
since then, but I got frustrated and decided to upgrade my graphics card once I
learnt that my on board graphics could not update any higher. I upgraded to a
Nvidia Geforce GT710 which can support much higher than 3.1 and this since has
fixed the issue. 
The problem therefore seemed to stem from being a user on a version of OpenGL
that is older than 3.1. I don't know if that is something you guys plan to keep
in place or whether you have anyone that can test the issue with an older
version of OpenGL now.
As I have installed the new card, I can no longer trigger the issue. I hope
this info helps in some way with later updates for Krita if it intends to stay
friendly to older systems.

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

[Breeze] [Bug 416348] Scrollbar on the right side is off-center

[Noah Davis]

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

--- Comment #4 from Noah Davis  ---
This should have been fixed already.

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

[k3b] [Bug 416364] can't find cd/dvd writer

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 CC||aa...@kde.org
 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Albert Astals Cid  ---
That version is more than 2 years old, please try a new version and see if you
can still reproduce the issue

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

[krusader] [Bug 411403] Users are not able to browse cbz files using the right arrow key (although it works for cbr files)

[Toni Asensi Esteve]

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

Toni Asensi Esteve  changed:

   What|Removed |Added

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

--- Comment #3 from Toni Asensi Esteve  ---
This bug report can be closed.

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

[digikam] [Bug 403349] Digikam window offset on high resolution display

[Steve Franks]

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

--- Comment #5 from Steve Franks  ---
Will try to replicate the bug over the weekend.
Sorry I haven’t had chance to download/test the new beta this week, because
of work.
Steve

On Fri, 17 Jan 2020 at 14:10,  wrote:

> https://bugs.kde.org/show_bug.cgi?id=403349
>
> caulier.gil...@gmail.com changed:
>
>What|Removed |Added
>
> 
>  CC||caulier.gil...@gmail.com
>
> --- Comment #4 from caulier.gil...@gmail.com ---
> This is reproducible using current digiKam 7.0.0-beta2 pre-release
> installar
> for Windows ?
>
> https://files.kde.org/digikam/
>
> Gilles Caulier
>
> --
> You are receiving this mail because:
> You reported the bug.
> You are on the CC list for the bug.

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

[plasmashell] [Bug 402392] dropbox system tray menu positioned off-screen

[Nate Graham]

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

--- Comment #10 from Nate Graham  ---
Fair enough!

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

[systemsettings] [Bug 416397] New: After I remove the shortcut to lock the screen via standalone "Screen locking" KCM, System Settings atarted to crash every time I double-click on "Workspace behavior

[Patrick Silva]

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

Bug ID: 416397
   Summary: After I remove the shortcut to lock the screen via
standalone "Screen locking" KCM, System Settings
atarted to crash every time I double-click on
"Workspace behavior"
   Product: systemsettings
   Version: 5.17.90
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: bugsefor...@gmx.com
  Target Milestone: ---

Application: systemsettings5 (5.17.90)

Qt Version: 5.14.0
Frameworks Version: 5.66.0
Operating System: Linux 5.4.12-arch1-1 x86_64
Windowing system: X11
Distribution: Arch Linux

-- Information about the crash:
- What I was doing when the application crashed:
I opened "Screen locking" kcm via the apps launcher
I removed the shortcut to lock the screen (meta+l)
I clicked on "Ok" button
since then system settings crashes every time I try to open "Workspace
behavior"

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7cc033c100 (LWP 96963))]

Thread 8 (Thread 0x7f7c9e330700 (LWP 97018)):
#0  0x7f7cc4a4d9ef in poll () at /usr/lib/libc.so.6
#1  0x7f7cc0f6f120 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f7cc0f6f1f1 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f7cc5008cdc in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f7c98000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f7cc4faf39c in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f7c9e32fd40, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:136
#5  0x7f7cc4dd4e62 in QThread::exec() (this=this@entry=0x5617c1ea7c90) at
../../include/QtCore/../../src/corelib/global/qflags.h:118
#6  0x7f7cc407b249 in QQmlThreadPrivate::run() (this=0x5617c1ea7c90) at
/tmp/makepkg/qt5-declarative-debug/src/qtdeclarative-everywhere-src-5.14.0/src/qml/qml/ftw/qqmlthread.cpp:155
#7  0x7f7cc4dd5fd6 in QThreadPrivate::start(void*) (arg=0x5617c1ea7c90) at
thread/qthread_unix.cpp:342
#8  0x7f7cc36374cf in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f7cc4a582d3 in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7f7cb5b2e700 (LWP 97008)):
#0  0x7f7cc363dc45 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f7cb7828dcc in  () at /usr/lib/dri/i965_dri.so
#2  0x7f7cb78289c8 in  () at /usr/lib/dri/i965_dri.so
#3  0x7f7cc36374cf in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f7cc4a582d3 in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f7cb632f700 (LWP 97007)):
#0  0x7f7cc363dc45 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f7cb7828dcc in  () at /usr/lib/dri/i965_dri.so
#2  0x7f7cb78289c8 in  () at /usr/lib/dri/i965_dri.so
#3  0x7f7cc36374cf in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f7cc4a582d3 in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f7cb6b30700 (LWP 97006)):
#0  0x7f7cc363dc45 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f7cb7828dcc in  () at /usr/lib/dri/i965_dri.so
#2  0x7f7cb78289c8 in  () at /usr/lib/dri/i965_dri.so
#3  0x7f7cc36374cf in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f7cc4a582d3 in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f7cb7331700 (LWP 97005)):
#0  0x7f7cc363dc45 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f7cb7828dcc in  () at /usr/lib/dri/i965_dri.so
#2  0x7f7cb78289c8 in  () at /usr/lib/dri/i965_dri.so
#3  0x7f7cc36374cf in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f7cc4a582d3 in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f7cbe189700 (LWP 96995)):
#0  0x7f7cc0f6662f in g_source_ref () at /usr/lib/libglib-2.0.so.0
#1  0x7f7cc0f6d662 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f7cc0f6d7df in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7f7cc0f6f0c8 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7f7cc0f6f1f1 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7f7cc5008cdc in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f7cbb60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7f7cc4faf39c in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f7cbe188d30, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:136
#7  0x7f7cc4dd4e62 in QThread::exec() (this=this@entry=0x7f7cc52dd080
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
../../include/QtCore/../../src/corelib/global/qflags.h:118
#8  0x7f7cc5258b28 in 

[digikam] [Bug 416371] 7.0.0-beta bug in Album tree view sorting order

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/kde/
   ||digikam/commit/eebc58c6a0a8
   ||e864a6d3078dfc0fe693e9d6cd6
   ||d
 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
   Version Fixed In||7.0.0

--- Comment #4 from Maik Qualmann  ---
Git commit eebc58c6a0a8e864a6d3078dfc0fe693e9d6cd6d by Maik Qualmann.
Committed on 17/01/2020 at 22:23.
Pushed by mqualmann into branch 'master'.

fix album sorting order
FIXED-IN: 7.0.0

M  +2-1NEWS
M  +13   -10   core/libs/models/albumfiltermodel.cpp

https://invent.kde.org/kde/digikam/commit/eebc58c6a0a8e864a6d3078dfc0fe693e9d6cd6d

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

[kdeconnect] [Bug 414894] kdeconnectd segfaults in Device::name() when I try to pair my phone

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

Summary|kdeconnectd segfaults in|kdeconnectd segfaults in
   |Device::name()  |Device::name() when I try
   ||to pair my phone

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

[kdeconnect] [Bug 414894] kdeconnectd segfaults in Device::name()

[Nate Graham]

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

--- Comment #1 from Nate Graham  ---
*** Bug 416396 has been marked as a duplicate of this bug. ***

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

[kdeconnect] [Bug 416396] Can no longer pair phone and computer

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Nate Graham  ---


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

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

[kdeconnect] [Bug 416396] New: Can no longer pair phone and computer

[Nate Graham]

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

Bug ID: 416396
   Summary: Can no longer pair phone and computer
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: n...@kde.org
  Target Milestone: ---

For about 3 months now, I have been unable to pair my phone and computer. I had
previously been able to, but one day it broke and I never started working
again.

Phone: Samsung Galaxy S7 running Android 8.0.0 and the latest KDE Connect app
from the Google Play store

Computer: 2016 HP Spectre x360 running openSUSE Tumbleweed with all KDE
software built from source.

Both devices are on my home WiFi network and can see one another.


STEPS TO REPRODUCE:
Try to pair from phone:
1. open KDE Connect app
2. Tap Hamburger menu and tap "Pair new device"
3. Tap my computer in the list
4. Tap "Request Pairing"
5. Click "Accept" on the notification that appears in Plasma on the compuer
Result: the Android app shows a spinner and eventually errors out the the
message "Timed out"


Try to pair from the KCM:
1. Open System Settings > KDE Connect
2. Click "Refresh"
3. Select my phone from the list
4. Click "Request Pair"
Result: The KCM shows an indeterminate progress bar and eventually shows an
inline message saying "Error trying to pair: Timed out"


Try to pair from the CLI:
1. Run `kdeconnect-cli --pair -d ` from the computer
Result: "Pair requested" is printed to the console but nothing further happens

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

[Falkon] [Bug 416395] New: Some downloads are canceled unnoticed

[Nikita Zlobin]

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

Bug ID: 416395
   Summary: Some downloads are canceled unnoticed
   Product: Falkon
   Version: 3.1.0
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: nick877...@gmail.com
  Target Milestone: ---

SUMMARY
If I try to e.g. save page with too long file name, it is reported as ok, but
file is not at its place. In download manager - its status is "canceled".
Reported to gentoo before: https://bugs.gentoo.org/705692


Steps to Reproduce:
1. Open some page and try to save it
2. Manually enter name, that is known to be too long for given dir/fs.
Actual Results:  
File is missing, and item in download list is "canceled".

Expected Results:  
It could at least report about calcel reason. But don't report it as success.

When I did so in Epiphany (gnome-web,gtk3), it clearly refused to save right in
save dialog (could be gtk feature).


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: gentoo (calculate)
(available in About System)
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.64.0
Qt Version: 5.12.3

ADDITIONAL INFORMATION
Configured with these:
-DCMAKE_DISABLE_FIND_PACKAGE_PySide2=ON
-DCMAKE_DISABLE_FIND_PACKAGE_Shiboken2=ON
-DCMAKE_DISABLE_FIND_PACKAGE_PythonLibs=ON
I don't use kde (desktop), falkon is installed without kde deps:
-DCMAKE_DISABLE_FIND_PACKAGE_KF5Wallet=ON
-DCMAKE_DISABLE_FIND_PACKAGE_KF5KIO=ON

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

[kdeconnect] [Bug 416326] 'Reply' and 'Like' buttons have switched functionality

[bugzilla_noreply]

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

v...@phux.dev changed:

   What|Removed |Added

 CC||v...@phux.dev

--- Comment #1 from v...@phux.dev ---
this is true for all action items. the right side buttons are reversed. The
upper button has the functionality of the lower and vice versa

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

[Discover] [Bug 416394] New: After I remove a flatpak remote via CLI, Discover always crashes while checking for updates

[Patrick Silva]

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

Bug ID: 416394
   Summary: After I remove a flatpak remote via CLI, Discover
always crashes while checking for updates
   Product: Discover
   Version: 5.17.90
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: lei...@leinir.dk
  Reporter: bugsefor...@gmx.com
CC: aleix...@kde.org
  Target Milestone: ---

SUMMARY
A few weeks ago I removed sdk.gnome.org remote via CLI and since then Discover
is unusable
on system because it always crashes while checking for updates.
Furthermore DiscoverNotifier crashes immediately after login.

Operating System: Arch Linux 
KDE Plasma Version: 5.17.90
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.0



Thread 27 (Thread 0x7fffa57fa700 (LWP 88573)):
#0  0x759eee9d in syscall () at /usr/lib/libc.so.6
#1  0x7282711b in g_cond_wait_until () at /usr/lib/libglib-2.0.so.0
#2  0x728a4f63 in  () at /usr/lib/libglib-2.0.so.0
#3  0x728a5154 in g_async_queue_timeout_pop () at
/usr/lib/libglib-2.0.so.0
#4  0x7284c02a in  () at /usr/lib/libglib-2.0.so.0
#5  0x72852bb1 in  () at /usr/lib/libglib-2.0.so.0
#6  0x74f9c4cf in start_thread () at /usr/lib/libpthread.so.0
#7  0x759f42d3 in clone () at /usr/lib/libc.so.6

Thread 22 (Thread 0x7fffa7fff700 (LWP 88568)):
#0  0x759e99ef in poll () at /usr/lib/libc.so.6
#1  0x72876120 in  () at /usr/lib/libglib-2.0.so.0
#2  0x728761f1 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x75fa6cdc in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fffb40166d0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x75f4d39c in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fffa7ffed60, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:136
#5  0x75d72e62 in QThread::exec() (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:118
#6  0x75d73fd6 in QThreadPrivate::start(void*) (arg=0x55c38e00) at
thread/qthread_unix.cpp:342
#7  0x74f9c4cf in start_thread () at /usr/lib/libpthread.so.0
#8  0x759f42d3 in clone () at /usr/lib/libc.so.6

Thread 21 (Thread 0x7fffb97fa700 (LWP 88567)):
#0  0x74fa2f7a in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x75d79c48 in QWaitConditionPrivate::wait_relative(QDeadlineTimer)
(this=0x56df69f0, deadline=...) at thread/qwaitcondition_unix.cpp:136
#2  0x75d79c48 in QWaitConditionPrivate::wait(QDeadlineTimer)
(deadline=..., this=0x56df69f0) at thread/qwaitcondition_unix.cpp:144
#3  0x75d79c48 in QWaitCondition::wait(QMutex*, QDeadlineTimer)
(this=, mutex=0x570661c8, deadline=...) at
thread/qwaitcondition_unix.cpp:225
#4  0x75d79d69 in QWaitCondition::wait(QMutex*, unsigned long)
(this=this@entry=0x56df69d0, mutex=mutex@entry=0x570661c8,
time=) at thread/qwaitcondition_unix.cpp:209
#5  0x75d773dd in QThreadPoolThread::run() (this=0x56df69c0) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:270
#6  0x75d73fd6 in QThreadPrivate::start(void*) (arg=0x56df69c0) at
thread/qthread_unix.cpp:342
#7  0x74f9c4cf in start_thread () at /usr/lib/libpthread.so.0
#8  0x759f42d3 in clone () at /usr/lib/libc.so.6

[mThread 20 (Thread 0x7fffb9ffb700 (LWP 88566)):
#0  0x74fa2c45 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x75d79cc4 in QWaitConditionPrivate::wait(QDeadlineTimer)
(deadline=..., this=0x56857580) at thread/qwaitcondition_unix.cpp:146
#2  0x75d79cc4 in QWaitCondition::wait(QMutex*, QDeadlineTimer)
(this=, mutex=0x56857560, deadline=...) at
thread/qwaitcondition_unix.cpp:225
#3  0x75d79da2 in QWaitCondition::wait(QMutex*, unsigned long)
(this=this@entry=0x56857568, mutex=mutex@entry=0x56857560,
time=time@entry=18446744073709551615) at
../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68
#4  0x77a8918b in QSGRenderThreadEventQueue::takeEvent(bool)
(wait=true, this=0x56857558) at
/tmp/makepkg/qt5-declarative-debug/src/qtdeclarative-everywhere-src-5.14.0/src/quick/scenegraph/qsgthreadedrenderloop.cpp:255
#5  0x77a8918b in QSGRenderThread::processEventsAndWaitForMore()
(this=this@entry=0x568574c0) at
/tmp/makepkg/qt5-declarative-debug/src/qtdeclarative-everywhere-src-5.14.0/src/quick/scenegraph/qsgthreadedrenderloop.cpp:905
#6  0x77a8941b in QSGRenderThread::run() (this=0x568574c0) at
/tmp/makepkg/qt5-declarative-debug/src/qtdeclarative-everywhere-src-5.14.0/src/quick/scenegraph/qsgthreadedrenderloop.cpp:1000
#7  0x75d73fd6 in QThreadPrivate::start(void*) (arg=0x568574c0) at
thread/qthread_unix.cpp:342
#8  

[digikam] [Bug 416392] Does not recognice Canon EOS 50D as well as Powershot G10 under Win 64

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #2 from Maik Qualmann  ---


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

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

[digikam] [Bug 388137] Camera not found by digiKam under Windows

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||martin.huon...@bluewin.ch

--- Comment #4 from Maik Qualmann  ---
*** Bug 416392 has been marked as a duplicate of this bug. ***

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

[digikam] [Bug 416392] Does not recognice Canon EOS 50D as well as Powershot G10 under Win 64

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
The problem is known, cameras as PTP or MTP devices are not yet supported under
Windows. Only mass storage is supported.

Maik

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

[plasmashell] [Bug 402392] dropbox system tray menu positioned off-screen

[Konrad Materka]

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

Konrad Materka  changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 Status|REPORTED|RESOLVED

--- Comment #9 from Konrad Materka  ---
Closing, as this is a Dropbox bug.

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

[plasmashell] [Bug 402392] dropbox system tray menu positioned off-screen

[Konrad Materka]

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

--- Comment #8 from Konrad Materka  ---
(In reply to Nate Graham from comment #7)
> Is there any way we can work around the issue on our side?

Heh... We can add something like this in our code:

if (findExcutableForPid(dbus()->senderPid()) == "*dropbox*") {
  wait, so menu UpdateLayout can proceed in the meantime or something like that
}

but... we shouldn't, because:
* this is a super ugly hack that can impact performance for all right clicks on
tray icons
* Dropbox is using Qt (PyQt to be clear)! It should work correctly out of the
box, they are definitely doing something nasty. Of course everything is
compiled and obfuscated, so no chance for community fix.
* As Samer Masterson wrote, they have other issue (memory leaks) and that's
*their* workaround for it.
* I know that Dropbox is important, I'm using it myself. But we shouldn't write
costly workarounds for one app.
* Dropbox Linux app is buggy and there is no support from their side. I would
love to report a bug correct and even send a patch. But I can't
* This is not a critical bug that, we can live with that. It is just annying.
* I may repeat myself, but it is super ugly :)

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

[Breeze] [Bug 413915] All electron apps have grey menus when using breeze gtk3 theme

[hexchain]

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

--- Comment #11 from hexchain  ---
Forgot to say that I'm on Arch Linux, Plasma 5.18 beta now. The active color
scheme is Breeze.

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

[Breeze] [Bug 413915] All electron apps have grey menus when using breeze gtk3 theme

[hexchain]

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

--- Comment #10 from hexchain  ---
Created attachment 125209
  --> https://bugs.kde.org/attachment.cgi?id=125209=edit
The said script in #c8

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

[Breeze] [Bug 413915] All electron apps have grey menus when using breeze gtk3 theme

[hexchain]

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

--- Comment #9 from hexchain  ---
Created attachment 125208
  --> https://bugs.kde.org/attachment.cgi?id=125208=edit
Electron6 menu bar (7 looks the same)

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

[Breeze] [Bug 413915] All electron apps have grey menus when using breeze gtk3 theme

[hexchain]

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

hexchain  changed:

   What|Removed |Added

 CC||i...@hexchain.org

--- Comment #8 from hexchain  ---
I'm afraid this change did not fix anything for me. Now the menu bar items in
Electron are hardly readable. A screenshot is attached.

It could be stale configurations on my side, but I am sure I have a fresh
~/.config/gtk-3.0/colors.css.

Electron uses a set of CSS selectors to get color for the menubar item text
from the current theme, see [1]. I've written a simple script to replicate most
of this logic according to [1] and [2], and the result is indeed
unsatisfactory.

Currently, to work around this issue, I have the following lines in
~/.config/gtk-3.0/gtk.css:

window.background.chromium menubar, window.background.chromium .menubar {
color: @theme_fg_color;
}

[1]
https://sourcegraph.com/github.com/electron/electron@v7.1.9/-/blob/shell/browser/ui/views/menu_bar.cc#L294-297
[2]
https://source.chromium.org/chromium/chromium/src/+/master:chrome/browser/ui/libgtkui/gtk_util.cc;l=474;drc=3085f123db39ded55bccebcd1e508ad94bc8ef50?originalUrl=https:%2F%2Fcs.chromium.org%2F

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

[kdenlive] [Bug 415299] Crash when opening a project with Qt 5.14

[Christoph Feck]

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

--- Comment #5 from Christoph Feck  ---
Those numbers are invent.kde.org (gitlab) issue numbers, see
https://invent.kde.org/kde/kdenlive/issues/494

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

[plasmashell] [Bug 416390] blue border is not fully drawn when I hover a tooltip with playback controls

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Assignee|h...@kde.org|n...@kde.org
 Status|CONFIRMED   |ASSIGNED

--- Comment #2 from Nate Graham  ---
Patch: https://phabricator.kde.org/D26739

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

[kwin] [Bug 416359] fonts of location bar of non-focused pane are transparent on Wayland

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #4 from Christoph Feck  ---
https://bugreports.qt.io/browse/QTBUG-80982

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