date:20191201

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

Evert Vorster  changed:

   What|Removed |Added

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

--- Comment #24 from Evert Vorster  ---
I can now apply layouts at will, without Kdenlive crashing and movit enabled

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

[kdenlive] [Bug 361087] git master 2016-03-28:Movit: Application crash when dragging a clip to timeline

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

Evert Vorster  changed:

   What|Removed |Added

Version|unspecified |git-master

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

[kdenlive] [Bug 361087] git master 2016-03-28:Movit: Application crash when dragging a clip to timeline

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

--- Comment #11 from Evert Vorster  ---
I can still segfault kdenlive at will by enabling the movit library, and then
dragging a clip to the timeline and clicking back and forth between clip
monitor and project monitor. 
Date 2019-12-02

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

[kdenlive] [Bug 361087] git master 2016-03-28:Movit: Application crash when dragging a clip to timeline

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

--- Comment #10 from Evert Vorster  ---
Created attachment 124255
  --> https://bugs.kde.org/attachment.cgi?id=124255=edit
GDB Backtrace

The backtrace of the GNU debugger, for people who are interested

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

[kdenlive] [Bug 361087] git master 2016-03-28:Movit: Application crash when dragging a clip to timeline

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

--- Comment #9 from Evert Vorster  ---
Created attachment 124254
  --> https://bugs.kde.org/attachment.cgi?id=124254=edit
Console Output 2019-12-02

The console output, for people who might be interested

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

[calligraplan] [Bug 414741] New: Only description is updated when new version of a package is received

2019-12-01 Thread Dag Andersen

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

Bug ID: 414741
   Summary: Only description is updated when new version of a
package is received
   Product: calligraplan
   Version: 3.2.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: work
  Assignee: dand...@get2net.dk
  Reporter: dand...@get2net.dk
  Target Milestone: ---

SUMMARY
Probably needs a merge dialog

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.

[kdenlive] [Bug 364888] git-master:2016-06-29:Stabilize clips on timeline.

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

Evert Vorster  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |NOT A BUG

--- Comment #1 from Evert Vorster  ---
I have been using the clip effects, and have gotten used to them. The extra
clips and such is not such a big hassle afterall. Closing this bug/feature
request

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

[kdenlive] [Bug 364531] 16.04 from git - libavfilter Deshake effect filter crashes application, and does not work.

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

Evert Vorster  changed:

   What|Removed |Added

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

--- Comment #4 from Evert Vorster  ---
Well, not technically a fix, but as the deshake filter is not available
anymore, this bug is moot.

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

[digikam] [Bug 414737] DigiKam becomes unresponsive when clicking on NFS-mounted photos

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

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

   What|Removed |Added

  Component|general |Database-Media

--- Comment #3 from caulier.gil...@gmail.com ---
Please check with official last stable 6.4.0 release:

https://www.digikam.org/download/

...or with current 7.0.0 pre release bundles available here :

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

Gilles Caulier

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

[kdenlive] [Bug 381223] Custom Profile handling bugs

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

Evert Vorster  changed:

   What|Removed |Added

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

--- Comment #17 from Evert Vorster  ---
The second issue got fixed somewhere, as Kdenlive now correctly detects the
custom profile if a clip with matching parameters is loaded. 

Completely fixed!

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

[apper] [Bug 414740] New: Apper stopped while uninstalling a program

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

Bug ID: 414740
   Summary: Apper stopped while uninstalling a program
   Product: apper
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dantt...@gmail.com
  Reporter: 97carm...@protonmail.com
  Target Milestone: ---

Application: apper (0.9.3)

Qt Version: 5.7.1
Frameworks Version: 5.28.0
Operating System: Linux 4.9.0-11-amd64 x86_64
Distribution: Devuan GNU/Linux 2.1 (ascii)

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

I had just uninstalled Kmix using Apper, I opened Apper again, nothing
happened, I opened Apper again and the error was shown

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

Thread 4 (Thread 0x7fcb377fe700 (LWP 25417)):
#0  0x7fcb5559f92d in read () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7fcb574eee20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fcb574aa4be in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fcb574aa994 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fcb574aad82 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fcb57a92656 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#6  0x7fcb574d24a5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7fcb539304a4 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#8  0x7fcb555acd0f in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 3 (Thread 0x7fcb37fff700 (LWP 25416)):
#0  0x7fcb555a38bd in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7fcb574aa9f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fcb574aab0c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fcb574aab51 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fcb574d24a5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fcb539304a4 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#6  0x7fcb555acd0f in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 2 (Thread 0x7fcb44deb700 (LWP 25412)):
#0  0x7fcb5559f92d in read () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7fcb574eee20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fcb574aa4be in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fcb574aa994 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fcb574aab0c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fcb563d21eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fcb5637bd1a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fcb561aa093 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fcb5d7386e5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#9  0x7fcb561aed48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7fcb539304a4 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#11 0x7fcb555acd0f in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 1 (Thread 0x7fcb5d652940 (LWP 25410)):
[KCrash Handler]
#6  0x7fcb56c36140 in QWindow::parent() const () from
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#7  0x7fcb56c21021 in QPlatformWindow::parent() const () from
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#8  0x7fcb482ee805 in QXcbWindow::hide() () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#9  0x7fcb56c3b20c in QWindow::setVisible(bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#10 0x7fcb58133c37 in QWidgetPrivate::hide_sys() () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x7fcb5813a27d in QWidgetPrivate::hide_helper() () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x7fcb5813eca0 in QWidget::setVisible(bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x7fcb582e6632 in QDialog::setVisible(bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x7fcb582e4d42 in QDialog::done(int) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x7fcb582e4711 in QDialog::closeEvent(QCloseEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x7fcb5d3fe7d5 in KCMultiDialog::closeEvent(QCloseEvent*) () from
/usr/lib/x86_64-linux-gnu/libKF5KCMUtils.so.5
#17 0x7fcb5813f118 in QWidget::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x7fcb580f7b8c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19

[kdenlive] [Bug 381223] Custom Profile handling bugs

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

--- Comment #16 from Evert Vorster  ---
I am able to make completely custom video profiles... just to test I created a
profile with 336 x 666 x 13fps. Kdenlive smoothly accepted it, it was just a
little tricky to generate. 
Project > Project Settings > Click on the Sliders Icon. 
Click on the "New" button
Have at it, just change the name to something unique. 
When you are happy with the new profile, click on the "Save" icon. Your new
profile will now be under the Custom profiles.

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

[digikam] [Bug 414737] DigiKam becomes unresponsive when clicking on NFS-mounted photos

2019-12-01 Thread Maik Qualmann

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #2 from Maik Qualmann  ---
The crash at this point is not unknown. We used a CoreDbAccess here to
synchronize the access. Meanwhile we use a QReadLocker. The crash should be
fixed in a more recent digiKam version.

Maik

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

[kdenlive] [Bug 404680] timeline refactor 2019-02-21_Composition effect issues.

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

Evert Vorster  changed:

   What|Removed |Added

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

--- Comment #11 from Evert Vorster  ---
This one is fixed, thanks JBM

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

[kdenlive] [Bug 410382] fit Width in transform effect not working properly

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

Evert Vorster  changed:

   What|Removed |Added

Version|19.04.1 |git-master

--- Comment #4 from Evert Vorster  ---
Hi there!

This bug still persists in the 19.12 release candidate, built from 19.12 branch
on 2019-12-02

As the stabilized footage "moves" on the larger canvas, maybe this is the
correct behavior. I guess I was more expecting the fit to width button to zoom
to fit the width of the clip that the *.mlt file was made from. 

I can still get the desired effect by zooming, and the center clip buttons do
work, so not a train smash.

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

[kdenlive] [Bug 388729] Speed change has no effect on *.mlt files

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

Evert Vorster  changed:

   What|Removed |Added

Version|19.04.0 |18.12.3
   Assignee|vpi...@kde.org  |j...@kdenlive.org

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

[kdenlive] [Bug 388729] Speed change has no effect on *.mlt files

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

--- Comment #18 from Evert Vorster  ---
This behaviour is still present in the 19.12 release candidate, built from git
on 2019-12-02

*.mlt files can not be sped up or slowed down.

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

[Spectacle] [Bug 414739] New: Spectacle is killed when the notification for the last capture goes away

2019-12-01 Thread Frederick Zhang

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

Bug ID: 414739
   Summary: Spectacle is killed when the notification for the last
capture goes away
   Product: Spectacle
   Version: 19.08.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: frederick...@tsundere.moe
CC: k...@david-redondo.de
  Target Milestone: ---

SUMMARY
If Spectacle is launched before the notification for the last capture
disappears, it will be killed when the notification goes away.

STEPS TO REPRODUCE
1. Launch Spectacle
2. Click Save, Spectacle closes and a notification pops up
3. Launch Spectacle again
4. Wait until the notification disappears

OBSERVED RESULT
Spectacle is killed when the notification disappears, which may interrupt
user's current capture.

EXPECTED RESULT
Notifications for previous captures do not cause current Spectacle to be
killed.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.17.3
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2
Kernel Version: 5.3.13-arch1-1
OS Type: 64-bit

ADDITIONAL INFORMATION
I'm using Xorg.

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

[lokalize] [Bug 299857] Lokalize does nt take in account the skip spellcheck for uppercase words, option

2019-12-01 Thread Dimitrios Glentadakis

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

--- Comment #2 from Dimitrios Glentadakis  ---
I cannot check the settings of spellchek as i don't use KDE any more. I have
switched to LXQt.

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

[kio-extras] [Bug 396630] Unable to rename files via kio_smb

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #8 from Nate Graham  ---
Weird, works fine for me.

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

[kwin] [Bug 412573] Gap between window decorations and content with fractional scaling enabled

2019-12-01 Thread Jan Grulich

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

--- Comment #5 from Jan Grulich  ---
Created attachment 124253
  --> https://bugs.kde.org/attachment.cgi?id=124253=edit
Screenshot of the issue

Same problem here. Attaching screenshot where a similar issue can be seen even
on the left side.

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

[kate] [Bug 414738] New: Wrong syntax highlight when open python file

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

Bug ID: 414738
   Summary: Wrong syntax highlight when open python file
   Product: kate
   Version: 19.08.3
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: syntax
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: choco.s...@protonmail.com
  Target Milestone: ---

SUMMARY
Wrong syntax highlight when open python file, python file(.py) detect as REXX


