[digikam] [Bug 412917] On macOS Mojave image editor opens withouth toolbars

[00pippo]

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

--- Comment #3 from 00pippo  ---
(In reply to Maik Qualmann from comment #2)
> Here you will find the pre-release of digiKam-6.4.0 where the problem has
> been fixed:
> 
> https://files.kde.org/digikam/
> 
> Maik

Maik

6.4.0 works so far, all mentioned issues are fixed as far as I can see up to
now. However, within all these good news, there are also  bad news. JPEG2000
files cannot be opened. It does not matter wether generated with version 6.4.0
or prior versions, the imaged editor opens and states "Cannot open file
.jp2."

00pippo

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

[digikam] [Bug 412950] While processing new collection, any (mouse)action will result in crash of digiKam

[Maik Qualmann]

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

--- Comment #2 from Maik Qualmann  ---
You can use the pre-release version of digiKam-6.4.0:

https://files.kde.org/digikam/

Maik

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

[digikam] [Bug 411927] Crash during initial scan

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||chasa.im...@xs4all.nl

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

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

[digikam] [Bug 412950] While processing new collection, any (mouse)action will result in crash of digiKam

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com
 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Maik Qualmann  ---


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

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

[systemsettings] [Bug 379822] Consider renaming "Multimedia" section to something more familiar

[Noah Davis]

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

Noah Davis  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 CC||noaha...@gmail.com
 Resolution|--- |FIXED

--- Comment #7 from Noah Davis  ---
Since the Audio KCM was moved out of the Multimedia category, I think this bug
can be closed.

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

[systemsettings] [Bug 379822] Consider renaming "Multimedia" section to something more familiar

[Noah Davis]

https://bugs.kde.org/show_bug.cgi?id=379822
Bug 379822 depends on bug 379885, which changed state.

Bug 379885 Summary: Breeze icon for "Multimedia" in systemsettings is confusing 
for new users
https://bugs.kde.org/show_bug.cgi?id=379885

   What|Removed |Added

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

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

[Breeze] [Bug 379885] Breeze icon for "Multimedia" in systemsettings is confusing for new users

[Noah Davis]

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

Noah Davis  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 CC||noaha...@gmail.com
 Resolution|--- |FIXED

--- Comment #8 from Noah Davis  ---
Since the Audio KCM was moved out of the Multimedia category, I think this bug
can be closed.

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

[plasma-nm] [Bug 412556] is not possible to have networkmanager to ask username for wireless

[Jan Grulich]

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

Jan Grulich  changed:

   What|Removed |Added

 CC||jgrul...@redhat.com

--- Comment #2 from Jan Grulich  ---
What type of wireless security do you use? Is that for WPA/WPA2 enterprise?

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

[kontact] [Bug 412955] New: Kontact crashed when I marked an expired task finished

[Szőts Ákos]

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

Bug ID: 412955
   Summary: Kontact crashed when I marked an expired task finished
   Product: kontact
   Version: 5.12.1
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: szots...@gmail.com
  Target Milestone: ---

Application: kontact (5.12.1)

Qt Version: 5.13.1
Frameworks Version: 5.62.0
Operating System: Linux 5.2.14-1-default x86_64
Distribution (Platform): openSUSE RPMs

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

I opened Kontact, went to Tasks tab in KOrganizer part, reversed the sorting of
the "Name" column, opened up the second level of the TreeView, therefore many
subtasks got visible, scrolled to an expired task (indicated with red
backround), clicked on its checkbutton to mark as finished, then Kontact
crashed immediately.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
29return SYSCALL_CANCEL (poll, fds, nfds, timeout);
[Current thread is 1 (Thread 0x7efbee215a80 (LWP 12303))]

Thread 23 (Thread 0x7efbaeffd700 (LWP 13864)):
#0  futex_reltimed_wait_cancelable (private=0, reltime=0x7efbaeffc840,
expected=0, futex_word=0x7efbaeffca08) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7efbaeffc8e0, mutex=0x7efbaeffc9b8,
cond=0x7efbaeffc9e0) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x7efbaeffc9e0, mutex=0x7efbaeffc9b8,
abstime=0x7efbaeffc8e0) at pthread_cond_wait.c:667
#3  0x7efbf66b6486 in base::ConditionVariable::TimedWait () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:127
#4  0x7efbf66b6e53 in base::WaitableEvent::TimedWaitUntil () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:230
#5  0x7efbf66b6fd1 in base::WaitableEvent::TimedWait () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:162
#6  0x7efbf666f141 in
base::internal::SchedulerWorker::Delegate::WaitForWork () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:37
#7  0x7efbf6671fdd in base::internal::SchedulerWorker::RunWorker () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:303
#8  0x7efbf66726d4 in base::internal::SchedulerWorker::RunPooledWorker ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:229
#9  0x7efbf66b92c5 in ThreadFunc () at
./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81
#10 0x7efbfd072faa in start_thread (arg=) at
pthread_create.c:486
#11 0x7efbff5e073f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 22 (Thread 0x7efaea938700 (LWP 12428)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x7efaea937a18) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x7efaea9379c8,
cond=0x7efaea9379f0) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x7efaea9379f0, mutex=0x7efaea9379c8) at
pthread_cond_wait.c:655
#3  0x7efbf66b638c in base::ConditionVariable::Wait () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:75
#4  0x7efbf66b6e60 in base::WaitableEvent::TimedWaitUntil () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:232
#5  0x7efbf66b6f8f in base::WaitableEvent::Wait () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:155
#6  0x7efbf666f116 in
base::internal::SchedulerWorker::Delegate::WaitForWork () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:35
#7  0x7efbf667232b in base::internal::SchedulerWorker::RunWorker () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:331
#8  0x7efbf6672714 in base::internal::SchedulerWorker::RunSharedWorker ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:241
#9  0x7efbf66b92c5 in ThreadFunc () at
./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81
#10 0x7efbfd072faa in start_thread (arg=) at
pthread_create.c:486
#11 0x7efbff5e073f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 21 (Thread 0x7efaeb6f1700 (LWP 12380)):
#0  __GI___libc_read (nbytes=16, buf=0x7efaeb6f0910, fd=114) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=114, buf=0x7efaeb6f0910, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2  0x7efbfc61370f in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7efbfc65fcbe in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#4  0x7efbfc661372 in ?? () from /usr/lib64/libglib-2.0.so.0
#5  0x7efbfc66149f in g_main_context_iteration () from

[Heaptrack] [Bug 412954] New: Software tests fails after build

[bugzilla_noreply]

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

Bug ID: 412954
   Summary: Software tests fails after build
   Product: Heaptrack
   Version: 1.1.0
  Platform: RedHat RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: m...@milianw.de
  Reporter: syst...@mdc-berlin.de
  Target Milestone: ---

Created attachment 123192
  --> https://bugs.kde.org/attachment.cgi?id=123192=edit
The complete build log

Hello,
after building, the software tests fails.
OS: CentOS 7.7

 4 - tst_inject (Failed)


4:
---
4: inject via libc
4:
---
4: /builddir/build/BUILD/heaptrack-1.1.0/tests/auto/tst_inject.cpp:105
4:
...
4: 
4: /builddir/build/BUILD/heaptrack-1.1.0/tests/auto/tst_inject.cpp:82: FAILED:
4:   REQUIRE( contents.find("\n+") != std::string::npos )
4: with expansion:
4:   18446744073709551615 (0x)
4:   !=
4:   18446744073709551615 (0x)
4: 
4:
===

---
4: inject via dlopen
4:
---
4: /builddir/build/BUILD/heaptrack-1.1.0/tests/auto/tst_inject.cpp:87
4:
...
4: 
4: /builddir/build/BUILD/heaptrack-1.1.0/tests/auto/tst_inject.cpp:82: FAILED:
4:   REQUIRE( contents.find("\n+") != std::string::npos )
4: with expansion:
4:   18446744073709551615 (0x)
4:   !=
4:   18446744073709551615 (0x)
4:

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

[kwin] [Bug 412382] Kwin Crash when minimized window with Magic Lamp effects

[Bug Janitor Service]

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

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

[okular] [Bug 375012] cannot print in custom dimensions

[Bug Janitor Service]

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

--- Comment #15 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 403759] system tray moves and overlaps with time and Configure Panel button after hiding some system tray icons

[Ben]

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

--- Comment #6 from Ben  ---
I cannot reproduce the bug in KDE neon 5.16 with updates as of 2019-10-14.  I
tried it on bare metal and in a VM.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.16
KDE Plasma Version: 5.16.5
KDE Frameworks Version: 5.63.0
Qt Version: 5.13.1
Kernel Version: 4.15.0-65-generice
OS Type: 64-bit