STEPS TO REPRODUCE
1. open python script file
2. check tool-> highlighting -> script
3. kate datect as REXX script not python script

OBSERVED RESULT
REXX script

EXPECTED RESULT
python script

Operating System: Manjaro Linux 
KDE Plasma Version: 5.17.3
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2
Kernel Version: 5.3.12-1-MANJARO
OS Type: 64-bit
Processors: 2 × Intel® Pentium® CPU B980 @ 2.40GHz
Memory: 3,7 GiB of RAM

ADDITIONAL INFORMATION
Kate
Version 19.08.3

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

[krita] [Bug 413749] just a simple crash after painting for more than 30 minutes

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

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.

[kdiamond] [Bug 413654] Timer begins increasing in 1440 minute increments

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

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.

[okular] [Bug 414179] Okular crashes when a password protected PDF is opened.

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

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

[systemsettings] [Bug 351791] After switching to reverse scrolling in input settings when I switch it back it still scrolls in reverse

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

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

[digikam] [Bug 414737] DigiKam becomes unresponsive when clicking on NFS-mounted photos

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #1 from caulier.gil...@gmail.com ---
Which kind of database type do you use ? Mysql or sqlte ?

Where are stored your database file ? On the NFS mount path, in local, or in a
remote server ?

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

[digikam] [Bug 414737] New: DigiKam becomes unresponsive when clicking on NFS-mounted photos

2019-12-01 Thread Cengiz Gunay

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

Bug ID: 414737
   Summary: DigiKam becomes unresponsive when clicking on
NFS-mounted photos
   Product: digikam
   Version: 6.1.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: cengi...@users.sf.net
  Target Milestone: ---

Application: digikam (6.1.0)

Qt Version: 5.13.0
Frameworks Version: 5.60.0
Operating System: Linux 4.19.60-1-MANJARO x86_64
Distribution: "Manjaro Linux"

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

I had albums scanned from an NFS drive and clicking on them just freezes
DigiKam and all of its operations. 

I'm on Manjaro. I can provide more details/test if there is any need.

The crash can be reproduced every time.

-- Backtrace:
Application: digiKam (digikam), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4d32b31040 (LWP 14404))]

Thread 13 (Thread 0x7f4c837fe700 (LWP 14462)):
#0  0x7f4d4b30677c in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f4d423cb996 in  () at /usr/lib/libQt5WebEngineCore.so.5
#2  0x7f4d423cc983 in  () at /usr/lib/libQt5WebEngineCore.so.5
#3  0x7f4d423ccb01 in  () at /usr/lib/libQt5WebEngineCore.so.5
#4  0x7f4d423d5811 in  () at /usr/lib/libQt5WebEngineCore.so.5
#5  0x7f4d423d6e12 in  () at /usr/lib/libQt5WebEngineCore.so.5
#6  0x7f4d423d7564 in  () at /usr/lib/libQt5WebEngineCore.so.5
#7  0x7f4d423cdb35 in  () at /usr/lib/libQt5WebEngineCore.so.5
#8  0x7f4d4b30057f in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f4d4f4890e3 in clone () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7f4cb5ffb700 (LWP 14461)):
#0  0x7f4d4b30677c in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f4d423cb996 in  () at /usr/lib/libQt5WebEngineCore.so.5
#2  0x7f4d423cc983 in  () at /usr/lib/libQt5WebEngineCore.so.5
#3  0x7f4d423ccb01 in  () at /usr/lib/libQt5WebEngineCore.so.5
#4  0x7f4d423d5811 in  () at /usr/lib/libQt5WebEngineCore.so.5
#5  0x7f4d423d7171 in  () at /usr/lib/libQt5WebEngineCore.so.5
#6  0x7f4d423d7564 in  () at /usr/lib/libQt5WebEngineCore.so.5
#7  0x7f4d423cdb35 in  () at /usr/lib/libQt5WebEngineCore.so.5
#8  0x7f4d4b30057f in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f4d4f4890e3 in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7f4cb4ff9700 (LWP 14460)):
#0  0x7f4d4b306415 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f4d423cb89c in  () at /usr/lib/libQt5WebEngineCore.so.5
#2  0x7f4d423cc990 in  () at /usr/lib/libQt5WebEngineCore.so.5
#3  0x7f4d423ccabf in  () at /usr/lib/libQt5WebEngineCore.so.5
#4  0x7f4d423d57e6 in  () at /usr/lib/libQt5WebEngineCore.so.5
#5  0x7f4d423d7171 in  () at /usr/lib/libQt5WebEngineCore.so.5
#6  0x7f4d423d75a4 in  () at /usr/lib/libQt5WebEngineCore.so.5
#7  0x7f4d423cdb35 in  () at /usr/lib/libQt5WebEngineCore.so.5
#8  0x7f4d4b30057f in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f4d4f4890e3 in clone () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7f4cb57fa700 (LWP 14459)):
[KCrash Handler]
#6  0x7f4d4f3c7755 in raise () at /usr/lib/libc.so.6
#7  0x7f4d4f3b2851 in abort () at /usr/lib/libc.so.6
#8  0x7f4d4fa2b8b6 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f4d4fa2ace2 in qt_assert_x(char const*, char const*, char const*,
int) () at /usr/lib/libQt5Core.so.5
#10 0x7f4d4f7db579 in  () at /usr/lib/libdigikamdatabase.so.6.1.0
#11 0x7f4d4f809c6f in Digikam::CollectionManager::locationForPath(QString
const&) () at /usr/lib/libdigikamdatabase.so.6.1.0
#12 0x7f4d4f8857b1 in Digikam::ItemInfo::fromLocalFile(QString const&) ()
at /usr/lib/libdigikamdatabase.so.6.1.0
#13 0x7f4d4f84ffe2 in
Digikam::DatabaseLoadSaveFileInfoProvider::orientationHint(QString const&) ()
at /usr/lib/libdigikamdatabase.so.6.1.0
#14 0x7f4d5129dac0 in Digikam::LoadSaveThread::exifOrientation(QString
const&, Digikam::DMetadata const&, bool, bool) () at
/usr/lib/libdigikamcore.so.6.1.0
#15 0x7f4d5128c355 in
Digikam::ThumbnailCreator::createThumbnail(Digikam::ThumbnailInfo const&, QRect
const&) const () at /usr/lib/libdigikamcore.so.6.1.0
#16 0x7f4d5128e9dc in
Digikam::ThumbnailCreator::load(Digikam::ThumbnailIdentifier const&, QRect
const&, bool) const () at /usr/lib/libdigikamcore.so.6.1.0
#17 0x7f4d5128f305 in
Digikam::ThumbnailCreator::load(Digikam::ThumbnailIdentifier const&) const ()
at /usr/lib/libdigikamcore.so.6.1.0
#18 0x7f4d5129c537 in Digikam::ThumbnailLoadingTask::execute() () at
/usr/lib/libdigikamcore.so.6.1.0
#19 0x7f4d5129e519 in Digikam::LoadSaveThread::run() () at

[kdenlive] [Bug 414736] New: Needs creation date in Clip Properties.

2019-12-01 Thread Anton

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

Bug ID: 414736
   Summary: Needs creation date in Clip Properties.
   Product: kdenlive
   Version: 19.08.3
  Platform: Flatpak
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: agvozdez...@yandex.ru
  Target Milestone: ---

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

SUMMARY

Please add clip creation date in Clip Properties. See the picture.
STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


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

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 414712] Visually highlight (root) password prompts and prevent other windows to steal the focus

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |INTENTIONAL
 Status|REPORTED|RESOLVED

--- Comment #1 from Nate Graham  ---
This is actually one of the most complained-about features of GNOME. :) Check
out the more than one dozen duplicates on
https://bugzilla.gnome.org/show_bug.cgi?id=688434

Making the password dialog system-modal does indeed solve the problem of focus
stealing, but it also prevents you from doing anything else when it's active.
For example, if you store passwords in a password manager/generator or an
encrypted text file, you can no longer access those to copy your password for
the purpose of pasting into the password dialog.

KWin has explicit focus stealing support. I think it would make more sense to
report the bug there in a targeted manner ("x window stole focus while I was
typing my password in a dialog originated by Z app") rather than using the
sledgehammer approach that GNOME uses.

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

[krita] [Bug 414735] New: Author Data not Saved when Saving/Exporting to PNG/JPG

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

Bug ID: 414735
Summary: Author Data not Saved when Saving/Exporting to PNG/JPG
Product: krita
Version: 4.2.7.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: File formats
Assignee: krita-bugs-n...@kde.org
Reporter: tus...@vista.aero
Target Milestone: ---

SUMMARY
Taken from
https://www.reddit.com/r/krita/comments/e3lkds/cant_get_author_information_to_save_to_file/

Author data cannot be saved/loaded properly when exporting or saving to PNG or
JPG files.

STEPS TO REPRODUCE
1. Edit author data in Configure Krita
2. Settings -> Active Author Profile -> select some profile other than
anonymous.
3. Create a Krita document. Save it as a kra file.
4. File -> Document Information -> Author.
5. Export it to a png file. Check "Save metadata" and "Sign with author profile
data."
6. Open the png file.
7. File -> Document Information -> Author.
8. Modify the png file and save it in-place. Check "Save metadata" and "Sign
with author profile data."
9. File -> Document Information -> Author.
10. Close the png file, and reopen it.
11. File -> Document Information -> Author.
12. Repeat 5-11 with jpg.

OBSERVED RESULT
Only in steps 4, 9 can I saw the author information.

EXPECTED RESULT
We should be able to see author information in 7 and 11 as well.

SOFTWARE/OS VERSIONS
Windows: 10
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version: 5.12.3

ADDITIONAL INFORMATION
For the JPG case, I am able to see the author filled in in the properties
dialog of Windows Explorer, so it could potentially be a loading issue, rather
than a saving one.

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

[systemsettings] [Bug 405405] System settings crashes on close after I try to install an invalid file

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

Nate Graham  changed:

   What|Removed |Added

Summary|System settings crashes on  |System settings crashes on
   |close after I try to|close after I try to
   |install a local gtk2 theme  |install an invalid file

--- Comment #10 from Nate Graham  ---
Can reproduce. However this content is actually not a GTK theme at all, but
rather a KDE color scheme. Trying to install it is what makes the KCM crash.
Still, it probably shouldn't crash. :)

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

[systemsettings] [Bug 408172] Crash when closing system settings

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #2 from Nate Graham  ---


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

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

[systemsettings] [Bug 405405] System settings crashes on close after I try to install an invalid file

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

Nate Graham  changed:

   What|Removed |Added

 CC||burac...@gmail.com

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

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

[systemsettings] [Bug 405405] System settings crashes on close after I try to install a local gtk2 theme

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

Nate Graham  changed:

   What|Removed |Added

 CC||rahil.rules@gmail.com

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

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

[systemsettings] [Bug 409683] SystemSettings crash on installing local gtk theme tar.gz

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #2 from Nate Graham  ---


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

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

[systemsettings] [Bug 369151] kde-gtk-config erroneously insert foundry name into font name for GTK 3 config

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

Nate Graham  changed:

   What|Removed |Added

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

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

[systemsettings] [Bug 369151] kde-gtk-config erroneously insert foundry name into font name for GTK 3 config

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

Nate Graham  changed:

   What|Removed |Added

  Latest Commit||https://cgit.kde.org/kde-gt
   ||k-config.git/commit/?id=947
   ||32eb8d6ee54573a4476e7b03680
   ||8ac9907ba0
   Version Fixed In||5.18.0
 CC||n...@kde.org

--- Comment #1 from Nate Graham  ---
Fixed by
https://cgit.kde.org/kde-gtk-config.git/commit/?id=94732eb8d6ee54573a4476e7b036808ac9907ba0
in Plasma 5.18.

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

[systemsettings] [Bug 411762] "Jump to mouse cursor position" does not work with Chromium and Chromium-based browsers

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #3 from Nate Graham  ---
Yeah, this not a bug in the KCM. Please report it to the Chromium folks and ask
them to respect the GTK setting for their custom scrollview implementation.

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

[systemsettings] [Bug 343561] kde-gtk-config fails to set fonts properly

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://cgit.kde.org/kde-gt
   ||k-config.git/commit/?id=947
   ||32eb8d6ee54573a4476e7b03680
   ||8ac9907ba0
 Status|REPORTED|RESOLVED
   Version Fixed In||5.18.0

--- Comment #6 from Nate Graham  ---
Fixed by
https://cgit.kde.org/kde-gtk-config.git/commit/?id=94732eb8d6ee54573a4476e7b036808ac9907ba0
in Plasma 5.18!

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

[systemsettings] [Bug 365020] Separate icon themes for GTK+2 and GTK+3 applications

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #3 from Nate Graham  ---
I don't think this is something we'll be doing. Our general direction is
improving and increasing the integration between the themes, not pushing them
apart. Just use a dark or light theme for all GTK apps; I don't think it makes
sense to use different themes for the different versions of GTK.

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

[systemsettings] [Bug 401123] Icon theme preview shows pixelated icons with fractional display scaling

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

Nate Graham  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kde
   ||-gtk-config/e3274dba5fb2739
   ||b226d753df532b78ab123cf81
 Status|REPORTED|RESOLVED
   Version Fixed In||5.18.0
 Resolution|--- |FIXED

--- Comment #1 from Nate Graham  ---
Git commit e3274dba5fb2739b226d753df532b78ab123cf81 by Nate Graham, on behalf
of Mikhail Zolotukhin.
Committed on 02/12/2019 at 03:07.
Pushed by ngraham into branch 'master'.

Remove unneeded options in GTK KCM

Summary:
Since font, icons, cursor theme, toolbar style, icons in menus and buttons
settings are now in sync with corresponding plasma settings, they shouldn't be
in GTK KCM anymore.

Depends on D24743
Related: bug 406740, bug 401008

FIXED-IN: 5.18.0

Test Plan:
Check if nothing breaks in GTK KCM functionality, that is left.

{F7617327}

{F7693105}

Reviewers: #vdg, #plasma, ngraham, nicolasfella

Reviewed By: #vdg, ngraham, nicolasfella

Subscribers: apol, ngraham, broulik, filipf, GB_2, plasma-devel

Tags: #plasma, #vdg

Maniphest Tasks: T10611

Differential Revision: https://phabricator.kde.org/D24744

M  +0-3CMakeLists.txt
M  +0-14   src/abstractappearance.cpp
M  +0-14   src/abstractappearance.h
M  +0-23   src/appearancegtk2.cpp
M  +0-33   src/appearancegtk3.cpp
M  +0-7src/appearencegtk.cpp
D  +0-87   src/cursorthemesmodel.cpp
D  +0-41   src/cursorthemesmodel.h
M  +0-79   src/dialog_installer.cpp
M  +0-14   src/dialog_installer.h
M  +0-40   src/dialog_uninstaller.cpp
M  +0-2src/dialog_uninstaller.h
D  +0-60   src/fontshelpers.cpp
D  +0-30   src/fontshelpers.h
M  +2-152  src/gtkconfigkcmodule.cpp
M  +0-8src/gtkconfigkcmodule.h
D  +0-131  src/iconthemesmodel.cpp
D  +0-45   src/iconthemesmodel.h
M  +0-12   src/installer.cpp
M  +0-7src/installer.h
M  +0-3src/thread.cpp
M  +114  -260  src/ui/dialog_installer.ui
M  +0-53   src/ui/dialog_uninstaller.ui
M  +121  -419  src/ui/gui.ui
M  +0-14   tests/configsavetest.cpp

https://commits.kde.org/kde-gtk-config/e3274dba5fb2739b226d753df532b78ab123cf81

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

[systemsettings] [Bug 401008] Tab title "Add GTK Theme" truncated

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

Nate Graham  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kde
   ||-gtk-config/e3274dba5fb2739
   ||b226d753df532b78ab123cf81
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
   Version Fixed In||5.18.0

--- Comment #4 from Nate Graham  ---
Git commit e3274dba5fb2739b226d753df532b78ab123cf81 by Nate Graham, on behalf
of Mikhail Zolotukhin.
Committed on 02/12/2019 at 03:07.
Pushed by ngraham into branch 'master'.

Remove unneeded options in GTK KCM

Summary:
Since font, icons, cursor theme, toolbar style, icons in menus and buttons
settings are now in sync with corresponding plasma settings, they shouldn't be
in GTK KCM anymore.

Depends on D24743
Related: bug 406740, bug 401123

FIXED-IN: 5.18.0

Test Plan:
Check if nothing breaks in GTK KCM functionality, that is left.

{F7617327}

{F7693105}

Reviewers: #vdg, #plasma, ngraham, nicolasfella

Reviewed By: #vdg, ngraham, nicolasfella

Subscribers: apol, ngraham, broulik, filipf, GB_2, plasma-devel

Tags: #plasma, #vdg

Maniphest Tasks: T10611

Differential Revision: https://phabricator.kde.org/D24744

M  +0-3CMakeLists.txt
M  +0-14   src/abstractappearance.cpp
M  +0-14   src/abstractappearance.h
M  +0-23   src/appearancegtk2.cpp
M  +0-33   src/appearancegtk3.cpp
M  +0-7src/appearencegtk.cpp
D  +0-87   src/cursorthemesmodel.cpp
D  +0-41   src/cursorthemesmodel.h
M  +0-79   src/dialog_installer.cpp
M  +0-14   src/dialog_installer.h
M  +0-40   src/dialog_uninstaller.cpp
M  +0-2src/dialog_uninstaller.h
D  +0-60   src/fontshelpers.cpp
D  +0-30   src/fontshelpers.h
M  +2-152  src/gtkconfigkcmodule.cpp
M  +0-8src/gtkconfigkcmodule.h
D  +0-131  src/iconthemesmodel.cpp
D  +0-45   src/iconthemesmodel.h
M  +0-12   src/installer.cpp
M  +0-7src/installer.h
M  +0-3src/thread.cpp
M  +114  -260  src/ui/dialog_installer.ui
M  +0-53   src/ui/dialog_uninstaller.ui
M  +121  -419  src/ui/gui.ui
M  +0-14   tests/configsavetest.cpp

https://commits.kde.org/kde-gtk-config/e3274dba5fb2739b226d753df532b78ab123cf81

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

[systemsettings] [Bug 406740] Content is too wide and requires horizontal scrolling

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/kde
   ||-gtk-config/e3274dba5fb2739
   ||b226d753df532b78ab123cf81
   Version Fixed In||5.18.0

--- Comment #2 from Nate Graham  ---
Git commit e3274dba5fb2739b226d753df532b78ab123cf81 by Nate Graham, on behalf
of Mikhail Zolotukhin.
Committed on 02/12/2019 at 03:07.
Pushed by ngraham into branch 'master'.

Remove unneeded options in GTK KCM

Summary:
Since font, icons, cursor theme, toolbar style, icons in menus and buttons
settings are now in sync with corresponding plasma settings, they shouldn't be
in GTK KCM anymore.

Depends on D24743
Related: bug 401008, bug 401123

FIXED-IN: 5.18.0

Test Plan:
Check if nothing breaks in GTK KCM functionality, that is left.

{F7617327}

{F7693105}

Reviewers: #vdg, #plasma, ngraham, nicolasfella

Reviewed By: #vdg, ngraham, nicolasfella

Subscribers: apol, ngraham, broulik, filipf, GB_2, plasma-devel

Tags: #plasma, #vdg

Maniphest Tasks: T10611

Differential Revision: https://phabricator.kde.org/D24744

M  +0-3CMakeLists.txt
M  +0-14   src/abstractappearance.cpp
M  +0-14   src/abstractappearance.h
M  +0-23   src/appearancegtk2.cpp
M  +0-33   src/appearancegtk3.cpp
M  +0-7src/appearencegtk.cpp
D  +0-87   src/cursorthemesmodel.cpp
D  +0-41   src/cursorthemesmodel.h
M  +0-79   src/dialog_installer.cpp
M  +0-14   src/dialog_installer.h
M  +0-40   src/dialog_uninstaller.cpp
M  +0-2src/dialog_uninstaller.h
D  +0-60   src/fontshelpers.cpp
D  +0-30   src/fontshelpers.h
M  +2-152  src/gtkconfigkcmodule.cpp
M  +0-8src/gtkconfigkcmodule.h
D  +0-131  src/iconthemesmodel.cpp
D  +0-45   src/iconthemesmodel.h
M  +0-12   src/installer.cpp
M  +0-7src/installer.h
M  +0-3src/thread.cpp
M  +114  -260  src/ui/dialog_installer.ui
M  +0-53   src/ui/dialog_uninstaller.ui
M  +121  -419  src/ui/gui.ui
M  +0-14   tests/configsavetest.cpp

https://commits.kde.org/kde-gtk-config/e3274dba5fb2739b226d753df532b78ab123cf81

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

[dolphin] [Bug 414729] Dead links for KDiskFree and KDE Partition Manager in Dolphin

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org
 Status|REPORTED|RESOLVED
   Version Fixed In||5.66
 Resolution|--- |FIXED
  Latest Commit||https://cgit.kde.org/knewst
   ||uff.git/commit/?id=cdafed6b
   ||395fcdd3bced8a4b0273b8d5f02
   ||80291

--- Comment #1 from Nate Graham  ---
Already fixed in the upcoming Frameworks 5.66 by
https://cgit.kde.org/knewstuff.git/commit/?id=cdafed6b395fcdd3bced8a4b0273b8d5f0280291.

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

[krita] [Bug 414734] New: Krita crashes when opening animation files

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

Bug ID: 414734
   Summary: Krita crashes when opening animation files
   Product: krita
   Version: 4.2.8
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: antha1...@gmail.com
  Target Milestone: ---

SUMMARY
Krita seems to exclusively crash when opening animation files.
This only happens with animations, any other files without animation seem to
work fine.

STEPS TO REPRODUCE
1. Open a .kra animation file 
2. Wait for it to crash 
3. Crash

SOFTWARE/OS VERSIONS
Windows 10 Version:10.0.18362 Build 18362


ADDITIONAL INFORMATION

I've attached my hardware information

Here's my crash log: https://pastebin.com/Px7hQc5f

I have 2 monitors

For some visual aid, here is a gif of the process: https://imgur.com/ntDqFTW

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

[kmail2] [Bug 413941] Crash when opening Kmail

2019-12-01 Thread Christoph Feck

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

Christoph Feck  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #3 from Christoph Feck  ---
Thanks for the update; changing status.

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

[okular] [Bug 414678] Okular does not render PDF version 1.2 or 1.3 documents correctly

2019-12-01 Thread Jim Sanderson

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

--- Comment #7 from Jim Sanderson  ---
Yuri,

That clue helped.  Something has installed a font called "Twitter Color Emoji
[1]" on my system.  I do not use Twitter.  I disabled the font and re-opened
the non-working files and they render correctly now.  I'm not sure why this
only affects PDF versions 1.2 and 1.3, though.  That's something for further
study.

Again, thanks for the help and I hope that this tiny bit of info can help
others.

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

[plasmashell] [Bug 414733] System Load Viewer, no information

2019-12-01 Thread Wyatt Childers

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

--- Comment #1 from Wyatt Childers  ---
Created attachment 124251
  --> https://bugs.kde.org/attachment.cgi?id=124251=edit
a log running the widget from the command line

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

[plasmashell] [Bug 414733] New: System Load Viewer, no information

2019-12-01 Thread Wyatt Childers

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

Bug ID: 414733
   Summary: System Load Viewer, no information
   Product: plasmashell
   Version: 5.17.3
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: System Monitor
  Assignee: notm...@gmail.com
  Reporter: dark...@nearce.com
  Target Milestone: 1.0

SUMMARY

After reinstalling KDE Neon, and putting a system load viewer widget on my
panel, it no longer shows any information for any category, CPU, memory, swap,
or cache. This is affecting the visual indicators, and additionally affecting
the tooltip. In the case of the tooltip it isn't display at all; instead I just
get "System load".

ADDITIONAL INFORMATION

I upgraded from a 1800X to 3950X processor, I'm not sure if the increased
number of cores could somehow be related?

KSysGuard is still able to view data

If I run "/usr/bin/plasmawindowed org.kde.plasma.systemloadviewer" I get an
error, which seems to be related to a missing data source:
"file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:251:
TypeError: Cannot read property 'value' of undefined"

This suggest to me, perhaps there's a packaging error, that the load viewer is
poorly recovering from? Replacing the calculations in the QML file with a value
of 0 allowed the tooltip to display, however, like the visual indicators, it
then printed no values.

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

[plasmashell] [Bug 414732] New: Some mouse lag when having multiple applications open

2019-12-01 Thread Bob S. Galbert

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

Bug ID: 414732
   Summary: Some mouse lag when having multiple applications open
   Product: plasmashell
   Version: 5.17.3
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: bobsgalb...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY

(This is my first handwritten bug report because i love KDE and im pretty sure
this applies in this place)


I have recently switched from Xfce4 when i installed Archlinux a couple days
ago and i have been noticing some mouse lag when i have some applications open.
I checked the usage via htop but the CPU and RAM resources are very fine but
yet i still get mouse lag. I have done some searching on the internet about
mouse drivers and stuff but i couldn't quite find anything helpful. I also
tried switching from Xorg to Wayland but that didn't really help too (i was
just trying to eliminate possible subjects). On Xfce i never had this issue. 