I tried killing xembedsniproxy but the green icon looks the same; however, that
green icon software has had several updates in the past months.  It only had
the black background when the panel got messed up.

I do not see a setting for compositor in System Settings > Display and Monitor
(see attachment "Display and Monitor settings").

The app with the green icon is Private Internet Access.

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

[plasmashell] [Bug 403759] system tray moves and overlaps with time and Configure Panel button after hiding some system tray icons

[Ben]

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

--- Comment #5 from Ben  ---
Created attachment 123191
  --> https://bugs.kde.org/attachment.cgi?id=123191=edit
Display and Monitor settings

Display and Monitor settings does not show a setting for compositor.

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

[krita] [Bug 412953] New: Compositions Docker exports duplicates of one composition when you export multiple.

[Jim]

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

Bug ID: 412953
   Summary: Compositions Docker exports duplicates of one
composition when you export multiple.
   Product: krita
   Version: 4.2.7-beta1
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Dockers
  Assignee: krita-bugs-n...@kde.org
  Reporter: snopm...@yahoo.com
  Target Milestone: ---

SUMMARY
Compositions Docker exports duplicates of one of the compositions if you export
multiple compositions at once. Sometimes there's artifacts like it's in the
middle of disabling or enabling view layers so it composited strangely.

STEPS TO REPRODUCE
1. Go to Compositions Docker and make at least two different compositions.
2. Have multiple compositions ticked, then export them.

OBSERVED RESULT
All the exported compositions are duplicates.
Sometimes an exported Composition will have artifacts on the image, like it was
in the middle of turning on/off view layers.

EXPECTED RESULT
Multiple compositions exported without duplicates.

SOFTWARE/OS VERSIONS
Windows: Windows 64-bit Home.
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Krita Plus 4.2.7-beta1 (git e9b2584)

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

[krita] [Bug 367832] Do not export PNG with Embed sRGB profile checked by default because Firefox color shift and more.

[Tyson Tan]

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

Tyson Tan  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED

--- Comment #32 from Tyson Tan  ---
There has been a new development to this old bug. When I was testing Bug
412943, I noticed that Firefox 69 now only does color management properly with
PNG pictures with this option CHECKED. It actually makes sense now that Firefox
is treating the option identically in both JPG and PNG pictures produced by
Krita.

It could also be my previous observation being flawed because of the faulty
color management mentioned in Bug 412943. With my current display setup it's
much easier to spot a wrong result.

Maybe we can now turn the "Embed sRGB profile" option in Save to PNG dialogue
back on.

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

[krita] [Bug 412926] Flattening a fill layer to apply a mask converts it to a regular paint layer.

[vanyossi]

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

vanyossi  changed:

   What|Removed |Added

 Resolution|--- |INTENTIONAL
 Status|REPORTED|RESOLVED
 CC||ghe...@gmail.com

--- Comment #3 from vanyossi  ---
This is already supported and covers the use case you are describing

To add the transparency information to the fill mask:
- right click on the mask
- Split Alpha > Write as alpha

Fill layer will remain as fill layer.

Flatten layer is designed to "apply" a layer projection an make it a pixel
layer.

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

[krita] [Bug 412928] Use color selector dockers for fill color when a fill layer is selected.

[vanyossi]

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

vanyossi  changed:

   What|Removed |Added

 CC||ghe...@gmail.com

--- Comment #2 from vanyossi  ---
In my opinion a button that changes function depending on the layer you are on
could generate confusion. However i see what you mean by the huge amount of
clicks to get the color you need.

This would need discussion as to how to implement it to reduce or eliminate
clicks. Ideally (my idea) one would press a button that would popup a
colorwheel, and changing the color wheel color would then change the color of
the fill layer.

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

[okular] [Bug 412930] Okular does not claim the ability to open .djvu files on Windows even though it can

[bugzilla_noreply]

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

sachanro...@gmail.com changed:

   What|Removed |Added

 CC||sachanro...@gmail.com