STEPS TO REPRODUCE
1. Open up a couple applications 
2. Try to move your mouse
3. observe the results

OBSERVED RESULT

Mouse lags and you have to stop moving it



EXPECTED RESULT

Mouse should move fine when switching applications or clicking stuffs.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.17.3
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2

ADDITIONAL INFORMATION

I've executed a troubleshooter script found in the discord-linux guild
(Discord)
https://i.notequity.com/xAd.txt. I have never experienced this on other desktop
environments.

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

[systemsettings] [Bug 414731] New: System Settings crashes

2019-12-01 Thread Chip

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

Bug ID: 414731
   Summary: System Settings crashes
   Product: systemsettings
   Version: 5.17.3
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: chipcatal...@outlook.com
  Target Milestone: ---

Application: systemsettings5 (5.17.3)

Qt Version: 5.13.2
Frameworks Version: 5.64.0
Operating System: Linux 4.19.86-1-lts x86_64
Distribution: Arch Linux

-- Information about the crash:
- What I was doing when the application crashed:
System Settings crashes when Im in Appearence. I click on Window decorations
and it crashes.

The crash can be reproduced sometimes.

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

Thread 15 (Thread 0x7fde62fbe700 (LWP 2711)):
#0  0x7fdebae279ef in poll () at /usr/lib/libc.so.6
#1  0x7fdeb8dfa120 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fdeb8dfa1f1 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fdebb3ccb2c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fdebb37383c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fdebb1a5305 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fdeba4ad449 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7fdebb1a6530 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fdeb9a004cf in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fdebae322d3 in clone () at /usr/lib/libc.so.6

Thread 14 (Thread 0x7fde63fff700 (LWP 2708)):
#0  0x7fdeb9a0819f in pthread_getspecific () at /usr/lib/libpthread.so.0
#1  0x7fdeb8dd9ae1 in g_thread_self () at /usr/lib/libglib-2.0.so.0
#2  0x7fdeb8df9edd in g_main_context_acquire () at
/usr/lib/libglib-2.0.so.0
#3  0x7fdeb8df9fc7 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7fdeb8dfa1f1 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7fdebb3ccb2c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7fdebb37383c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7fdebb1a5305 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7fdeba4ad449 in  () at /usr/lib/libQt5Qml.so.5
#9  0x7fdebb1a6530 in  () at /usr/lib/libQt5Core.so.5
#10 0x7fdeb9a004cf in start_thread () at /usr/lib/libpthread.so.0
#11 0x7fdebae322d3 in clone () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7fde737fe700 (LWP 2707)):
#0  0x7fdeb8daa479 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7fdeb8df0d72 in g_main_context_query () at /usr/lib/libglib-2.0.so.0
#2  0x7fdeb8dfa09d in  () at /usr/lib/libglib-2.0.so.0
#3  0x7fdeb8dfa1f1 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7fde96aa4e5e in  () at /usr/lib/gio/modules/libdconfsettings.so
#5  0x7fdeb8dd6bb1 in  () at /usr/lib/libglib-2.0.so.0
#6  0x7fdeb9a004cf in start_thread () at /usr/lib/libpthread.so.0
#7  0x7fdebae322d3 in clone () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7fde725b6700 (LWP 2468)):
#0  0x7fdebae3f557 in clock_gettime () at /usr/lib/libc.so.6
#1  0x7fdebb3cc412 in  () at /usr/lib/libQt5Core.so.5
#2  0x7fdebb3cacfa in QTimerInfoList::updateCurrentTime() () at
/usr/lib/libQt5Core.so.5
#3  0x7fdebb3cb2c6 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/libQt5Core.so.5
#4  0x7fdebb3cc86f in  () at /usr/lib/libQt5Core.so.5
#5  0x7fdeb8df9a00 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#6  0x7fdeb8dfa046 in  () at /usr/lib/libglib-2.0.so.0
#7  0x7fdeb8dfa1f1 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#8  0x7fdebb3ccb2c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#9  0x7fdebb37383c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#10 0x7fdebb1a5305 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#11 0x7fdebb1a6530 in  () at /usr/lib/libQt5Core.so.5
#12 0x7fdeb9a004cf in start_thread () at /usr/lib/libpthread.so.0
#13 0x7fdebae322d3 in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7fde9522d700 (LWP 2466)):
#0  0x7fdeb8df7d5d in  () at /usr/lib/libglib-2.0.so.0
#1  0x7fdeb8df867c in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fdeb8df87df in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7fdeb8dfa0c8 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7fdeb8dfa1f1 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7fdebb3ccb2c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7fdebb37383c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7fdebb1a5305

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

2019-12-01 Thread Allen Winter

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

--- Comment #2 from Allen Winter  ---
maybe you have a timezone Korganizer doesn't like?
what is your system timezone?

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

[kdenlive] [Bug 414636] MP4 different from kdenlive

2019-12-01 Thread farid

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

farid  changed:

   What|Removed |Added

 CC||snd.no...@gmail.com

--- Comment #1 from farid  ---
Hi, you started editing with which version? Can you get the AppImage of it and
test if it works properly? Hope someone can give a better answer soon.

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

[plasmashell] [Bug 414730] New: Weather Report widget crashes

2019-12-01 Thread Bob S. Galbert

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

Bug ID: 414730
   Summary: Weather Report widget crashes
   Product: plasmashell
   Version: 5.17.3
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: bobsgalb...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.17.3)
 (Compiled from sources)
Qt Version: 5.13.2
Frameworks Version: 5.64.0
Operating System: Linux 5.3.13-arch1-1 x86_64
Distribution: Arch Linux

-- Information about the crash:
- What I was doing when the application crashed:
I was searching the weather stations for the closest one around me

- Unusual behavior I noticed:

It was taking forever

- Custom settings of the application:

Only thing i set was the update setting

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

Thread 17 (Thread 0x7f24f64fa700 (LWP 4955)):
#0  0x7f256039bc45 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f2560eab610 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt5Core.so.5
#2  0x7f2560eab702 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#3  0x7f2562b34e3d in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f2562b350ee in  () at /usr/lib/libQt5Quick.so.5
#5  0x7f2560ea5530 in  () at /usr/lib/libQt5Core.so.5
#6  0x7f25603954cf in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f2560b2f2d3 in clone () at /usr/lib/libc.so.6

Thread 16 (Thread 0x7f24f770b700 (LWP 4954)):
#0  0x7f256039bc45 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f2560eab610 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt5Core.so.5
#2  0x7f2560eab702 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#3  0x7f2562b34e3d in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f2562b350ee in  () at /usr/lib/libQt5Quick.so.5
#5  0x7f2560ea5530 in  () at /usr/lib/libQt5Core.so.5
#6  0x7f25603954cf in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f2560b2f2d3 in clone () at /usr/lib/libc.so.6

Thread 15 (Thread 0x7f24f58f9700 (LWP 4953)):
#0  0x7f2560b2042c in read () at /usr/lib/libc.so.6
#1  0x7f255f3ab9f0 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f255f3f99e1 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7f255f3fb0c8 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7f255f3fb1f1 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7f25610cbb2c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7f256107283c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7f2560ea4305 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7f25627c9449 in  () at /usr/lib/libQt5Qml.so.5
#9  0x7f2560ea5530 in  () at /usr/lib/libQt5Core.so.5
#10 0x7f25603954cf in start_thread () at /usr/lib/libpthread.so.0
#11 0x7f2560b2f2d3 in clone () at /usr/lib/libc.so.6

Thread 14 (Thread 0x7f252ce23700 (LWP 1590)):
#0  0x7f256039bc45 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f2560eab610 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt5Core.so.5
#2  0x7f2560eab702 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#3  0x7f2562b34e3d in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f2562b350ee in  () at /usr/lib/libQt5Quick.so.5
#5  0x7f2560ea5530 in  () at /usr/lib/libQt5Core.so.5
#6  0x7f25603954cf in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f2560b2f2d3 in clone () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7f252ee34700 (LWP 1161)):
#0  0x7f256039bc45 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f2560eab610 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt5Core.so.5
#2  0x7f2560eab702 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#3  0x7f2562b34e3d in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f2562b350ee in  () at /usr/lib/libQt5Quick.so.5
#5  0x7f2560ea5530 in  () at /usr/lib/libQt5Core.so.5
#6  0x7f25603954cf in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f2560b2f2d3 in clone () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7f252e5bd700 (LWP 1154)):
#0  0x7f25610cb89b in  () at /usr/lib/libQt5Core.so.5
#1  0x7f255f3faa00 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7f255f3fb046 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f255f3fb1f1 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f25610cbb2c in

[cantor] [Bug 414541] cantor git master and maxima 5.43 crash

2019-12-01 Thread nijso

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