--- Comment #3 from sachanro...@gmail.com ---
(In reply to Christoph Cullmann from comment #2)
> Hmm, does opening the file work?

yep, opening the file manually from the applications works. It's just that it
not showing up made me assume okular-extra-backends was not included in full
somehow.

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

[krita] [Bug 412747] Crashed when editing global selection mask (Safe assert: clonedDocument->image()->isIdle() at KisDocument.cpp 1006)

[bugzilla_noreply]

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

acc4commissi...@gmail.com changed:

   What|Removed |Added

  Component|Tools/Transform |Tools/Selection
Summary|Crashed when using  |Crashed when editing global
   |transform tool (Safe|selection mask (Safe
   |assert: |assert:
   |clonedDocument->image()->is |clonedDocument->image()->is
   |Idle() at KisDocument.cpp   |Idle() at KisDocument.cpp
   |1006)   |1006)

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

[krita] [Bug 412943] Use System Monitor Profile checkbox attributes wrong profile to screens, breaking color management

[Tyson Tan]

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

--- Comment #4 from Tyson Tan  ---
(In reply to Tyson Tan from comment #3)
> I did some further test today, and found that on one machine no matter how I
> arrange the multi-displays, Krita will always attribute wrong profiles to
> each monitor. Manually setting the profile does not work (at first) on
> Display #1 but works on Display #2. Check/Unchecking the Use system monitor
> profile checkbox will make the manually assigned profile work for Display #1
> as well, and it will remain working on restart.

So on this particular machine (it has KDE Plasma), I had to set the lower
monitor as "Primary" for Krita to auto-configure the profiles properly. I also
noticed that unless I configure it like that, every other graphics apps
(gwenview, Firefox) would also color manage incorrectly the same way as Krita
did.

I'm so confused right now...

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

[kdiff3] [Bug 412932] [KDiff3][v 1.9.70 x64] Missing Icons in Taskbar (Ubuntu)

[michael]

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

--- Comment #1 from michael  ---
I get the messages on my machine but the icon loads correctly. Weird. Let me
see what I can find out.

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

[ark] [Bug 409835] ark crashes when dragging a file into a new archive from kio-gdrive

[bugzilla_noreply]

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

--- Comment #1 from benaventeadr...@gmail.com ---
Created attachment 123190
  --> https://bugs.kde.org/attachment.cgi?id=123190=edit
New crash information added by DrKonqi

ark (19.08.1) using Qt 5.13.1

- What I was doing when the application crashed:
Trying to add a file inside a .zip using Ark inside kio-gdrive

- Unusual behavior I noticed:
The app crashed everytime I did the forementioned action

- Custom settings of the application:

-- Backtrace (Reduced):
#6  std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x0) at
/usr/include/c++/7/bits/atomic_base.h:396
#7  QAtomicOps::load (_q_value=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:227
#8  QBasicAtomicInteger::load (this=0x0) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:103
[...]
#10 QString::QString (other=..., this=0x7ffc8ea2ae68) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:956
#11 Kerfuffle::ReadOnlyArchiveInterface::entryPathsFromDestination
(entries=..., destination=, entriesWithoutChildren=0) at
./kerfuffle/archiveinterface.cpp:217

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

[ark] [Bug 409835] ark crashes when dragging a file into a new archive from kio-gdrive

[bugzilla_noreply]

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

benaventeadr...@gmail.com changed:

   What|Removed |Added

 CC||benaventeadr...@gmail.com

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

[krita] [Bug 412943] Use System Monitor Profile checkbox attributes wrong profile to screens, breaking color management

[Tyson Tan]

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

--- Comment #3 from Tyson Tan  ---
I did some further test today, and found that on one machine no matter how I
arrange the multi-displays, Krita will always attribute wrong profiles to each
monitor. Manually setting the profile does not work (at first) on Display #1
but works on Display #2. Check/Unchecking the Use system monitor profile
checkbox will make the manually assigned profile work for Display #1 as well,
and it will remain working on restart.

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

[Breeze] [Bug 360593] Dead-lock with --help on Qt 5.6

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 CC||k...@davidedmundson.co.uk
 Resolution|--- |WORKSFORME

--- Comment #9 from David Edmundson  ---
This seems to be not true anymore.

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

[krunner] [Bug 356020] krunner crash at plasma startup and from command line with segmentation fault (Qt5.5.1)

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||k...@davidedmundson.co.uk
 Resolution|--- |WORKSFORME

--- Comment #2 from David Edmundson  ---
Crash is in a really old Qt and we haven't had any duplicates.

Closing. Please do reopen if you still see this with a modern setup (Qt 5.12 or
newer)

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

[systemsettings] [Bug 410265] Bugs with application file type associations

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO
 CC||k...@davidedmundson.co.uk

--- Comment #2 from David Edmundson  ---
The bug described could be one of two things.

Either we do have a problem saving mime type associations, or the magic and
mimedata for ymv is rwong.

We can test that by running 

"file /path/to/your/blah.ymv" and seeing what that returns.
Please then paste output here.

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

[bugs.kde.org] [Bug 412299] A ticket can have both resolution INTENTIONAL and status RESOLVED

[Filipus Klutiero]

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

--- Comment #9 from Filipus Klutiero  ---
(In reply to Nate Graham from comment #8)
> (In reply to Filipus Klutiero from comment #7)
> > Ehm, and where in this report do you think I am being pedantic regarding the
> > resolution statuses?
> In everything you've written in this and several other bug reports. :)

This ticket's summary/topic is certainly not pedantic. In fact, I just found
that more than 500 tickets are *currently* set to RESOLVED INTENTIONAL:
https://bugs.kde.org/buglist.cgi?bug_status=RESOLVED_id=1670435_format=advanced=WONTFIX

If that's what you mean by "pedantic", you don't need to give such unreliable
advice. In fact, as far as this ticket is concerned, you didn't need to reply
at all.


> (In reply to Filipus Klutiero from comment #7)
> > Nate, considering that you demonstrated your misunderstanding of statuses in
> > https://community.kde.org/index.php?title=Get_Involved/
> > Bug_Reporting=79358=79286 and even more recently on this very
> > site, I have to ask: do you have understand that RESOLVED and INTENTIONAL
> > were not designed to be used together (or - to put it simply - that they are
> > incompatible)?
> You can keep claiming this, but I'm afraid it won't change anything. Your
> understanding is not accurate. We can and do use the RESOLVED and
> INTENTIONAL statuses together to mean "this bug report is closed because the
> software that you believe is behaving incorrectly is in fact behaving
> exactly the way we intend it to behave". Thousands of bugs have been closed
> with RESOLVED INTENTIONAL and that meaning. That's just what it means,
> sorry. If you don't like that, you'll have to get used to it, or start a
> discussion in the kde-devel mailing list proposing that we change it.

Eh, that was not a claim. That was a question. But your reply makes the answer
clear - you still completely misunderstand the meaning of these statuses, and
therefore you are not in a position to understand this bug currently. Thanks
for:
1. Answering questions rather than trying to change the topic.
2. Taking the measures necessary so that this ticket's resolution is restored.
3. *Filing* tickets asking to change the definitions, if you would like to
change the meaning of statuses.
4. Leaving this ticket and others which conflict with your usage alone, unless
the meanings are actually changed, or you otherwise have something to
*contribute* to them.

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

[digikam] [Bug 412113] Permanent error

[Pauli]

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

--- Comment #6 from Pauli  ---
 This is the answer from SuSE Support.

Fakt ist:

   - digiKam: 

– Qt5::WebKitWidgets – zwingend erforderlich.
– Qt5::WebEngine – nicht vorgeschrieben …

   - openSUSE:

– libqt5-qtwebengine – steht für Tumbleweed und Leap zur Verfügung …
– libqt5-qtwebkit – AFAICS, nur der Quellcode steht zur Verfügung …

   - Plasma ab Version 5.6 hat gar keine Qt WebKit mehr …
   - Und, .

   The KDE team has decided to remove Qt Webkit from the default openSUSE
installation. There should be minimal impact to users; the only exception is
with Marble and Digikam. Those will not be installed by default anymore because
they still depend on Qt Webkit, but they’re still available from YaST and
zypper.  Scheinbar, eine Fehlermeldung ist nötig –
. 

Am Freitag, 20. September 2019, 22:03:46 MESZ hat Maik Qualmann
 Folgendes geschrieben:  

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

--- Comment #4 from Maik Qualmann  ---
Git commit d73a25ed14440af7aabcc161d3a26adfdb9dd52a by Maik Qualmann.
Committed on 20/09/2019 at 20:02.
Pushed by mqualmann into branch 'master'.

set QWebEngine settings after new page

M  +6    -6    core/app/views/stack/welcomepageview.cpp
M  +5    -5  
core/utilities/geolocation/geoiface/widgets/htmlwidget_qwebengine.cpp

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

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

[Heaptrack] [Bug 412929] Can we grab a frame from Ruby land?

[Sam Saffron]

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

--- Comment #2 from Sam Saffron  ---
Yeah I think usability wise the best thing would be:

```
gem install heaptrack_ruby

# in the ruby script
require 'heaptrack_ruby'
```

Then heaptrack can publish some sort of library to register callbacks for
scripting languages, and the ruby gem can then on require simply register the
"lookup frame function" in the heaptrack library. 

Then you would use libunwind to get your stack followed by calling the callback
which is injected via ruby.

The actual code the Ruby extension would call to get the frame is along the
lines of:

```
if (ruby_thread_has_gvl_p() && ruby_current_vm_ptr &&
ruby_current_execution_context_ptr) {
  int line;
  const char *ptr = rb_source_location_cstr();
}
```

So I guess the signature of the method would be something like this if my C is
write which it is likely not:

```
heaptrack_register_backtrace_lookup( *(char**)(void) )
```

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

[korganizer] [Bug 412833] Monthview shows comma in year

[Trevor Parsons]

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

--- Comment #3 from Trevor Parsons  ---
(In reply to Allen Winter from comment #2)
> patch is up for review at https://phabricator.kde.org/D24638

Looks good to my untutored eye. Thanks for such quick work, Allen!

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

[Heaptrack] [Bug 412742] $pipe for mkfifo has no write permission

[Sam Saffron]

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

--- Comment #4 from Sam Saffron  ---
Yeah I do see the cleanup working, I think where I was getting confused is that
I was doing a CTRL-C on heaptrack when it is attached and that left the file
around, but I am not sure if there is any clean thing we can do for such a
case.

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

[korganizer] [Bug 232162] Events, to-dos and journal entries not sorted within a day in Month view

[bugzilla_noreply]

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

--- Comment #3 from cs...@bxabi.com ---
19.08.2

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

[kdev-python] [Bug 412936] No inbuilt support for virtual environments

[Francis Herne]

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

Francis Herne  changed:

   What|Removed |Added

 CC||m...@flherne.uk

--- Comment #3 from Francis Herne  ---
There should be; you might have to reload files after changing the path.

It would be better if we autodetected virtualenvs, of course.

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

[plasma-nm] [Bug 412556] is not possible to have networkmanager to ask username for wireless

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #1 from David Edmundson  ---
Just to make really sure I understand this correctly.

You have a setup where everyone logs into the laptop with the same credentials
then logs onto the wifi with unique credentials.

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

[konsole] [Bug 412348] Scrollbar floats to the left in i3, without Plasma.

[Mariusz Glebocki]

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

Mariusz Glebocki  changed:

   What|Removed |Added

 CC||m...@arccos-1.net

--- Comment #6 from Mariusz Glebocki  ---
It happens also with Breeze and Fusion. Bug in code. Fix:
https://invent.kde.org/kde/konsole/merge_requests/40

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

[plasmashell] [Bug 412781] Various graphical glitches since Qt5.14

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #19 from David Edmundson  ---
We have an upstream report, it's got our attention and Qt's attention. 

I don't think any local workaround is doable. Lets focus there.

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

[dolphin] [Bug 412952] Dolphin seems to add extra quotes when deleting trailing quote

[Marco Parillo]

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

Marco Parillo  changed:

   What|Removed |Added

URL||https://forum.manjaro.org/t
   ||/testing-update-2019-10-13-
   ||kernels-kde-apps-firefox-ll
   ||vm9-pamac-9-0/107033/41

--- Comment #1 from Marco Parillo  ---
Discussion starts here:
https://forum.manjaro.org/t/testing-update-2019-10-13-kernels-kde-apps-firefox-llvm9-pamac-9-0/107033/41?

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

[dolphin] [Bug 412952] New: Dolphin seems to add extra quotes when deleting trailing quote

[Marco Parillo]

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

Bug ID: 412952
   Summary: Dolphin seems to add extra quotes when deleting
trailing quote
   Product: dolphin
   Version: 19.08.2
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: search
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: marco_pari...@hotmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Open Dolphin
2. Click on Search
3. Type search string
4. Delete trailing quote

OBSERVED RESULT

The trailing quote is added back, with an additional opening quote

EXPECTED RESULT

Quotes should match.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 

Operating System: Manjaro Linux 
KDE Plasma Version: 5.16.5
KDE Frameworks Version: 5.62.0
Qt Version: 5.13.1
Kernel Version: 4.19.79-1-MANJARO
OS Type: 64-bit
Processors: 2 × Intel® Core™2 Duo CPU T7300 @ 2.00GHz
Memory: 3.8 GiB of RAM

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

[systemsettings] [Bug 412951] New: hmaburger button aside the header of several KCMs

[Patrick Silva]

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

Bug ID: 412951
   Summary: hmaburger button aside the header of several KCMs
   Product: systemsettings
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: bugsefor...@gmx.com
  Target Milestone: ---

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

SUMMARY
On neon unstable edition I see a hamburger button aside the header of several
KCMs, no menu opens when such button is clicked. My screenshot shows "global
theme" KCM, but the following KCMs are also affected:

plasma style
window decorations
colors
fonts
icons
cursors
general behavior
desktop effects
virtual desktops
boot splash screen
splash screen
file search
notifications
language
launch feedback
user feedback
display configuration
night colors
audio

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.17.80
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.1

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

[kdenlive] [Bug 412949] kdenlive-19.08.1-x86_64.appimage or kdenlive-19.08.2-x86_64.appimage or kdenlive-19.08.2b-x86_64.appimage does not start on my system : Ubuntu 18.04.3

[Thiel JP]

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

Thiel JP  changed:

   What|Removed |Added

Summary|kdenlive-19.08.2-x86_64.app |kdenlive-19.08.1-x86_64.app
   |image or|image or
   |kdenlive-19.08.2b-x86_64.ap |kdenlive-19.08.2-x86_64.app
   |pimage does not start on my |image or
   |system : Ubuntu 18.04.3 |kdenlive-19.08.2b-x86_64.ap
   ||pimage does not start on my
   ||system : Ubuntu 18.04.3

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

[digikam] [Bug 412950] New: While processing new collection, any (mouse)action will result in crash of digiKam

[bugzilla_noreply]

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

Bug ID: 412950
   Summary: While processing new collection, any (mouse)action
will result in crash of digiKam
   Product: digikam
   Version: 6.3.0
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Albums-Engine
  Assignee: digikam-bugs-n...@kde.org
  Reporter: chasa.im...@xs4all.nl
  Target Milestone: ---

SUMMARY

See:
https://discuss.pixls.us/t/digikam-6-3-0-is-released/14065/8?u=panomeister


STEPS TO REPRODUCE

digiKam 6.3.0 seems to running stable… As long as I don’t select a fresh
‘collection’ e.g. a directory which has not been scanned before by digiKam. As
soon as I add a new Local Collection, digiKam starts processing this, you can
see the progress bar/percentage increasing at the bottom of the screen.

But when I move the mouse cursor around and try to select any existing Album, I
don’t get any response any more and a few seconds later, digiKam crashes…  Just
befor the mouse cursor changed into the hour-glass symbol.

With the same error message in the event log.

OBSERVED RESULT
crash!

EXPECTED RESULT
NO crash!

SOFTWARE/OS VERSIONS
Windows: 10 Pro Version 10.0.18362 Build 18362

ADDITIONAL INFORMATION

Faulting application name: digikam.exe, version: 0.0.0.0, time stamp:
0x5d6fdfed
Faulting module name: Qt5Core.dll, version: 5.13.0.0, time stamp: 0x
Exception code: 0xc602
Fault offset: 0x0032bfe1
Faulting process id: 0x2518
Faulting application start time: 0x01d582d69971b7d8
Faulting application path: C:\Program Files\digiKam\digikam.exe
Faulting module path: C:\Program Files\digiKam\Qt5Core.dll
Report Id: e4d45037-0681-4e38-91f7-5f3fa53aca15
Faulting package full name: 
Faulting package-relative application ID: 

Fault bucket 1585111947967311761, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: digikam.exe
P2: 0.0.0.0
P3: 5d6fdfed
P4: Qt5Core.dll
P5: 5.13.0.0
P6: 
P7: c602
P8: 0032bfe1
P9: 
P10:

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

[kdenlive] [Bug 412949] kdenlive-19.08.2-x86_64.appimage or kdenlive-19.08.2b-x86_64.appimage does not start on my system : Ubuntu 18.04.3

[Thiel JP]

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

Thiel JP  changed:

   What|Removed |Added

Summary|kdenlive-19.08.2-x86_64.app |kdenlive-19.08.2-x86_64.app
   |image or|image or
   |kdenlive-19.08.2b-x86_64KO. |kdenlive-19.08.2b-x86_64.ap
   |appimage does not start on  |pimage does not start on my
   |my system : Ubuntu 18.04.3  |system : Ubuntu 18.04.3

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

[kdenlive] [Bug 412949] New: kdenlive-19.08.2-x86_64.appimage or kdenlive-19.08.2b-x86_64KO.appimage does not start on my system : Ubuntu 18.04.3

[Thiel JP]

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

Bug ID: 412949
   Summary: kdenlive-19.08.2-x86_64.appimage or
kdenlive-19.08.2b-x86_64KO.appimage does not start on
my system : Ubuntu 18.04.3
   Product: kdenlive
   Version: 19.08.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: Installation
  Assignee: vpi...@kde.org
  Reporter: jeanpaul.th...@cegetel.net
  Target Milestone: ---

SUMMARY
kdenlive-19.08.2-x86_64.appimage or kdenlive-19.08.2b-x86_64KO.appimage
does not start on my system : Ubuntu 18.04.3


STEPS TO REPRODUCE
1. To start: ./kdenlive-19.08.1b-x86_64.appimage

OBSERVED RESULT in a terminal :
**
* FATAL ERROR:   *
* This OpenCV build doesn't support current CPU/HW configuration *
**
* Use OPENCV_DUMP_CONFIG=1 environment variable for details  *
**

Required baseline features:
SSE - OK
SSE2 - OK
SSE3 - OK
SSSE3 - OK
SSE4.1 - OK
POPCNT - NOT AVAILABLE
SSE4.2 - NOT AVAILABLE
terminate called after throwing an instance of 'cv::Exception'
  what():  OpenCV(4.1.0)
/build/deps-build/ext_opencv/ext_opencv-prefix/src/ext_opencv/modules/core/src/system.cpp:538:
error: (-215:Assertion failed) Missing support for required CPU baseline
features. Check OpenCV build configuration and required CPU/HW setup. in
function 'initialize'

/tmp/.mount_kdenlita3Uom/AppRun : ligne 26 : 19845 Abandon
(core dumped) kdenlive --config kdenlive-appimagerc $@


kdenlive-19.08.2-x86_64.appimage  does not start.
likewise:
kdenlive-19.08.2b-x86_64.appimage  does not start.
kdenlive-19.08.1b-x86_64.appimage  does not start.

On the other hand :
kdenlive-19.08.1-x86_64.appimage starts correctly

Linux : Ubuntu 18.04.3

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

[kmail2] [Bug 411992] kmail poorly written notification text if no password entered to collect email

[Allen Winter]

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

Allen Winter  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED
 CC||win...@kde.org

--- Comment #1 from Allen Winter  ---
patch created at https://phabricator.kde.org/D24646

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

[kmail2] [Bug 411999] kmail crashes on a base64 encoded PDF file

[Allen Winter]

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

Allen Winter  changed:

   What|Removed |Added

 CC||vkra...@kde.org,
   ||win...@kde.org

--- Comment #3 from Allen Winter  ---
of course it works fine for me.

I do see you are using a newer poppler than I am.  I'm still using poppler
0.67.
also could be a bug in kitinerary.

I'll CC Volker on this. maybe he has an idea.

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

[frameworks-kcalendarcore] [Bug 412025] Wrong timezone offset with TZID=Western/Central Europe

[Allen Winter]

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

Allen Winter  changed:

   What|Removed |Added

 CC||win...@kde.org

--- Comment #3 from Allen Winter  ---
I'm happy to see your proof-of-concent workaround.

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

[korganizer] [Bug 411994] timeline view - scroll bar in Calendar and timeline screen not correlated

[Allen Winter]

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

Allen Winter  changed:

   What|Removed |Added

 CC||win...@kde.org

--- Comment #2 from Allen Winter  ---
start making patches and upload them to https://phabricator.kde.org

we'll review them.  once we think you're ready we'll give you commit access

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

[korganizer] [Bug 412242] Feature request : double click on a reminder of an event to directly edit it

[Allen Winter]

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

--- Comment #3 from Allen Winter  ---
I'm not seeing anything broken with modern KOrganizer (version 5.12.x)

I suppose this could be something due to XFCE too.  I'm not planning to run
XFCE to test. maybe you could make a screencast showing the problem

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

[kmymoney] [Bug 412927] aqbanking not available

[Jack]

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

Jack  changed:

   What|Removed |Added

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

--- Comment #3 from Jack  ---
Feel free to reopen if Arch/Manjaro can't resolve it.

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

[lattedock] [Bug 412940] Dock background and Rearrange button are not removed when settings panel closed

[Richard Ullger]

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

--- Comment #5 from Richard Ullger  ---
System Settings > Display and Monitor > Compositor is enabled.

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

[korganizer] [Bug 412506] Adding new events always takes the whole day

[Allen Winter]

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

Allen Winter  changed:

   What|Removed |Added

 CC||win...@kde.org

--- Comment #1 from Allen Winter  ---
no idea how this can happen.

this would be a huge problem and many people would be reporting it.
I suppose there could be something with Qt5.13 that changed and broke things
badly.

for now I am unable to reproduce this.

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

[korganizer] [Bug 232162] Events, to-dos and journal entries not sorted within a day in Month view

[Allen Winter]

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

Allen Winter  changed:

   What|Removed |Added

 CC||win...@kde.org

--- Comment #2 from Allen Winter  ---
what KOrganizer version are you using?

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

[lattedock] [Bug 412940] Dock background and Rearrange button are not removed when settings panel closed

[Richard Ullger]

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

--- Comment #4 from Richard Ullger  ---
Created attachment 123187
  --> https://bugs.kde.org/attachment.cgi?id=123187=edit
Dock on left of screen

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

[lattedock] [Bug 412940] Dock background and Rearrange button are not removed when settings panel closed

[Richard Ullger]

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

--- Comment #3 from Richard Ullger  ---
Correction to item 2, the dock on the left of the screen does exhibit the same
behaviour.

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

[lattedock] [Bug 412940] Dock background and Rearrange button are not removed when settings panel closed

[Richard Ullger]

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

--- Comment #2 from Richard Ullger  ---
1. Where can I find that setting?

2. No. I have been using latte-dock for some time. It's the first time I have
seen this behaviour and probably the first time I have gone into settings while
running plasma 5.16.90 (5.17 beta) and QT 5.14.0beta1 from the kde-unstable
repo. I also have a dock on the left of the screen which does not exhibit this
behaviour.

3. Terminal output from the point of clicking the Close button on the settings
panel...

[debug 21:33:09.832832] - ConfigView deleting ...
[warning 21:33:09.934934] -
file:///usr/share/latte/indicators/default/package/config/config.qml:233:
TypeError: Cannot read property 'optionsWidth' of null
[warning 21:33:09.934934] -
file:///usr/share/latte/indicators/default/package/config/config.qml:214:
TypeError: Cannot read property 'optionsWidth' of null
[warning 21:33:09.934934] -
file:///usr/share/latte/indicators/default/package/config/config.qml:204:
TypeError: Cannot read property 'optionsWidth' of null
[warning 21:33:09.934934] -
file:///usr/share/latte/indicators/default/package/config/config.qml:108:
TypeError: Cannot read property 'optionsWidth' of null
[warning 21:33:09.934934] -
file:///usr/share/latte/indicators/default/package/config/config.qml:48:
TypeError: Cannot read property 'optionsWidth' of null
[debug 21:33:09.9797] - Latte::QuickWindowSystem destructed
[warning 21:33:09.99] - "" doesn't have any WindowType, assuming as
NET::Normal
[warning 21:33:10.001001] - "" doesn't have any WindowType, assuming as
NET::Normal
[warning 21:33:10.002002] - "" doesn't have any WindowType, assuming as
NET::Normal
[debug 21:33:10.005005] - SecDockConfigView deleting ...
[debug 21:33:10.0101] - Latte::QuickWindowSystem destructed
[warning 21:33:10.028028] - "" doesn't have any WindowType, assuming as
NET::Normal
[warning 21:33:10.031031] - "" doesn't have any WindowType, assuming as
NET::Normal
[warning 21:33:10.052052] - "" doesn't have any WindowType, assuming as
NET::Normal
[warning 21:33:10.053053] - "" doesn't have any WindowType, assuming as
NET::Normal

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

[plasmashell] [Bug 412781] Various graphical glitches since Qt5.14

[petrk]

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

--- Comment #18 from petrk  ---
Everything seems to be fixed, except incorrect fonts in context menus.

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

[digikam] [Bug 412921] BatchQueueManager: change file format

[00pippo]

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

--- Comment #4 from 00pippo  ---
(In reply to Maik Qualmann from comment #3)
> If I use a JPEG quality of 95-98 similar to the files of my camera, the file
> size is quite identical. What kind of editing do you do on the images? The
> tools to save are in the same list as the editing tools "Convert to ..."
> These will be added to the end of an edit queue.
> 
> Maik

A I said, my files are only about half the size. I have a Sony alpha 6000. Does
that camera use an inefficient jpeg compression mode?
Besides, JPEG2000 as well as PNG are about 3-5 times as big as the original
from the camera (tried with digikam 6.2.0)...

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

[digikam] [Bug 412948] New: Deleting a versioned file leaves original hidden in thumbnail view

[Han Holl]

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

Bug ID: 412948
   Summary: Deleting a versioned file leaves original hidden in
thumbnail view
   Product: digikam
   Version: 6.1.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Versioning
  Assignee: digikam-bugs-n...@kde.org
  Reporter: han.h...@pobox.com
  Target Milestone: ---

SUMMARY
Create a _v1 version of any photograph.
The original is no longer visible in the thumbnail view.



STEPS TO REPRODUCE
1. Create a _v1 version of any photograph.
2. Delete the _v1 file
3. 

OBSERVED RESULT
The original file is not visible in the thumbnail view.
It is of course visble in the table view.

EXPECTED RESULT
Original file should be visible

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.5

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

[Gerry Makaro aka Fraser_Bell]

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

--- Comment #315 from Gerry Makaro aka Fraser_Bell  
---
(In reply to Nate Graham from comment #314)
> You don't close an open bug just because it hasn't gotten implemented yet
> and people are frustrated by this. If you want the honest truth, here it is:
> 
> We know that this is an irritation and we do want to fix it. However doing
> so requires untangling some of the code  behind the Activities feature,
> which is where per/workspace wallpapers got moved to during a prior Plasma
> version. We understand how that this was probably a mistake, and that
> Activities unfortunately never got the proper support and took off like we'd
> hoped, and we want to merge the functionality of Activities back into
> Virtual Desktops, possibly under the new umbrella name "Workspaces" or
> something like that. This merge would result in the feature having both the
> features of Virtual Desktops and also Activities. We discussed this a lot at
> Akademy 2018 but the work got delayed by other matters, sorry about that. We
> hope to pick it up again, and in either case it's a requirement before we
> can call Wayland done (which takes on an elevated level of importance now
> that it's been selected as a community goal).
> 
> It's super duper frustrating to have to wait so long. I understand and
> sympathize. I'm going to have to ask for a bit more patience though, because
> we want to fix this in the right way, which takes a bit longer than just
> hacking it back in quickly.

Okay, now this is a very good explanation of what is going on.  So, once this
gets worked out, the feature will be back in some future version of the
desktop.

Explanations like this and a "Where we're at ..." post on occasion would help
mitigate some of the frustration, I think.

Thanks

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

[digikam] [Bug 406019] Corrupted image thumbnail on some pictures

[Maik Qualmann]

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

--- Comment #10 from Maik Qualmann  ---
Git commit 20dbf8abadbeac5cc093e8283f0e105c9d763be5 by Maik Qualmann.
Committed on 14/10/2019 at 19:35.
Pushed by mqualmann into branch 'master'.

try revert a older commit

M  +4-4core/libs/threadimageio/engine/managedloadsavethread.cpp

https://invent.kde.org/kde/digikam/commit/20dbf8abadbeac5cc093e8283f0e105c9d763be5

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

[klipper] [Bug 407606] Clipboard icon does't appear after copying something on Wayland

[mthw0]

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

--- Comment #4 from mthw0  ---
(In reply to Konrad Materka from comment #3)
> Probably a duplicate of BUG 412350

That seems like the same thing, which report should we keep? This one for being
older or the other one for having more info?

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

[systemsettings] [Bug 407689] Preview of sddm themes and icons look pixelated in "Startup and Shutdown" when fractional display scale is used

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||5.17.1

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

[plasmashell] [Bug 356937] Xembed icons have black background

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In|5.17.1  |5.18

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

[plasmashell] [Bug 412947] New: Crash while clicking 'Help' button on the Global Menu of System Settings

[Jig]

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

Bug ID: 412947
   Summary: Crash while clicking 'Help' button on the Global Menu
of System Settings
   Product: plasmashell
   Version: 5.16.5
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: jig.pa...@live.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.16.5)

Qt Version: 5.13.1
Frameworks Version: 5.62.0
Operating System: Linux 5.3.5-arch1-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
I had opened System Settings and then I clicked Help button. The KDE system
crashed and desktop background gone black. It came back on its own. I clicked
the same button again and it couldn't restart itself.

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

Thread 7 (Thread 0x7f5f0ffe7700 (LWP 1062)):
#0  0x7f5f40701c45 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f5f41236660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt5Core.so.5
#2  0x7f5f41236752 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#3  0x7f5f4301adad in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f5f4301b05e in  () at /usr/lib/libQt5Quick.so.5
#5  0x7f5f412305b0 in  () at /usr/lib/libQt5Core.so.5
#6  0x7f5f406fb4cf in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f5f40ebc2d3 in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f5f1d1a1700 (LWP 1054)):
#0  0x7f5f40eb19ef in poll () at /usr/lib/libc.so.6
#1  0x7f5f3f6d0180 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f5f3f6d0251 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f5f41456a1c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f5f413fd4ec in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f5f4122f385 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f5f412305b0 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f5f406fb4cf in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f5f40ebc2d3 in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f5f265b1700 (LWP 1034)):
#0  0x7f5f40701c45 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f5f41236660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt5Core.so.5
#2  0x7f5f41236752 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#3  0x7f5f4301adad in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f5f4301b05e in  () at /usr/lib/libQt5Quick.so.5
#5  0x7f5f412305b0 in  () at /usr/lib/libQt5Core.so.5
#6  0x7f5f406fb4cf in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f5f40ebc2d3 in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f5f283ad700 (LWP 1030)):
#0  0x7f5f40eb19ef in poll () at /usr/lib/libc.so.6
#1  0x7f5f3f6d0180 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f5f3f6d0251 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f5f41456a1c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f5f413fd4ec in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f5f4122f385 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f5f42f8f6eb in  () at /usr/lib/libQt5Quick.so.5
#7  0x7f5f412305b0 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f5f406fb4cf in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f5f40ebc2d3 in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f5f398e3700 (LWP 1003)):
#0  0x7f5f40ead42c in read () at /usr/lib/libc.so.6
#1  0x7f5f3f6809f0 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f5f3f6cea41 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7f5f3f6d0128 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7f5f3f6d0251 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7f5f41456a1c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7f5f413fd4ec in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7f5f4122f385 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7f5f42caf849 in  () at /usr/lib/libQt5Qml.so.5
#9  0x7f5f412305b0 in  () at /usr/lib/libQt5Core.so.5
#10 0x7f5f406fb4cf in start_thread () at /usr/lib/libpthread.so.0
#11 0x7f5f40ebc2d3 in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f5f3ab51700 (LWP 965)):
#0  0x7f5f40eb19ef in poll () at /usr/lib/libc.so.6
#1  0x7f5f3f6d0180 in  () at 

[frameworks-solid] [Bug 412945] ISO image "inserted" with cdemu client disappears from "Removable devices" section after Dolphin to be restarted

[Nick Stefanov]

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

Nick Stefanov  changed:

   What|Removed |Added

 CC||m...@abv.bg

--- Comment #1 from Nick Stefanov  ---
But it can't be ejected via Dolphin's unmount context menu and the ISO is still
occupying the device and you can't mount new image until unmoint the already
mounted image via CDEmu.

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

[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling

[bugzilla_noreply]

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

undyin...@gmail.com changed:

   What|Removed |Added

 CC||undyin...@gmail.com

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

[krita] [Bug 412946] Changing the stroke of a vector to a gradient causes Krita to freeze

[Tymond]

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

Tymond  changed:

   What|Removed |Added

 CC||tamtamy.tym...@gmail.com
 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Tymond  ---


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

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

[frameworks-solid] [Bug 394348] Umounting mounted disk image (e.g. .iso file) does not remove it from Device Notifier

[Patrick Silva]

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

--- Comment #79 from Patrick Silva  ---
(In reply to Nick Stefanov from comment #78)
> I noticed something interesting - if I unmount the previously mounted disk
> via device notifier or Dolphin and I close Dolphin, the mounted image is
> gone from the side bar's devices section after I open Dolphin again. But the
> device isn't released and no image can be mounted until I unmount the
> previous image via CDEmu or restart.

I have just reported an issue that seems related to your comment. See bug
412945.

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

[krita] [Bug 412746] Select gradient fill for vector shape stroke, krita freezes

[Tymond]

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

Tymond  changed:

   What|Removed |Added

 CC||10nesc...@gmail.com

--- Comment #5 from Tymond  ---
*** Bug 412946 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 365105] QSystemTrayIcon with context menu does not react after second show

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|REOPENED|CONFIRMED
 CC||n...@kde.org

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

[krita] [Bug 412946] New: Changing the stroke of a vector to a gradient causes Krita to freeze

[bugzilla_noreply]

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

Bug ID: 412946
   Summary: Changing the stroke of a vector to a gradient causes
Krita to freeze
   Product: krita
   Version: 4.2.7
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Tools/Vector
  Assignee: krita-bugs-n...@kde.org
  Reporter: 10nesc...@gmail.com
  Target Milestone: ---

SUMMARY
When putting a gradient on the stroke of a vector Krita will become
unresponsive, though changing the fill to a gradient still works

STEPS TO REPRODUCE
1. Open Krita and create a file with a vector layer
2. Make a vector of any shape or size
3. Using the Tool Options docker change the stroke from "Solid" to "Gradient
fill"

OBSERVED RESULT
Krita hangs indefinitely

EXPECTED RESULT
A simple default gradient gets applied 

SOFTWARE/OS VERSIONS
Windows: 10

ADDITIONAL INFORMATION
This use case was working in 4.2.6

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

[frameworks-solid] [Bug 412945] New: ISO image "inserted" with cdemu client disappears from "Removable devices" section after Dolphin to be restarted

[Patrick Silva]

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

Bug ID: 412945
   Summary: ISO image "inserted" with cdemu client disappears from
"Removable devices" section after Dolphin to be
restarted
   Product: frameworks-solid
   Version: 5.63.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: lu...@kde.org
  Reporter: bugsefor...@gmx.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

STEPS TO REPRODUCE
1. open Dolphin
2. right click on an ISO image (I tested with Arch Linux ISO), select "Open
with cdemu client"
(an entry related to the ISO image appears in Places panel under "Removable
devices", as expected).
3. Restart Dolphin

OBSERVED RESULT
The entry of the ISO image disappeared from "Removable devices" section in
Places panel.
However the "inserted" ISO is still listed by devices notifier in the system
tray.

EXPECTED RESULT
The entry of the ISO image should be present under "Removable devices" section
of Places panel
after Dolphin to be restarted.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.16.90
KDE Frameworks Version: 5.63.0
Qt Version: 5.14.0 beta1

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

[plasmashell] [Bug 365105] QSystemTrayIcon with context menu does not react after second show

[Konrad Materka]

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

Konrad Materka  changed:

   What|Removed |Added

 CC||h...@urpla.net

--- Comment #12 from Konrad Materka  ---
*** Bug 411851 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 411851] Systray icons loose connected actions, if hidden once

[Konrad Materka]

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

Konrad Materka  changed:

   What|Removed |Added

 Resolution|NOT A BUG   |DUPLICATE

--- Comment #3 from Konrad Materka  ---
Sorry, I was too quick with the judge. This is a KDE error, already reported.
This is a duplicate of BUG 365105.

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

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

[kfontview] [Bug 407294] KFontView does not display font previews properly on hidpi screen with scaling

[hexchain]

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

hexchain  changed:

   What|Removed |Added

Version|5.15.4  |5.16.90
 CC||i...@hexchain.org

--- Comment #2 from hexchain  ---
Reproduced with 5.16.90 on Arch Linux X11. The scaling factor is 2.

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

[digikam] [Bug 412944] Wrong Piwigo version parsing (2.10.x < 2.4)

[Eike Rathke]

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

--- Comment #2 from Eike Rathke  ---
Thanks for the fast fix!
While that likely will work, d->version will not match the proper version
though, as it will be calculated as 20+10=30 (which is >24 so that part should
be ok), mimicking a 3.0. Just mentioning in case d->version is used for other
purposes as well, I didn't check; or in future needs to compare against a
future version where "3.0" 30 would be less than "2.15" 35 ...

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

[bugs.kde.org] [Bug 412299] A ticket can have both resolution INTENTIONAL and status RESOLVED

[Nate Graham]

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

--- Comment #8 from Nate Graham  ---
(In reply to Filipus Klutiero from comment #7)
> Ehm, and where in this report do you think I am being pedantic regarding the
> resolution statuses?
In everything you've written in this and several other bug reports. :)

(In reply to Filipus Klutiero from comment #7)
> Nate, considering that you demonstrated your misunderstanding of statuses in
> https://community.kde.org/index.php?title=Get_Involved/
> Bug_Reporting=79358=79286 and even more recently on this very
> site, I have to ask: do you have understand that RESOLVED and INTENTIONAL
> were not designed to be used together (or - to put it simply - that they are
> incompatible)?
You can keep claiming this, but I'm afraid it won't change anything. Your
understanding is not accurate. We can and do use the RESOLVED and INTENTIONAL
statuses together to mean "this bug report is closed because the software that
you believe is behaving incorrectly is in fact behaving exactly the way we
intend it to behave". Thousands of bugs have been closed with RESOLVED
INTENTIONAL and that meaning. That's just what it means, sorry. If you don't
like that, you'll have to get used to it, or start a discussion in the
kde-devel mailing list proposing that we change it.

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

[digikam] [Bug 406019] Corrupted image thumbnail on some pictures

[Maik Qualmann]

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

--- Comment #9 from Maik Qualmann  ---
I can reproduce the problem very confidently on a Windows7 computer in my
company. Namely when a new collection is added or you start with an empty DB
and the thumbnails are created on the first scan. Later with F5 the problem
does not occur anymore. There are no error messages, but loading the thumbnail
via DImg must generate a NULL image.

Maik

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

[plasmashell] [Bug 356937] Xembed icons have black background

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[Akonadi] [Bug 411093] Unable to start Akonadi: Could not open required defaults file

[Dmitry]

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

Dmitry  changed:

   What|Removed |Added

 CC||dmitry-kog...@mail.ru

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

[digikam] [Bug 412944] Wrong Piwigo version parsing (2.10.x < 2.4)

[bugzilla_noreply]

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

   Version Fixed In||6.4.0
  Latest Commit||https://invent.kde.org/kde/
   ||digikam/commit/402a88c480da
   ||f819275470518e1a26c22c9efcd
   ||4
 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from caulier.gil...@gmail.com ---
Git commit 402a88c480daf819275470518e1a26c22c9efcd4 by Gilles Caulier.
Committed on 14/10/2019 at 17:55.
Pushed by cgilles into branch 'master'.

fix wrong piwigo version parsed by talker
FIXED-IN: 6.4.0

M  +1-1core/dplugins/generic/webservices/piwigo/piwigotalker.cpp

https://invent.kde.org/kde/digikam/commit/402a88c480daf819275470518e1a26c22c9efcd4

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

[digikam] [Bug 412944] New: Wrong Piwigo version parsing (2.10.x < 2.4)

[Eike Rathke]

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

Bug ID: 412944
   Summary: Wrong Piwigo version parsing (2.10.x < 2.4)
   Product: digikam
   Version: unspecified
  Platform: Other
OS: All
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Plugin-WebService-Piwigo
  Assignee: digikam-bugs-n...@kde.org
  Reporter: er...@erack.de
CC: frederic.coiff...@free.fr
  Target Milestone: ---

With a recent Piwigo version 2.10.0 or 2.10.1 the plugin refuses to work,
saying

"Failed to login into remote piwigo. Upload to Piwigo version < 2.4 is no
longer supported."

The cause is in ./core/dplugins/generic/webservices/piwigo/piwigotalker.cpp
line 487 in PiwigoTalker::parseResponseGetVersion() where the regex

  QRegExp verrx(QLatin1String(".?(\\d)\\.(\\d).*"));

extracts only two digits (here '2' and '1' of "2.10.1") that then later in line
509 are calculated as

  d->version   = qsl[1].toInt() * 10 + qsl[2].toInt();

resulting in 20+1 thus the value 21 which is less than 24.

A correct attempt would be to allow at least 2 (better more) digits for each
major.minor, hence

  QRegExp verrx(QLatin1String(".?(\\d+)\\.(\\d+).*"));

and for example

  d->version   = qsl[1].toInt() * 1000 + qsl[2].toInt();

that would work with up to 3 digits per minor.

The error occurred also in digikam 5.9.0 Piwigo export kipi plugin.

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

[krita] [Bug 412943] Use System Monitor Profile checkbox attributes wrong profile to screens, breaking color management

[Tyson Tan]

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

--- Comment #2 from Tyson Tan  ---
(In reply to wolthera from comment #1)
> Hey Tyson, can you give your operating system information? It's rather vital
> here as everything behaves differently in each operating system :)

Hi Wolthera,
I think this is not OS specific, but I tested them on the following:

Manjaro KDE 18.1.0
Manjaro Gnome 18.1.0
Fedora Gnome 31 beta
Windwos 10 1903
2 different machines in 2 locations

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

[systemsettings] [Bug 412913] Initial loading is broken

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[kate] [Bug 412799] Editing shortcuts are not wokring

[Benji Dial]

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

Benji Dial  changed:

   What|Removed |Added

 CC||benji6...@gmail.com
 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Benji Dial  ---
This works fine for me with KWrite 19.04.2 on Fedora.  What version of KWrite
are you using?  Do you have any other settings changed from the defaults that
might be causing this issue?

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

[krita] [Bug 412943] Use System Monitor Profile checkbox attributes wrong profile to screens, breaking color management

[wolthera]

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

wolthera  changed:

   What|Removed |Added

 CC||griffinval...@gmail.com

--- Comment #1 from wolthera  ---
Hey Tyson, can you give your operating system information? It's rather vital
here as everything behaves differently in each operating system :)

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

[krita] [Bug 412943] New: Use System Monitor Profile checkbox attributes wrong profile to screens, breaking color management

[Tyson Tan]

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

Bug ID: 412943
   Summary: Use System Monitor Profile checkbox attributes wrong
profile to screens, breaking color management
   Product: krita
   Version: unspecified
  Platform: Other
OS: All
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: tysont...@gmail.com
  Target Milestone: ---

When the checkbox:
Configure Krita -> Color Management -> [ ] Use system monitor profile
is checked...

Krita is expected to automatically attribute color profiles set in the OS's
Color Management panel to each screen accordingly. However, in multi-screen
scenarios, it sometimes attributes profiles to the wrong displays.

#

The problem appears to be:

The screen list underneath the checkbox:
Screen 1:
Screen 2:
...

Krita gets this list from the system's Display settings panel. For KDE Plasma,
Screen 1 is the "Primary" screen set in Plasma's Display settings. For Windows
and Gnome, Screen 1 is the display plugged into the connector with highest
priority.

But when it comes to actually applying the profiles, the top-left screen is
always #1. This often cause profiles to be attributed to the wrong displays,
breaking color accuracy in a color managed workflow.

#

Workaround:
A) For dual screen, manually adding 2 profiles using the "Folder" icon below,
assign them in reversed order to what the "Use system monitor profile"
checkbox's automatically does.

B) KDE Plasma only: Make the top-left display "Primary".

I have no idea how we deal with this issue if we had more than 2 displays. :P

#

Notes:
I think this is the exact bug that plagued me all these years, causing my color
management effort to fail since my first day as a Krita user -- I always use 2
monitors, and the lower one is always set to "Primary" or #1 in the system's
Display settings. I was perplexed by things like the dark areas being too
black, but since 2 monitors were both sRGB, and they had outstanding color
accuracy, I never had any clue.

Recently I replaced all my old displays. My top display is still sRGB, but the
lower one is now AdobeRGB. After calibration and profiling, the sheer amount of
over-saturation on the lower screen and the de-saturation on the top screen
naturally led me to the assumption that the sRGB display's profile was applied
to the AdobeRGB display, and vise versa. I was right, and I tested my theory on
KDE Plasma, Gnome, Windows 10. It happened everywhere.

I think this issue should be consider critical -- it breaks color accuracy in a
properly configured color managed workflow. Thanks to this bug, many of my
previous pictures are irreversibly affected in a bad way. Thank god I'm mostly
a hobbyist XD. I suggest if we can't fix the bug soon, we at least remove that
checkbox and add a warning below the screen list.

#

Possibly related:
https://bugs.kde.org/show_bug.cgi?id=412393
https://bugs.kde.org/show_bug.cgi?id=407498
https://bugs.kde.org/show_bug.cgi?id=412608

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

[dolphin] [Bug 412698] When right clicking on a text file to edit Dolphin hangs along with the plasma desktop widgets

[Benji Dial]

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

Benji Dial  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||benji6...@gmail.com
 Status|REPORTED|NEEDSINFO

--- Comment #1 from Benji Dial  ---
Can you upload the file you were trying to edit as an attachment here?

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

[krita] [Bug 411863] Artifacts appear when using HSV adjustments

[Dmitry Kazakov]

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

Dmitry Kazakov  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/kde/
   ||krita/commit/f68e3ef17af7ac
   ||913a657f7b5106894bc6a9acf0
 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED
  Latest Commit|https://invent.kde.org/kde/ |
   |krita/commit/f68e3ef17af7ac |
   |913a657f7b5106894bc6a9acf0  |
 Status|RESOLVED|ASSIGNED
 Resolution|FIXED   |---

--- Comment #5 from Dmitry Kazakov  ---
Git commit f68e3ef17af7ac913a657f7b5106894bc6a9acf0 by Dmitry Kazakov.
Committed on 14/10/2019 at 16:04.
Pushed by dkazakov into branch 'master'.

Fix HSL, HSV, HCI and HCY transformations for white and black images

Basically, the transformations are substituted with their chroma-based
counterparts, with clever sliding on the edges of the triangle.

The new filters behave a bit differently, therefore the patch adds
a "Compatibility Mode" switch for the filter. It enables old behavior.

M  +12   -8libs/global/kis_global.h
M  +370  -75   plugins/color/colorspaceextensions/kis_hsv_adjustment.cpp
M  +13   -0plugins/filters/colorsfilters/kis_hsv_adjustment_filter.cpp
M  +7-0plugins/filters/colorsfilters/wdg_hsv_adjustment.ui

https://invent.kde.org/kde/krita/commit/f68e3ef17af7ac913a657f7b5106894bc6a9acf0

--- Comment #6 from Dmitry Kazakov  ---
Git commit 4cbf5ef4826b72bb13b8e1951f4df9cdf7124a82 by Dmitry Kazakov.
Committed on 14/10/2019 at 16:04.
Pushed by dkazakov into branch 'master'.

Fix backward compatibility for filter layers which don't have new keys

Some filter configurations (e.g. HSV-filter) expect that older configs
don't have newly introduced keys (e.g. "compatibilityMode"). Therefore
we shouldn't use default filter configuration as a source when loading
the layer. Instead, we should create a new one, and only then load.

M  +8-6plugins/impex/libkra/kis_kra_load_visitor.cpp
M  +2-1plugins/impex/libkra/kis_kra_load_visitor.h

https://invent.kde.org/kde/krita/commit/4cbf5ef4826b72bb13b8e1951f4df9cdf7124a82

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

[krita] [Bug 411863] Artifacts appear when using HSV adjustments

[Dmitry Kazakov]

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

Dmitry Kazakov  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/kde/
   ||krita/commit/f68e3ef17af7ac
   ||913a657f7b5106894bc6a9acf0
 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

--- Comment #5 from Dmitry Kazakov  ---
Git commit f68e3ef17af7ac913a657f7b5106894bc6a9acf0 by Dmitry Kazakov.
Committed on 14/10/2019 at 16:04.
Pushed by dkazakov into branch 'master'.

Fix HSL, HSV, HCI and HCY transformations for white and black images

Basically, the transformations are substituted with their chroma-based
counterparts, with clever sliding on the edges of the triangle.

The new filters behave a bit differently, therefore the patch adds
a "Compatibility Mode" switch for the filter. It enables old behavior.

M  +12   -8libs/global/kis_global.h
M  +370  -75   plugins/color/colorspaceextensions/kis_hsv_adjustment.cpp
M  +13   -0plugins/filters/colorsfilters/kis_hsv_adjustment_filter.cpp
M  +7-0plugins/filters/colorsfilters/wdg_hsv_adjustment.ui

https://invent.kde.org/kde/krita/commit/f68e3ef17af7ac913a657f7b5106894bc6a9acf0

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

[Akonadi] [Bug 411093] Unable to start Akonadi: Could not open required defaults file

[Alexander Zhigalin]

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

Alexander Zhigalin  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |---
Version|5.12.0  |GIT (master)
 CC||alexan...@zhigalin.tk
 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED

--- Comment #7 from Alexander Zhigalin  ---
The worksforme status is for bugs which can't be reproduced.

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

[korganizer] [Bug 412833] Monthview shows comma in year

[Allen Winter]

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

--- Comment #2 from Allen Winter  ---
patch is up for review at https://phabricator.kde.org/D24638

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

[klipper] [Bug 407606] Clipboard icon does't appear after copying something on Wayland

[Konrad Materka]

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

--- Comment #3 from Konrad Materka  ---
Probably a duplicate of BUG 412350

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

[klipper] [Bug 407606] Clipboard icon does't appear after copying something on Wayland

[Konrad Materka]

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

Konrad Materka  changed:

   What|Removed |Added

  Component|System Tray |plasma-widget
Summary|Clipboard icon does't   |Clipboard icon does't
   |appear after copying|appear after copying
   |something   |something on Wayland
   Target Milestone|1.0 |---
Product|plasmashell |klipper

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

[Nate Graham]

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

--- Comment #314 from Nate Graham  ---
You don't close an open bug just because it hasn't gotten implemented yet and
people are frustrated by this. If you want the honest truth, here it is:

We know that this is an irritation and we do want to fix it. However doing so
requires untangling some of the code  behind the Activities feature, which is
where per/workspace wallpapers got moved to during a prior Plasma version. We
understand how that this was probably a mistake, and that Activities
unfortunately never got the proper support and took off like we'd hoped, and we
want to merge the functionality of Activities back into Virtual Desktops,
possibly under the new umbrella name "Workspaces" or something like that. This
merge would result in the feature having both the features of Virtual Desktops
and also Activities. We discussed this a lot at Akademy 2018 but the work got
delayed by other matters, sorry about that. We hope to pick it up again, and in
either case it's a requirement before we can call Wayland done (which takes on
an elevated level of importance now that it's been selected as a community
goal).

It's super duper frustrating to have to wait so long. I understand and
sympathize. I'm going to have to ask for a bit more patience though, because we
want to fix this in the right way, which takes a bit longer than just hacking
it back in quickly.

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

[systemsettings] [Bug 412942] New: Add-on Installer's title does not follow color scheme.

[Benji Dial]

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

Bug ID: 412942
   Summary: Add-on Installer's title does not follow color scheme.
   Product: systemsettings
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: benji6...@gmail.com
  Target Milestone: ---

Created attachment 123186
  --> https://bugs.kde.org/attachment.cgi?id=123186=edit
screenshot of the add-on installer

SUMMARY
The title of the Add-on Installer window stays black on a white background no
matter the color scheme.

STEPS TO REPRODUCE
1. Change the color theme.
2. Go to the Add-on Installer.

OBSERVED RESULT
Black text on a white background.

EXPECTED RESULT
Colors matching the applied theme.

SOFTWARE/OS VERSIONS
Fedora Linux 5.2.18
KDE Plasma 5.15.5
KDE Frameworks 5.59.0
Qt 5.12.5

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

[bugzilla_noreply]

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

--- Comment #313 from aschn...@gmx.net ---
KDE Plasma 5.16.90 Released and still no sign of different Wallpapers. 
But "Wallpaper slideshows can now have user-chosen ordering rather than always
being random." Very nice.
@Nate Graham: Hey, Nate, why don't you be honest and close this bug as "Will
not be fixed"? After more than 5 years nothing will happen anyway.

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

[kstars] [Bug 412941] New: Solver fails; unusual decect in captured FITs green layer

[Larry White]

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

Bug ID: 412941
   Summary: Solver fails; unusual decect in captured FITs green
layer
   Product: kstars
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: larryhwh...@bendbroadband.com
  Target Milestone: ---

Created attachment 123185
  --> https://bugs.kde.org/attachment.cgi?id=123185=edit
Screen capture of kstars FITs viewer

SUMMARY
Solver fails.  Multiple times with different iso and exposure times.
Captured FITs have full width rectangular area on green plane that is off
color.
Using Linux/kstars with Celestron AVX/Explore Scientific/AR127/Canon 70D.

STEPS TO REPRODUCE
1. Run alignment routine
2. Capture and solve
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
Both vignetting and rectangular defect are enhanced by kstars view compared to
viewing in GIMP, Siril or fv5.5.
Vignetting is likely due to telescope.
However, full width rectangular area could be camera or kstars.  Suspect kstars
because images taken before and since with camera do not show defect in RAW or
JPG files.

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