--- Comment #8 from nijso  ---
(In reply to Alexander Semke from comment #7)
> To unblock you, instead of using a latex entry you can work with a markdown
> entry and use the $...$ environment to set mathematical expressions. For
> this we already work with pdflatex and PDF to generate images.

Thanks! I see the rendered equation between $...$, but if I just type e.g.
$\alpha=1$, the rendered equation is displayed in a normal size, but with a lot
of whitespace surrounding the equation on all sides. Effectively, the result
fills an entire page. Actually, if I open the pdf-file it shows an entire page
with the equation somehwere in the middle. It looks like cantor does not scale
the equation to something that fits on a single line. Is this connected? Do you
see the same behavior?

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

[krita] [Bug 414696] Converting a filter mask created with selection into a paint layer doesn't work properly

2019-12-01 Thread Ahab Greybeard

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

--- Comment #3 from Ahab Greybeard  ---
Extra Observation:

If you do a Layer Export of one of those paint layers as a .png file and then
Import it back in, the resulting paint layer does not cause any of the problems
that have been seen so far.

If you then convert it to a Filter mask, it has black instead of transparency
and will then convert back to a paint layer with all black surround as
expected.

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

[dolphin] [Bug 414729] Dead links for KDiskFree and KDE Partition Manager in Dolphin

2019-12-01 Thread Davi

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

Davi  changed:

   What|Removed |Added

 CC||davi.si...@live.com

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

[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.

2019-12-01 Thread Nick Stefanov

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

--- Comment #72 from Nick Stefanov  ---
It would be great, thank you :)

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

[dolphin] [Bug 414729] New: Dead links for KDiskFree and KDE Partition Manager in Dolphin

2019-12-01 Thread Davi

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

Bug ID: 414729
   Summary: Dead links for KDiskFree and KDE Partition Manager in
Dolphin
   Product: dolphin
   Version: 18.04.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: davi.si...@live.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Created attachment 124250
  --> https://bugs.kde.org/attachment.cgi?id=124250=edit
displays the area mentioned in the bug description

Dead links for KDiskFree and KDE Partition Manager in Dolphin

Upon using the Plasma desktop on KDE Neon 5.17.3, the links for KDiskFree and
KDE Partition Manager which show up after clicking Dolphin's bottom right area
(the one which displays free disk space) are outdated.

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

[krita] [Bug 414726] Select tool deselects old selected area (or doesn't select another) and disables drawing on canvas

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

4lph4dr4g0nl...@gmail.com changed:

   What|Removed |Added

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

--- Comment #2 from 4lph4dr4g0nl...@gmail.com ---
(In reply to Tymond from comment #1)
> Can you please check what mode you have selected in the Tool Options and
> whether you know what is the correct behaviour of that mode? (Assuming
> you're not using any modifier or shortcut to change the behaviour) The
> Selection modes list is here:
> https://docs.krita.org/en/user_manual/selections.html#editing-selections
> 
> I believe you might be looking for Add mode instead of the default Replace.

Huh. That fixed it. Somehow the settings got changed from default. Maybe I hit
a shortcut by mistake without realizing.
Thanks for the help ^^; sorry about that

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

[dolphin] [Bug 414492] Dolphin doesn't build against Qt 5.14

2019-12-01 Thread Laurent Montel

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

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #8 from Laurent Montel  ---
I confirm with last qt5.14 that there is a compile error.
So patch seems ok

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

[kdeconnect] [Bug 405847] SFTP transfer corrupts all files

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

dutchgu...@hotmail.com changed:

   What|Removed |Added

 CC||dutchgu...@hotmail.com

--- Comment #43 from dutchgu...@hotmail.com ---
Same issue here. It works with 1.11, but the moment i switch to 1.12 it breaks.
Using 1.3.5 on openSUSE linux leap 15.1.

Not sure whether it is related but since 1.12 you need to define the storage
locations manually where before it was done automatically with pre-defined
names. 

Showing of the directory content in 1.11 and before is also much faster than
from 1.12 onwards. 

Sending of files from phone to linux works fine even in the higher versions. 

Really would like the other way around working again as that makes it easier to
copy large amounts of files from the phone to my main system through dolphin.

I just tried 1.13.5 but still issue. Switching back to 1.11 and it works fine.

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

[kde] [Bug 414728] New: Systemsettings module crashed when deleting empty entries

2019-12-01 Thread Alex

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

Bug ID: 414728
   Summary: Systemsettings module crashed when deleting empty
entries
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: alex1701c@gmx.net
  Target Milestone: ---

Application: kcmshell5 (5.16.5)

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

-- Information about the crash:
- What I was doing when the application crashed:
A couple of months ago I deletes some of the existing web shortcuts because I
will never use them.
Scince then there are a lot of empty entries.  If I delete them or any other
entry the app crashes when I click Ok/Apply.

- Custom settings of the application:
Some of the default entries have been deleted and shortcuts for existing
entries have been added.

The crash can be reproduced every time.

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

Thread 4 (Thread 0x7f8539096700 (LWP 4109)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x5564268982c8) at ../sysdeps/unix/sysv/linux/futex-internal.h:80
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x556426898278,
cond=0x5564268982a0) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x5564268982a0, mutex=0x556426898278) at
pthread_cond_wait.c:638
#3  0x7f853975d97b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#4  0x7f853975d59b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#5  0x7f8545107669 in start_thread (arg=) at
pthread_create.c:479
#6  0x7f85477de323 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f853be44700 (LWP 4108)):
#0  __GI___libc_read (nbytes=16, buf=0x7f853be43b20, fd=7) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=7, buf=0x7f853be43b20, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2  0x7f854462463f in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f85445dc58e in g_main_context_check () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f85445dc9e2 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f85445dcb73 in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f85462986c3 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f854623f63b in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f8546078a75 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f854723eefa in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#10 0x7f8546079cc2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f8545107669 in start_thread (arg=) at
pthread_create.c:479
#12 0x7f85477de323 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f8540f8c700 (LWP 4107)):
#0  0x7f85477d1c2f in __GI___poll (fds=0x7f8540f8bc68, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f8544de8917 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f8544dea53a in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f854173d288 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f8546079cc2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f8545107669 in start_thread (arg=) at
pthread_create.c:479
#6  0x7f85477de323 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f8541e5b840 (LWP 4106)):
[KCrash Handler]
#6  0x0041 in ?? ()
#7  0x7f853a9ef0de in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/urifilters/kurisearchfilter.so
#8  0x7f853a9f27af in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/urifilters/kurisearchfilter.so
#9  0x7f8541862b1e in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_webshortcuts.so
#10 0x7f8541862b6d in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_webshortcuts.so
#11 0x7f854768a328 in KCModuleProxy::deleteClient() () from
/usr/lib/x86_64-linux-gnu/libKF5KCMUtils.so.5
#12 0x7f854768a3e1 in KCModuleProxy::~KCModuleProxy() () from
/usr/lib/x86_64-linux-gnu/libKF5KCMUtils.so.5
#13 0x7f854768a57d in KCModuleProxy::~KCModuleProxy() () from
/usr/lib/x86_64-linux-gnu/libKF5KCMUtils.so.5
#14 0x7f854626a17e in QObjectPrivate::deleteChildren() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7f8546c90919 in QWidget::~QWidget() () from

[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards

2019-12-01 Thread Rob

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

--- Comment #170 from Rob  ---
Actually its "astropy" Maybe spell check changed it.  But Did you try running
the commands Ekos put in the log into the terminal to see what happens?

Don't copy and paste it from here, copy and paste it from KStars into the
terminal

export
PATH=/Applications/KStars.app/Contents/MacOS/netpbm/bin:/usr/local/opt/python/libexec/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin

/Applications/KStars.app/Contents/MacOS/astrometry/bin/solve-field -O
--no-plots --no-verify --resort --downsample 2 -3 292.875 -4 28.0033 -5 30
--config /Applications/KStars.app/Contents/MacOS/astrometry/bin/astrometry.cfg
-W /private/var/folders/vd/vwnkltm92sx93mrg14plg82rgn/T/solution.wcs
/private/var/folders/vd/vwnkltm92sx93mrg14plg82rgn/T/fitsdfuyiD.fits

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

[krita] [Bug 414696] Converting a filter mask created with selection into a paint layer doesn't work properly

2019-12-01 Thread Ahab Greybeard

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

Ahab Greybeard  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

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

[krita] [Bug 414696] Converting a filter mask created with selection into a paint layer doesn't work properly

2019-12-01 Thread Ahab Greybeard

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

Ahab Greybeard  changed:

   What|Removed |Added

 CC||ahab.greybe...@hotmail.co.u
   ||k

--- Comment #2 from Ahab Greybeard  ---
Created attachment 124249
  --> https://bugs.kde.org/attachment.cgi?id=124249=edit
Filter Masks to Paint Layers have rendering problems

I can Confirm this for the 4.2.8 appimage.

Using a selection to limit the extent of the filter mask gives what seems to be
transparency in the mask, outside the selection. It should all be black outside
the selection, I'd have thought.

Note: As a filter mask, it works fine.

When the mask is converted to a paint layer, that 'transparency' does not
render well and causes all kinds of effects like making things transparent
underneath it.
You can get the background back by turning off the paint layers that were made
this way and then toggling the background on and off.

I attach a .kra file which has some paint layers that were obviously made in
this way. You can turn them on and off to see the consequences.

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

[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards

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

--- Comment #169 from Stanley Fertig  ---
Er...that's "satrapy" not "satrapy"--so much for dyslexia!

(In reply to Stanley Fertig from comment #167)
> Created attachment 124246 [details]
> attachment-2807-0.html
> 
> Hi Rob,
> 
> In answer to the python3 question below, when I click on the “Setup” button
> under Astrometry.net  panel in Ekos, I get the
> following message:  “Home-brew, python and satrapy are already installed”
> 
> Thanks,
> stan
> 
> 
> --
> Stanley Fertig
> 35 Sidney Place
> Brooklyn, New York  11201
> +1 917-361-0632
> stanl...@nyc.rr.com
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> > On Dec 1, 2019, at 2:25 PM, Rob  wrote:
> > 
> > https://bugs.kde.org/show_bug.cgi?id=405437
> > 
> > --- Comment #166 from Rob  ---
> > And on this device, you have python3 all set up in homebrew?
> > 
> > -- 
> > You are receiving this mail because:
> > You are on the CC list for the bug.

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

[lokalize] [Bug 356149] Synchronization panel omits characters when line wrapping

2019-12-01 Thread Alexander Potashev

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

--- Comment #9 from Alexander Potashev  ---
Created attachment 124248
  --> https://bugs.kde.org/attachment.cgi?id=124248=edit
screenshot: it works

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

[lokalize] [Bug 356149] Synchronization panel omits characters when line wrapping

2019-12-01 Thread Alexander Potashev

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

--- Comment #8 from Alexander Potashev  ---
works as expected now with {Fedora 31 + Lokalize 19.07.70 built from Git + Qt
5.12.5 + KF 5.61.0} and {ArchLinux + Lokalize 19.11.90 + Qt 5.14.0 + KF
5.64.0}.

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

[konversation] [Bug 414727] New: Konversation crashes without any user input

2019-12-01 Thread William

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

Bug ID: 414727
   Summary: Konversation crashes without any user input
   Product: konversation
   Version: 1.7.5
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konversation-de...@kde.org
  Reporter: gtr...@gmail.com
  Target Milestone: ---

SUMMARY
I started Konversation, connected to a server, joined a couple of channels and
minimized the window. While I was using another app (firefox, the last time),
Konversation crashed.
This has happened both on Windows 10 (1909) and openSUSE Leap 15.1, both times
running the 1.7.5 version. The Windows version was downloaded from
https://binary-factory.kde.org/.

STEPS TO REPRODUCE
1. Open Konversation;
2. Connect to a server and join a channel;
3. Minimize Konversation;
4. Wait a few minutes (about 20 to 40 minutes(?) - it's not constant) until it
crashes.

OBSERVED RESULT
Konversation crashes silently. The last time (in openSUSE), I ran it from the
console to check if I got an error to display there, and it actually brought up
the KDE crash reporter; The generated report is pasted under "Additional
Information".

EXPECTED RESULT
Keep Konversation running.

SOFTWARE/OS VERSIONS
Windows: Windows 10 (1909, 64-bit)
Linux/KDE Plasma: openSUSE Leap 15.1, KDE Plasma 5.12.8
(openSUSE)
KDE Plasma Version: 5.12.8
KDE Frameworks Version: 5.55.0
Qt Version: 5.9.7
(Windows 10 - information taken from "About Konversation")
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2 (built against 5.13.2)

ADDITIONAL INFORMATION
KDE generated crash report:

Application: Konversation (konversation), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8164a58900 (LWP 2520))]

Thread 6 (Thread 0x7f8131ce6700 (LWP 2525)):
#0  0x7f815b0938ad in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f813739c83b in ?? () from /usr/lib64/dri/r600_dri.so
#2  0x7f813739c547 in ?? () from /usr/lib64/dri/r600_dri.so
#3  0x7f815b08d569 in start_thread () from /lib64/libpthread.so.0
#4  0x7f815d6099ef in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f8132628700 (LWP 2524)):
#0  0x7f815b0938ad in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f813739c83b in ?? () from /usr/lib64/dri/r600_dri.so
#2  0x7f813739c547 in ?? () from /usr/lib64/dri/r600_dri.so
#3  0x7f815b08d569 in start_thread () from /lib64/libpthread.so.0
#4  0x7f815d6099ef in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f8146be7700 (LWP 2523)):
#0  0x7f815d5ff19b in poll () from /lib64/libc.so.6
#1  0x7f81578551a9 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f81578552bc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f815e27c96b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f815e22190a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f815e03fdaa in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f815e044ced in ?? () from /usr/lib64/libQt5Core.so.5
#7  0x7f815b08d569 in start_thread () from /lib64/libpthread.so.0
#8  0x7f815d6099ef in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f8147fff700 (LWP 2522)):
#0  0x7f8157854640 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#1  0x7f81578550db in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f81578552bc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f815e27c96b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f815e22190a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f815e03fdaa in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f815e6fc9e5 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x7f815e044ced in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x7f815b08d569 in start_thread () from /lib64/libpthread.so.0
#9  0x7f815d6099ef in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f814f56c700 (LWP 2521)):
#0  0x7f815d5ff19b in poll () from /lib64/libc.so.6
#1  0x7f8159416307 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f8159417f3a in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f8152324939 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f815e044ced in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x7f815b08d569 in start_thread () from /lib64/libpthread.so.0
#6  0x7f815d6099ef in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f8164a58900 (LWP 2520)):
[KCrash Handler]
#6  0x7f815e0bf6e3 in operator==(QString const&, QString const&) () from
/usr/lib64/libQt5Core.so.5
#7  0x562f782d32d9 in ?? ()
#8  0x562f782e035c in ?? ()
#9  0x562f782e96fd in ?? ()
#10 0x562f78297b9b in ??

[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards

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

--- Comment #168 from Stanley Fertig  ---
Just checked.  Python v. 3.7.3 is running on my Air (where astrometry does not
work) whereas v. 2.7 is running on my iMac (where it does work).

-stan
--
Stanley Fertig
35 Sidney Place
Brooklyn, New York  11201
+1 917-361-0632
stanl...@nyc.rr.com











> On Dec 1, 2019, at 2:25 PM, Rob  wrote:
> 
> https://bugs.kde.org/show_bug.cgi?id=405437
> 
> --- Comment #166 from Rob  ---
> And on this device, you have python3 all set up in homebrew?
> 
> -- 
> You are receiving this mail because:
> You are on the CC list for the bug.

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

[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.

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

--- Comment #71 from Nate Graham  ---
I'll see if I can get some eyes on this.

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

[juk] [Bug 414644] Cannot reorder music tracks in the Play Queue

2019-12-01 Thread Michael

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

Michael  changed:

   What|Removed |Added

 CC||kde@callthecomputerdoctor.c
   ||om

--- Comment #1 from Michael  ---
I can verify that this bug on my version of Juk too. I hit this when I tried to
change the order of some tracks in the play queue once. I had to remove
everything from the queue and then re-add all the tracks back in manually in
the order I wanted. So being able to drag 'n drop the tracks around would've
been very welcome.

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

[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards

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

--- Comment #167 from Stanley Fertig  ---
Hi Rob,

In answer to the python3 question below, when I click on the “Setup” button
under Astrometry.net  panel in Ekos, I get the
following message:  “Home-brew, python and satrapy are already installed”

Thanks,
stan


--
Stanley Fertig
35 Sidney Place
Brooklyn, New York  11201
+1 917-361-0632
stanl...@nyc.rr.com











> On Dec 1, 2019, at 2:25 PM, Rob  wrote:
> 
> https://bugs.kde.org/show_bug.cgi?id=405437
> 
> --- Comment #166 from Rob  ---
> And on this device, you have python3 all set up in homebrew?
> 
> -- 
> You are receiving this mail because:
> You are on the CC list for the bug.

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

[kwin] [Bug 397850] kwin_x11 - triple buffer detection of compositing apparently broken with every driver; causing stuttering, lag or tearing

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org
 Resolution|UNMAINTAINED|DUPLICATE

--- Comment #5 from Nate Graham  ---


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

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

[kwin] [Bug 344433] SceneOpenGL::paint() occasionally lasts > 16ms (triple buffering enabled)

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

Nate Graham  changed:

   What|Removed |Added

 CC||tempel.jul...@gmail.com

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

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

[kate] [Bug 414628] Add support for UTF8 Emoji characters in kate

2019-12-01 Thread Martin

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

--- Comment #2 from Martin  ---
Thanks Kåre.

If I select "Noto Color Emoji" as default font, the emojis are displayed but
the normal letters are ugly.

Since NotoColorEmoji.ttf does not contain letters, where are taken the letter
characters?

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

[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards

2019-12-01 Thread Rob

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

--- Comment #166 from Rob  ---
And on this device, you have python3 all set up in homebrew?

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

[krita] [Bug 414726] Select tool deselects old selected area (or doesn't select another) and disables drawing on canvas

2019-12-01 Thread Tymond

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

Tymond  changed:

   What|Removed |Added

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

--- Comment #1 from Tymond  ---
Can you please check what mode you have selected in the Tool Options and
whether you know what is the correct behaviour of that mode? (Assuming you're
not using any modifier or shortcut to change the behaviour) The Selection modes
list is here:
https://docs.krita.org/en/user_manual/selections.html#editing-selections

I believe you might be looking for Add mode instead of the default Replace.

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

[krita] [Bug 414726] New: Select tool deselects old selected area (or doesn't select another) and disables drawing on canvas

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

Bug ID: 414726
   Summary: Select tool deselects old selected area (or doesn't
select another) and disables drawing on canvas
   Product: krita
   Version: 4.2.8
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Tools/Selection
  Assignee: krita-bugs-n...@kde.org
  Reporter: 4lph4dr4g0nl...@gmail.com
  Target Milestone: ---

SUMMARY
Selecting one area while another area is selected already seems to not select,
and if the new selection overlaps the old, the new just gets smaller. This is
while not using the shift key to select new areas at once.

STEPS TO REPRODUCE
1. Select an area, any shape
2. Select another area without deselecting first

OBSERVED RESULT
New selection overlaps into the old, deselecting the overlapped part of the
old, and causes the brushes to no longer interact with the canvas.

EXPECTED RESULT
Selecting a new section without deselecting

SOFTWARE/OS VERSIONS
Windows: 10

ADDITIONAL NOTES
The effects on the canvas can be reversed if I hit undo a few times, but I
think it's worth reporting.

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

[systemsettings] [Bug 414109] Plasma session started with a new user account shows different cursor depending on hovered area

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

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||5.18.0

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

[print-manager] [Bug 326289] plasma-desktop crashed after configuring printer applet [JobModel::updateJob]

2019-12-01 Thread Albert Astals Cid

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

--- Comment #44 from Albert Astals Cid  ---
(In reply to Meinhard Ritscher from comment #43)
> I do experience the crash and 
> 
> $> lpstat -R
>   0 printer-97user  316416 Sun Sep 15 22:00:36 2019
>   1 printer-97user  316416 Sun Sep 15 22:00:36 2019
>   2 printer-97user  316416 Sun Sep 15 22:00:36 2019
> 
> Running on openSuse Thumbleweed on the latests updates. Experience this
> crash since a few days

Right, you have 3 print jobs with id 97, which is why this is crashing.

Do you remember what you did to end up with 3 print jobs with the same id? Was
your printer off or on or it failed during printing or something?

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

[systemsettings] [Bug 414725] New: System Settings KDE Connect doesn't select device without manually clicking it

2019-12-01 Thread Nuclear Man

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

Bug ID: 414725
   Summary: System Settings KDE Connect doesn't select device
without manually clicking it
   Product: systemsettings
   Version: 5.17.3
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: nuclide...@protonmail.com
  Target Milestone: ---

Created attachment 124245
  --> https://bugs.kde.org/attachment.cgi?id=124245=edit
No device selected without manually clicking it.

SUMMARY
When I open System Settings>KDE Connect, no device is selected automatically
even though I have my phone paired to KDE.

STEPS TO REPRODUCE
1. Open System Settings
2. Select the KDE Connect section

OBSERVED RESULT
No device is selected, even though there is one present. I have to select it
myself.

EXPECTED RESULT
The device should be selected automatically.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 19.10
KDE Plasma Version: 5.17.3
KDE Frameworks Version: 5.64.0
Qt Version: 5.12.4

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

[kdenlive] [Bug 414509] Curve effect settings lost when splitting clip or copying effect

2019-12-01 Thread emohr

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

emohr  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||fritzib...@gmx.net
 Status|REPORTED|CONFIRMED
  Flags||Brainstorm+

--- Comment #1 from emohr  ---
Confirmed. After cut the curve effect, the effect on the right clip part is
reseted.

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

[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards

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

--- Comment #165 from Stanley Fertig  ---
Hi Rob,

Hope this finds you well.

I just downloaded kStars v3.3.8 and tried it out (using the simulators).
When plate-solving using Astrometry.net  online, it
works fine.  But when I try doing it offline, it immediately fails.  I’ve
copied the session comments below (although not through Terminal as last time).

I haven’t moved any of the Astrometry indexes, although I have installed
Catalina on my Air.  

BTW this problem does not occur on my iMac, same as last time.

Do you have any advice?

Many thanks again,
Stanley Fertig



2019-12-01T13:37:42 Solver failed. Try again.
2019-12-01T13:37:42 Error starting solver: Process crashed
2019-12-01T13:37:42 Reading input file 1 of 1:
"/private/var/folders/vd/vwnkltm92sx93mrg14plg82rgn/T/fitsdfuyiD.fits"...
2019-12-01T13:37:41
/Applications/KStars.app/Contents/MacOS/astrometry/bin/solve-field -O
--no-plots --no-verify --resort --downsample 2 -3 292.875 -4 28.0033 -5 30
--config /Applications/KStars.app/Contents/MacOS/astrometry/bin/astrometry.cfg
-W /private/var/folders/vd/vwnkltm92sx93mrg14plg82rgn/T/solution.wcs
/private/var/folders/vd/vwnkltm92sx93mrg14plg82rgn/T/fitsdfuyiD.fits
2019-12-01T13:37:41 Starting solver...
2019-12-01T13:37:41 export
PATH=/Applications/KStars.app/Contents/MacOS/netpbm/bin:/usr/local/opt/python/libexec/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
2019-12-01T13:37:41 Solver iteration #1
2019-12-01T13:37:41 Image received.
2019-12-01T13:37:38 Capturing image...


--
Stanley Fertig
35 Sidney Place
Brooklyn, New York  11201
+1 917-361-0632
stanl...@nyc.rr.com

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

[print-manager] [Bug 326289] plasma-desktop crashed after configuring printer applet [JobModel::updateJob]

2019-12-01 Thread Meinhard Ritscher

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

Meinhard Ritscher  changed:

   What|Removed |Added

 CC||mr203010s...@gmx.net

--- Comment #43 from Meinhard Ritscher  ---
I do experience the crash and 

$> lpstat -R
  0 printer-97user  316416 Sun Sep 15 22:00:36 2019
  1 printer-97user  316416 Sun Sep 15 22:00:36 2019
  2 printer-97user  316416 Sun Sep 15 22:00:36 2019

Running on openSuse Thumbleweed on the latests updates. Experience this crash
since a few days

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

[dolphin] [Bug 414492] Dolphin doesn't build against Qt 5.14

2019-12-01 Thread David Faure

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

David Faure  changed:

   What|Removed |Added

 CC||fa...@kde.org

--- Comment #7 from David Faure  ---
This is. interesting.

I'm using Qt 5.4 from git (54f5b89750, 2 weeks ago) and dolphin builds fine.
So I looked at how qevent.h gets included by views/draganddrophelper.cpp (easy
technique: put #error in qevent.h), and it turns out that the generated header
include/QtGui/QList says:
#include 
!!!

I have no idea why this forwarding header even exists, there's
include/QtCore/QList which includes qlist.h as it should.

Ah, that's a bug that got fixed in Qt recently.
Commit 5771b5325b85 in qtbase says

commit 5771b5325b85f71a8f8ff78ed13eaee3df2e3ba8
Author: Andy Shaw 
Date:   Tue Nov 5 22:10:24 2019 +0100

syncqt: Add a means to suspend/resume the processing of a file

Rather than tweaking the parser to cover every eventuality with corner
case lines that could cause incorrect header files to be created then
the means to suspend/resume the processing of a file is added.

This enables us to have it skip over the template line that is causing
a QList header to be created as part of the QtGui headers. This patch
includes the fix to solve this in addition.

Fixes: QTBUG-68129
Change-Id: I751646c4b20a4434347c149ae5e6dcb6e7618853
Reviewed-by: Joerg Bornemann 

So your fixes seem correct to me.
Suddenly  includes qlist.h and not qevent.h anymore...

Man, I'm not looking forward to updating my qt git and fixing compilation in
the 399 modules I build..

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

[kinfocenter] [Bug 413003] KInfoCenter eventually crashes when browsing through energy information

2019-12-01 Thread Rex Dieter

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

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@gmail.com

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

[digikam] [Bug 412067] I get a error message: "Error while opening the database".

2019-12-01 Thread Maik Qualmann

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

--- Comment #5 from Maik Qualmann  ---
You could edit the "digikamrc" manually and enter the correct hostname again.
We may need to enable the MySQL configuration dialog at the start if the
connection fails.

Maik

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

[lattedock] [Bug 414180] Items are constantly shrinking/expanding

2019-12-01 Thread Michail Vourlakos

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

Michail Vourlakos  changed:

   What|Removed |Added

  Latest Commit|https://commits.kde.org/lat |https://commits.kde.org/lat
   |te-dock/9739c43674fbf3b19b6 |te-dock/747d4870a0c82e2afe4
   |a13584a7364998a49b0d5   |1bfe5ed7ecfa61165b6e1

--- Comment #7 from Michail Vourlakos  ---
Git commit 747d4870a0c82e2afe41bfe5ed7ecfa61165b6e1 by Michail Vourlakos.
Committed on 01/12/2019 at 17:20.
Pushed by mvourlakos into branch 'master'.

introduce AutomaticItemSizer and add protector

--the automatic item sizer algorithm now is present
in its own class/responsibility area. As a new
improvement/fix the new implementation provides also
a protector/tracker that when the current prediction
to grow has already be applied two steps back in
history then the growing is not applied. This way
endless loops with growings and shrinks are blocked.
FIXED-IN:0.9.5

A  +234  -0containment/package/contents/ui/AutomaticItemSizer.qml
[License: GPL (v2+)]
M  +1-1containment/package/contents/ui/DebugWindow.qml
M  +5-5containment/package/contents/ui/VisibilityManager.qml
M  +1-1containment/package/contents/ui/editmode/Visual.qml
M  +2-2containment/package/contents/ui/layouts/LayoutsContainer.qml
M  +6-140  containment/package/contents/ui/main.qml

https://commits.kde.org/latte-dock/747d4870a0c82e2afe41bfe5ed7ecfa61165b6e1

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

[lattedock] [Bug 414180] Items are constantly shrinking/expanding

2019-12-01 Thread Michail Vourlakos

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

Michail Vourlakos  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
   Version Fixed In||0.9.5
  Latest Commit||https://commits.kde.org/lat
   ||te-dock/9739c43674fbf3b19b6
   ||a13584a7364998a49b0d5

--- Comment #6 from Michail Vourlakos  ---
Git commit 9739c43674fbf3b19b6a13584a7364998a49b0d5 by Michail Vourlakos.
Committed on 01/12/2019 at 17:17.
Pushed by mvourlakos into branch 'v0.9'.

introduce AutomaticItemSizer and add protector

--the automatic item sizer algorithm now is present
in its own class/responsibility area. As a new
improvement/fix the new implementation provides also
a protector/tracker that when the current prediction
to grow has already be applied two steps back in
history then the growing is not applied. This way
endless loops with growings and shrinks are blocked.
FIXED-IN:0.9.5

A  +234  -0containment/package/contents/ui/AutomaticItemSizer.qml
[License: GPL (v2+)]
M  +1-1containment/package/contents/ui/DebugWindow.qml
M  +5-5containment/package/contents/ui/VisibilityManager.qml
M  +1-1containment/package/contents/ui/editmode/Visual.qml
M  +2-2containment/package/contents/ui/layouts/LayoutsContainer.qml
M  +6-140  containment/package/contents/ui/main.qml

https://commits.kde.org/latte-dock/9739c43674fbf3b19b6a13584a7364998a49b0d5

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

[kmail2] [Bug 284172] Kmail does not correctly recognize some IMAP-Inbox-Folders

2019-12-01 Thread kmi

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

kmi  changed:

   What|Removed |Added

 CC||cyg...@tutanota.com

--- Comment #28 from kmi  ---
*** Bug 343825 has been marked as a duplicate of this bug. ***

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

[kmail2] [Bug 343825] KMail does not pull IMAP inbox mail

2019-12-01 Thread kmi

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

kmi  changed:

   What|Removed |Added

 Resolution|UNMAINTAINED|DUPLICATE
 CC||kamika...@web.de

--- Comment #7 from kmi  ---


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

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

[digikam] [Bug 399923] Segmentation fault during face detection

2019-12-01 Thread Maik Qualmann

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

--- Comment #280 from Maik Qualmann  ---
Git commit a0774df21a8f039e3355c8ad3ffa0ca20924dbbf by Maik Qualmann.
Committed on 01/12/2019 at 17:11.
Pushed by mqualmann into branch 'master'.

latest DImg change has a memory leak

M  +1-3core/libs/threadimageio/fileio/loadingcache.cpp
M  +1-1core/libs/threadimageio/fileio/loadsavetask.cpp
M  +1-1core/libs/threadimageio/preview/previewtask.cpp

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

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

[digikam] [Bug 399923] Segmentation fault during face detection

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

--- Comment #279 from timo...@zoho.com ---
With aacced0438943b163ffa95a3e1d82d74e4d065ae:

> digikam.general: Preview quality:  1
> digikam.dimg: 
> "/tmp/tmp.HClqSMevcG/Pictures/p/Syncthing-3TB/Telegram-Android/Telegram 
> Images/238228297_1801.jpg" : "JPEG" file identified
> digikam.general: Found 0 faces in "238224963_303731.jpg" QSize(720, 1280) 
> QSize(720, 1280)
> digikam.general: Removing old entries ()
> digikam.general: Check for finish:  51 packages, 0 infos to filter, 
> hasFinished() false
> digikam.general: Try to get preview from 
> "/tmp/tmp.HClqSMevcG/Pictures/p/Syncthing-3TB/Telegram-Android/Telegram 
> Images/238228345_51256.jpg"
> digikam.general: Preview quality:  1
> digikam.dimg: 
> "/tmp/tmp.HClqSMevcG/Pictures/p/Syncthing-3TB/Telegram-Android/Telegram 
> Images/238228345_51256.jpg" : "JPEG" file identified
> digikam.general: Found 0 faces in "238224970_75850.jpg" QSize(949, 1280) 
> QSize(949, 1280)
> digikam.general: Removing old entries ()
> digikam.general: Found 0 faces in "238224982_164876.jpg" QSize(1280, 949) 
> QSize(1280, 949)
> digikam.general: Found 0 faces in "238225065_102724.jpg" QSize(589, 429) 
> QSize(589, 429)
> digikam.general: Found 0 faces in "238225204_14626.jpg" QSize(720, 1280) 
> QSize(720, 1280)
> digikam.general: Removing old entries ()
> digikam.general: Check for finish:  51 packages, 0 infos to filter, 
> hasFinished() false
> digikam.general: Try to get preview from 
> "/tmp/tmp.HClqSMevcG/Pictures/p/Syncthing-3TB/Telegram-Android/Telegram 
> Images/238228411_98872.jpg"
> digikam.general: Preview quality:  1
> digikam.dimg: 
> "/tmp/tmp.HClqSMevcG/Pictures/p/Syncthing-3TB/Telegram-Android/Telegram 
> Images/238228411_98872.jpg" : "JPEG" file identified
> digikam.general: Removing old entries ()
> digikam.general: Check for finish:  51 packages, 0 infos to filter, 
> hasFinished() false
> digikam.general: Try to get preview from 
> "/tmp/tmp.HClqSMevcG/Pictures/p/Syncthing-3TB/Telegram-Android/Telegram 
> Images/238228432_91266.jpg"
> digikam.general: Preview quality:  1
> digikam.dimg: 
> "/tmp/tmp.HClqSMevcG/Pictures/p/Syncthing-3TB/Telegram-Android/Telegram 
> Images/238228432_91266.jpg" : "JPEG" file identified
> digikam.general: Removing old entries ()
> digikam.general: Check for finish:  51 packages, 0 infos to filter, 
> hasFinished() false
> digikam.general: Try to get preview from 
> "/tmp/tmp.HClqSMevcG/Pictures/p/Syncthing-3TB/Telegram-Android/Telegram 
> Images/238228438_206539.jpg"
> digikam.general: Preview quality:  1
> digikam.dimg: 
> "/tmp/tmp.HClqSMevcG/Pictures/p/Syncthing-3TB/Telegram-Android/Telegram 
> Images/238228438_206539.jpg" : "JPEG" file identified
> digikam.facesengine: Good rect =  QRect(76,85 71x104) , conf =  0.999438
> digikam.general: Found 1 faces in "238225234_157978.jpg" QSize(1280, 959) 
> QSize(1280, 959)
> digikam.general: Removing old entries ()
> digikam.general: Check for finish:  51 packages, 0 infos to filter, 
> hasFinished() false
> digikam.general: Found 0 faces in "238225255_170020.jpg" QSize(1280, 949) 
> QSize(1280, 949)
> digikam.general: Removing old entries ()
> digikam.general: Found 0 faces in "238225346_22680.jpg" QSize(949, 1280) 
> QSize(949, 1280)
> digikam.general: Removing old entries ()
> digikam.general: Found 0 faces in "238225406_274036.jpg" QSize(1280, 720) 
> QSize(1280, 720)
> digikam.general: Removing old entries ()
> digikam.general: Found 0 faces in "238225432_9767.jpg" QSize(960, 894) 
> QSize(960, 894)
> digikam.general: Removing old entries ()
> 
> Thread 52 "Thread (pooled)" received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7fff2af58700 (LWP 21794)]
> Digikam::PreviewLoadingTask::execute (this=0x31e1640)
> at 
> /tmp/tmp.HClqSMevcG/digikam/core/libs/threadimageio/preview/previewtask.cpp:325
> 325 if (l->accessMode() == 
> LoadSaveThread::AccessModeReadWrite)
> (gdb) bt
> #0  Digikam::PreviewLoadingTask::execute (this=0x31e1640) at 
> /tmp/tmp.HClqSMevcG/digikam/core/libs/threadimageio/preview/previewtask.cpp:325
> #1  0x7797d77e in Digikam::LoadSaveThread::run (this=0x5525c00) at 
> /tmp/tmp.HClqSMevcG/digikam/core/libs/threadimageio/fileio/loadsavethread.cpp:133
> #2  0x7799de0e in Digikam::DynamicThread::Private::run 
> (this=0x3acb730) at 
> /tmp/tmp.HClqSMevcG/digikam/core/libs/threads/dynamicthread.cpp:183
> #3  0x74b1b7d2 in ?? () from 
> /nix/store/683732s7dq6bxrl267lcadl5lvn6i4nh-qtbase-5.12.0/lib/libQt5Core.so.5
> #4  0x74b17062 in ?? () from 
> /nix/store/683732s7dq6bxrl267lcadl5lvn6i4nh-qtbase-5.12.0/lib/libQt5Core.so.5
> #5  0x744e2ef7 in start_thread () from 
> /nix/store/iykxb0bmfjmi7s53kfg6pjbfpd8jmza6-glibc-2.27/lib/libpthread.so.0
> #6  0x7441822f in clone () from 
> /nix/store/iykxb0bmfjmi7s53kfg6pjbfpd8jmza6-glibc-2.27/lib/libc.so.6
> (gdb)

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

[digikam] [Bug 412067] I get a error message: "Error while opening the database".

2019-12-01 Thread Bart

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

--- Comment #4 from Bart  ---
Created attachment 124243
  --> https://bugs.kde.org/attachment.cgi?id=124243=edit
Debugview  log

When digikam stops, in the top it displays: 
Checking ICC repository

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

[digikam] [Bug 412067] I get a error message: "Error while opening the database".

2019-12-01 Thread Bart

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

Bart  changed:

   What|Removed |Added

 CC||bart@smedema.net

--- Comment #3 from Bart  ---
Have the same issue after the following situation.
1) Changed network topology, so my database is not reachable anymore on the
existing location. (MySQL)
2) Digikam detects this. When proceding without database hangs.

I'll attach the logs.

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

[Active Window Control] [Bug 414724] New: Bad file management