[kalgebra] [Bug 402960] Can't put a function on the 3D graphic

2019-01-06 Thread Nasty
https://bugs.kde.org/show_bug.cgi?id=402960

--- Comment #2 from Nasty  ---
sorry I solved it

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

[kalgebra] [Bug 402960] Can't put a function on the 3D graphic

2019-01-06 Thread Nasty
https://bugs.kde.org/show_bug.cgi?id=402960

--- Comment #1 from Nasty  ---
sorry, I solved it.

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

[kalgebra] [Bug 402960] New: Can't put a function on the 3D graphic

2019-01-06 Thread Nasty
https://bugs.kde.org/show_bug.cgi?id=402960

Bug ID: 402960
   Summary: Can't put a function on the 3D graphic
   Product: kalgebra
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: aleix...@kde.org
  Reporter: anastasia4es...@gmail.com
  Target Milestone: ---

SUMMARY
Can't put a function on the 3D graphic.

STEPS TO REPRODUCE
1. You enter on the section of the 3D.
2. You write the function on the search, down below.
3. It doesn't get the function.


EXPECTED RESULT:
That the function have been represented on the graphic.


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

[gcompris] [Bug 402959] New: crash on chess move

2019-01-06 Thread bce
https://bugs.kde.org/show_bug.cgi?id=402959

Bug ID: 402959
   Summary: crash on chess move
   Product: gcompris
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: bruno.coud...@gcompris.net
  Reporter: bruno.ce...@gmail.com
  Target Milestone: ---

SUMMARY
systematic crash after chess move

STEPS TO REPRODUCE
1. open "end of party" chess game
2. move queen F1 to E2 -OR-  move queen G1 to E3

OBSERVED RESULT
systematic crash

basic log :
exeCount set to:  xxx
qml: enter main.qml (run #xxx, ratio=2.076923076923077, fontRatio=2.25,
dpi=128, sharedWritablePath=/home/***/.local/share/GCompris)
Downloading resource file "data2/voices-ogg/voices-fr.rcc"
Local resource is up-to-date: "voices-fr.rcc"
Successfully registered resource
"/home/***/.cache/KDE/gcompris-qt/data2/voices-ogg/voices-fr.rcc"
Erreur de segmentation (core dumped)

 ( last line : segfault in French without detail )

EXPECTED RESULT
no crash


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: xUbuntu 18.10 - 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 5 

ADDITIONAL INFORMATION
gcompris-qt 0.91 (xUbuntu 18.10)

(thx to specify into help if a verbose mode is available )

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

[akregator] [Bug 386699] the date of atom feeds are wrong

2019-01-06 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=386699

Laurent Montel  changed:

   What|Removed |Added

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

--- Comment #1 from Laurent Montel  ---
For me it's ok.
Could you verify with new version ?

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

[krita] [Bug 402834] Add dithering to gradients

2019-01-06 Thread Raghavendra kamath
https://bugs.kde.org/show_bug.cgi?id=402834

--- Comment #3 from Raghavendra kamath  ---
Sorry for taking this different tangent. I think dithering should be in how
colors are mixed and shown on screen and not just in gradients.  for example
there will be banding when you convert from 16 bit to 8 bit and sometime the
look of the image will change drastically due to this. So i think dithering
should be added to converting images , and if possible everyplace where there
is a possibility of seeing a banding.

A work around for this situation is to add noise spread filter from gmic

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

[digikam] [Bug 372340] Tagged face areas on portait (vertical) oriented images are mispositioned

2019-01-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=372340

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

   What|Removed |Added

Version|5.4.0   |6.0.0

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

[kwin] [Bug 402943] KWin crashes when closing program and switching virtual desktop at the same time

2019-01-06 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=402943

Martin Flöser  changed:

   What|Removed |Added

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

--- Comment #5 from Martin Flöser  ---
Opening as debug information is provided.

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

[kalzium] [Bug 402297] Avogadro styles are shown untranslated in the Molecule Editor

2019-01-06 Thread Burkhard Lueck
https://bugs.kde.org/show_bug.cgi?id=402297

Burkhard Lueck  changed:

   What|Removed |Added

 CC||lu...@hube-lueck.de

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

[Falkon] [Bug 402936] Usernames and passwords are stored for autofill as plain text in sqlite database which is the default option

2019-01-06 Thread Prasad Murthy
https://bugs.kde.org/show_bug.cgi?id=402936

--- Comment #4 from Prasad Murthy  ---
If the encrypted backend does the same and if it is available on all systems
then why not enable it by default and remove the unencrypted database option?

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

[elisa] [Bug 397523] Add keyboard shortcut to seek/scrub/navigate/fast forward/reverse audio files

2019-01-06 Thread Ashwin Dhakaita
https://bugs.kde.org/show_bug.cgi?id=397523

Ashwin Dhakaita  changed:

   What|Removed |Added

 CC||ashwingpdhaka...@gmail.com
 Status|CONFIRMED   |ASSIGNED
   Assignee|matthieu_gall...@yahoo.fr   |ashwingpdhaka...@gmail.com

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

[korganizer] [Bug 402958] New: Korganizer crashes on startup

2019-01-06 Thread Raghavendra kamath
https://bugs.kde.org/show_bug.cgi?id=402958

Bug ID: 402958
   Summary: Korganizer crashes on startup
   Product: korganizer
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: ra...@raghukamath.com
  Target Milestone: ---

SUMMARY
On arch linux  with korganizer version 5.10, crashes on startup.

STEPS TO REPRODUCE
1. Open Korganizer 5.10 in arch linux


OBSERVED RESULT
Crash on opening


SOFTWARE/OS VERSIONS

Operating System: Arch Linux 
KDE Plasma Version: 5.14.4
Qt Version: 5.12.0
KDE Frameworks Version: 5.53.0
Kernel Version: 4.20.0-arch1-1-ARCH


ADDITIONAL INFORMATION

-- Backtrace --



Application: KOrganizer (korganizer), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe5cb370840 (LWP 2511))]

Thread 5 (Thread 0x7fe5c2dee700 (LWP 2516)):
#0  0x7fe5d3a1cc21 in poll () from /usr/lib/libc.so.6
#1  0x7fe5d102f540 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fe5d102f62e in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fe5d3f695c4 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7fe5d3f1258c in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7fe5d3d565c9 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7fe5d3d579cc in ?? () from /usr/lib/libQt5Core.so.5
#7  0x7fe5d1c28a9d in start_thread () from /usr/lib/libpthread.so.0
#8  0x7fe5d3a27b23 in clone () from /usr/lib/libc.so.6

Thread 4 (Thread 0x7fe5c35ef700 (LWP 2514)):
#0  0x7fe5d0fdd424 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0
#1  0x7fe5d102f639 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#2  0x7fe5d3f695c4 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#3  0x7fe5d3f1258c in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#4  0x7fe5d3d565c9 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#5  0x7fe5d3d579cc in ?? () from /usr/lib/libQt5Core.so.5
#6  0x7fe5d1c28a9d in start_thread () from /usr/lib/libpthread.so.0
#7  0x7fe5d3a27b23 in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7fe5c893e700 (LWP 2513)):
#0  0x7fe5d3a1cc21 in poll () from /usr/lib/libc.so.6
#1  0x7fe5d102f540 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fe5d102f62e in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fe5d3f695c4 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7fe5d3f1258c in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7fe5d3d565c9 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7fe5d3690ba6 in ?? () from /usr/lib/libQt5DBus.so.5
#7  0x7fe5d3d579cc in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7fe5d1c28a9d in start_thread () from /usr/lib/libpthread.so.0
#9  0x7fe5d3a27b23 in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7fe5c9f60700 (LWP 2512)):
#0  0x7fe5d3a1cc21 in poll () from /usr/lib/libc.so.6
#1  0x7fe5d0fa4630 in ?? () from /usr/lib/libxcb.so.1
#2  0x7fe5d0fa62db in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7fe5caf3496b in ?? () from /usr/lib/libQt5XcbQpa.so.5
#4  0x7fe5d3d579cc in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7fe5d1c28a9d in start_thread () from /usr/lib/libpthread.so.0
#6  0x7fe5d3a27b23 in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7fe5cb370840 (LWP 2511)):
[KCrash Handler]
#6  0x7fe5d3dfacba in ?? () from /usr/lib/libQt5Core.so.5
#7  0x7fe5d3df45d9 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7fe5d3d9d0ef in ?? () from /usr/lib/libQt5Core.so.5
#9  0x7fe5d3d9d56d in ?? () from /usr/lib/libQt5Core.so.5
#10 0x7fe5d3d9db04 in QDateTime::QDateTime(QDate const&, QTime const&,
QTimeZone const&) () from /usr/lib/libQt5Core.so.5
#11 0x7fe5d51375d0 in KCalCore::MemoryCalendar::rawEvents(QDate const&,
QDate const&, QTimeZone const&, bool) const () from
/usr/lib/libKF5CalendarCore.so.5
#12 0x7fe5d50ea259 in KCalCore::Calendar::events(QDate const&, QDate
const&, QTimeZone const&, bool) const () from /usr/lib/libKF5CalendarCore.so.5
#13 0x7fe5d5488dde in ?? () from /usr/lib/libkorganizerprivate.so.5
#14 0x7fe5d548a608 in ?? () from /usr/lib/libkorganizerprivate.so.5
#15 0x7fe5d5484265 in ?? () from /usr/lib/libkorganizerprivate.so.5
#16 0x7fe5d547e010 in ?? () from /usr/lib/libkorganizerprivate.so.5
#17 0x7fe5d5472260 in CalendarView::CalendarView(QWidget*) () from
/usr/lib/libkorganizerprivate.so.5
#18 0x55cddd3da7fc in ?? ()
#19 0x55cddd3dbc7d in ?? ()
#20 0x55cddd3dc84f in ?? ()
#21 0x7fe5d552c605 in
KontactInterface::PimUniqueApplication::start(QStringList const&, bool) () 

[kdenlive] [Bug 401752] Track generators are listed twice in appimage version

2019-01-06 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=401752

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

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

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

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

[krita] [Bug 402831] Resizing Brush with shift +lmb drag is lagging, and not smooth for various complex brush tips

2019-01-06 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=402831

Bug Janitor Service  changed:

   What|Removed |Added

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

--- Comment #4 from Bug Janitor Service  ---
Thanks for your comment!

Automatically switching the status of this bug to REPORTED so that the KDE team
knows that the bug is ready to get confirmed.

In the future you may also do this yourself when providing needed information.

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

[Discover] [Bug 401873] system will not update

2019-01-06 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=401873

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

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

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

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

[krita] [Bug 402535] Krita memory leaks or endless loop when using freehand brush with perspective assistant

2019-01-06 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=402535

Bug Janitor Service  changed:

   What|Removed |Added

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

--- Comment #10 from Bug Janitor Service  ---
Thanks for your comment!

Automatically switching the status of this bug to REPORTED so that the KDE team
knows that the bug is ready to get confirmed.

In the future you may also do this yourself when providing needed information.

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

[kdenlive] [Bug 401642] Unable to capture screen and cam

2019-01-06 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=401642

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

[kdenlive] [Bug 381239] Capture audio dub

2019-01-06 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=381239

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

[kdenlive] [Bug 401748] Action "Disable clip" is not available in JogShuttle buttons configuration

2019-01-06 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=401748

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

[kmymoney] [Bug 402473] Change Date Format to ddmmyyyy

2019-01-06 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=402473

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

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

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

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

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

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

[latte-dock] [Bug 401580] Handling of pinned applications such as gnome-boxes and nautilus

2019-01-06 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=401580

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 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.

[kdenlive] [Bug 401753] DVD wizard freezes when trying to add chapters (with backtrace)

2019-01-06 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=401753

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 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.

[kmymoney] [Bug 402474] Credit card balance always appears as negative even when positive

2019-01-06 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=402474

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

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

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

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

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

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

[kdenlive] [Bug 401750] Time code overlay not rendered correctly in rendered video (possibly appimage related)

2019-01-06 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=401750

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

[kwin] [Bug 401877] kWin crashed after repeatedly invoking screen corners

2019-01-06 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=401877

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|BACKTRACE   |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.

[kscreenlocker] [Bug 402921] 2FA feature for greeter

2019-01-06 Thread Karouka
https://bugs.kde.org/show_bug.cgi?id=402921

--- Comment #2 from Karouka  ---
(In reply to David Edmundson from comment #1)
> You're mixing up terms. 
> 
> kscreenlocker is not a login interface equivalent to GDM or lightDM

I understand that kscreenlocker is just a lock-up tool like xscrrensaver, etc.
DM is another tool which 'introduce' the KDE or other DE.

Under the normal KDE experience, a user may use the kscreenlocker to lock up
their desktop session, instead of log out to use DM-related login interface.

Upon the issue, when I change the auth line about 2FA tools in 'required' mode
in /etc/pam.d/system-login, the lightDM works perfectly, but when you enter the
KDE, using kscreenlocker to lock your session, their is the problem.

When I change the line into 'sufficient' mode, the kscreenlocker works!

It seems that there should be the implementation to help entering the
verification code

I have tried GDM, there is no such a issue in the previous login or later lock
screen.

Thanks.

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

[kwin] [Bug 397595] Window Decorations are not properly highlighting the selected theme

2019-01-06 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=397595

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #4 from Nate Graham  ---
That commit doesn't fully fix the issue for me. The active decoration theme is
correctly selected when opening the KCM standalone in `kcmshell5`, but not from
within System Settings itself.

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

[plasmashell] [Bug 402957] New: Pressing ENTER does not reveal hidden login module in Breeze/Breath Theme for SDDM

2019-01-06 Thread Tyson Tan
https://bugs.kde.org/show_bug.cgi?id=402957

Bug ID: 402957
   Summary: Pressing ENTER does not reveal hidden login module in
Breeze/Breath Theme for SDDM
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Look & Feel package
  Assignee: plasma-b...@kde.org
  Reporter: tysont...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY
On SDDM login screen using Breeze/Breath theme, the login module would
disappear after a while without input. Pressing Enter does not reveal the
password input field but actually submit the password. This is a small thing
but nonetheless a real nuisance. Combined with SDDM not being able to show
masked password letters on some occasions (on multiple screen setup) it is a
major source of confusion.

This bug was first reported to SDDM: https://github.com/sddm/sddm/issues/1089
And with David Edmundson pointing it out, we relay it to
Plasmashell/Lookandfeel

My opinions:

People usually make their input only when they can see an input field. They
probably do not realize they are still inputting password when the password
field is absent. Unwanted letters would probably be recorded as part of the
password and cause the login to fail, seemingly "without any reason".

People tend to use mouse click or to press a key on their keyboard (usually a
modifier/space/enter) to reveal password fields before they consider themselves
in a valid password input conversation. This is also how roughly Windows 7+ and
many other OS design their login screen.

Although we can move mouse or input letters to reveal the login module, note
that clicking a mouse button does not always comes with mouse movement, so it
is very confusing as the user would perceive it as "the password field appears
only sometimes as I click my mouse".

My suggestions:

1) Allow modifier/enter/space/mouse click/drag to reveal password input module.
2) When the login module is hidden, do not record any password input.
3) When the login module is hidden, do not submit the password by pressing
ENTER.
4) Always show correct masked letters when the password input field is on
screen.

SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: Manjaro 18.0.2 KDE
(available in About System)
KDE Plasma Version: 5.14.4
KDE Frameworks Version: 5.53.0
Qt Version: 5.12.0

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

[plasmashell] [Bug 402587] Snap apps pinned to Task Manager get executed by their path, not the exec line of their .desktop file

2019-01-06 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402587

Nate Graham  changed:

   What|Removed |Added

 Status|REOPENED|CONFIRMED

--- Comment #8 from Nate Graham  ---
Thanks for the information!

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

[kinfocenter] [Bug 402949] kinfocenter does not present the usb devices correctly

2019-01-06 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402949

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[kamoso] [Bug 402956] New: Multiple webcam UI is not as good as it could be

2019-01-06 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402956

Bug ID: 402956
   Summary: Multiple webcam UI is not as good as it could be
   Product: kamoso
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aleix...@kde.org
  Reporter: n...@kde.org
  Target Milestone: ---

I have a laptop with two webcams: a normal one and an infrared camera for the
"Windows Hello" feature that is mostly useless.

Kamoso does handle this case, which is nice, but the presentation is not as
good as it could be: two buttons appear in the top-left corner of the window.
Problems with this:
- The buttons have no labels so you can't see what they are, or which camera
they're for
- The button corresponding to the current camera isn't selected or highlighted
somehow

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

[Systemd KCM] [Bug 361558] No clear way to run Systemd KCM from terminal if systemsettings5 not installed

2019-01-06 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=361558

Christoph Feck  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

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

[kamoso] [Bug 402955] New: Burst mode should not be so scary

2019-01-06 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402955

Bug ID: 402955
   Summary: Burst mode should not be so scary
   Product: kamoso
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: aleix...@kde.org
  Reporter: n...@kde.org
  Target Milestone: ---

Burst mode is really scary right now.

Once it starts going, it never stops until the user explicitly stops it. This
is hard due to Bug 402953. While it's going, it's scary because the screen
keeps flashing once per second forever. The effects is really disconcerting.
The first time I used it, I immediately got a very strong "must throw the
computer out the window" feeling. :(

Ideas to improve this:
- Only take 5 pictures and then stop, and also fix Bug 402951
- Increase the interval between shots to 2 or more seconds
- Provide a simple way to disable the flash effect

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

[kamoso] [Bug 402954] New: Play a picture taking click sound when taking a photo in picture or burst mode

2019-01-06 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402954

Bug ID: 402954
   Summary: Play a picture taking click sound when taking a photo
in picture or burst mode
   Product: kamoso
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: aleix...@kde.org
  Reporter: n...@kde.org
  Target Milestone: ---

The title says it all. :)  Most photo apps do this, and Kamoso should too.

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

[kamoso] [Bug 402953] When in video or burst mode, show an actual stop button somewhere

2019-01-06 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402953

Nate Graham  changed:

   What|Removed |Added

   Severity|normal  |wishlist

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

[kamoso] [Bug 402953] New: When in video or burst mode, show an actual stop button somewhere

2019-01-06 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402953

Bug ID: 402953
   Summary: When in video or burst mode, show an actual stop
button somewhere
   Product: kamoso
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aleix...@kde.org
  Reporter: n...@kde.org
  Target Milestone: ---

The buttons for Video and Burst modes are toggles rather than pushbuttons,
which is confusing because nothing about their appearance suggests this, and
the usability isn't great. Especially in burst mode, escaping from it quickly
is rather difficult which is extremely disconcerting.

We should make all of the three mode buttons just be regular old pushbuttons,
and conditionally display a "Stop" button when Video or Burst modes are active.
That way it will be completely obvious how to stop recording/shooting.

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

[kamoso] [Bug 402952] All effects in gallery drawer disappear after using burst mode once

2019-01-06 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402952

Nate Graham  changed:

   What|Removed |Added

Summary|ALl effects in gallery  |All effects in gallery
   |drawer disappear after  |drawer disappear after
   |using burst mode once   |using burst mode once

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

[kamoso] [Bug 402952] New: ALl effects in gallery drawer disappear after using burst mode once

2019-01-06 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402952

Bug ID: 402952
   Summary: ALl effects in gallery drawer disappear after using
burst mode once
   Product: kamoso
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aleix...@kde.org
  Reporter: n...@kde.org
  Target Milestone: ---

SUMMARY
Kamoso from git master

STEPS TO REPRODUCE
1. Open left drawer and verify that effects are there
2. Use burst mode
3. Turn off burst mode
4, Open the left drawer again

OBSERVED RESULT
All effects are gone! It's just a big white empty drawer

EXPECTED RESULT
Effects are still there

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

[kamoso] [Bug 402951] New: Kamoso doesn't display the ModeInfo text anymore

2019-01-06 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402951

Bug ID: 402951
   Summary: Kamoso doesn't display the ModeInfo text anymore
   Product: kamoso
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aleix...@kde.org
  Reporter: n...@kde.org
  Target Milestone: ---

Kamoso from git master

This bit just doesn't seem to work:

Text {
anchors {
horizontalCenter: parent.horizontalCenter
top: parent.top
margins: 20
}

text: root.pageStack.currentItem.actions.main.modeInfo


No text is rendered at the top.

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

[kspaceduel] [Bug 402950] New: KSpaceDuel crashed for no apparent reason

2019-01-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=402950

Bug ID: 402950
   Summary: KSpaceDuel crashed for no apparent reason
   Product: kspaceduel
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dirkrath...@gmx.de
  Reporter: lessth...@airmail.cc
CC: kde-games-b...@kde.org
  Target Milestone: ---

Application: kspaceduel (2.1)

Qt Version: 5.11.2
Frameworks Version: 5.53.0
Operating System: Linux 4.15.0-43-generic x86_64
Distribution: KDE neon User Edition 5.14

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

Playing the game like normal, as I had for about 50 rounds across several
different sessions without a crash.
No idea if it's related but I had picked up a green circle powerup thing less
than half a second before the game crashed.

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

Thread 3 (Thread 0x7f5dc0973700 (LWP 10823)):
#0  0x7f5dd9789bf9 in __GI___poll (fds=0x7f5dbc004db0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f5dd3324539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f5dd332464c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f5dda46204b in QEventDispatcherGlib::processEvents
(this=0x7f5dbc000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x7f5dda40630a in QEventLoop::exec (this=this@entry=0x7f5dc0972d70,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:214
#5  0x7f5dda231bba in QThread::exec (this=) at
thread/qthread.cpp:525
#6  0x7f5dd8c73e45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f5dda23cadb in QThreadPrivate::start (arg=0x7f5dd8eebd60) at
thread/qthread_unix.cpp:367
#8  0x7f5dd4e4d6db in start_thread (arg=0x7f5dc0973700) at
pthread_create.c:463
#9  0x7f5dd979688f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f5dc8e0f700 (LWP 10822)):
#0  0x7f5dd9789bf9 in __GI___poll (fds=0x7f5dc8e0eca8, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f5dd30bb747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f5dd30bd36a in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f5dcbdcfed9 in QXcbEventReader::run (this=0x557ec66f16a0) at
qxcbconnection.cpp:1391
#4  0x7f5dda23cadb in QThreadPrivate::start (arg=0x557ec66f16a0) at
thread/qthread_unix.cpp:367
#5  0x7f5dd4e4d6db in start_thread (arg=0x7f5dc8e0f700) at
pthread_create.c:463
#6  0x7f5dd979688f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f5ddd20c800 (LWP 10820)):
[KCrash Handler]
#6  Ai::nextPositions (this=this@entry=0x557ec67d81a0, sp=...,
a=a@entry=0x557ec68aef90, frames=frames@entry=2) at ./ai.cpp:208
#7  0x557ec646537d in Ai::calculateNextPositions
(this=this@entry=0x557ec67d81a0) at ./ai.cpp:226
#8  0x557ec6466f21 in Ai::think (this=0x557ec67d81a0) at ./ai.cpp:116
#9  0x557ec64703a4 in MyMainView::timerEvent (this=0x557ec6777590,
event=) at ./mainview.cpp:602
#10 0x7f5dda437b9b in QObject::event (this=this@entry=0x557ec6777590,
e=e@entry=0x7fff86abd3e0) at kernel/qobject.cpp:1273
#11 0x7f5ddb1d41ab in QWidget::event (this=0x557ec6777590,
event=0x7fff86abd3e0) at kernel/qwidget.cpp:9353
#12 0x7f5ddb194e1c in QApplicationPrivate::notify_helper
(this=this@entry=0x557ec66d34b0, receiver=receiver@entry=0x557ec6777590,
e=e@entry=0x7fff86abd3e0) at kernel/qapplication.cpp:3727
#13 0x7f5ddb19c3ef in QApplication::notify (this=0x7fff86abd720,
receiver=0x557ec6777590, e=0x7fff86abd3e0) at kernel/qapplication.cpp:3486
#14 0x7f5dda407fe8 in QCoreApplication::notifyInternal2
(receiver=0x557ec6777590, event=event@entry=0x7fff86abd3e0) at
kernel/qcoreapplication.cpp:1048
#15 0x7f5dda4614be in QCoreApplication::sendEvent (event=0x7fff86abd3e0,
receiver=) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:234
#16 QTimerInfoList::activateTimers (this=0x557ec671f210) at
kernel/qtimerinfo_unix.cpp:643
#17 0x7f5dda461c81 in timerSourceDispatch (source=) at
kernel/qeventdispatcher_glib.cpp:182
#18 0x7f5dd3324387 in g_main_context_dispatch () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x7f5dd33245c0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x7f5dd332464c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7f5dda46202f in QEventDispatcherGlib::processEvents
(this=0x557ec6720d00, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#22 0x7f5dcbe5b761 in QPAEventDispatcherGlib::processEvents

[kinfocenter] [Bug 402949] New: kinfocenter does not present the usb devices correctly

2019-01-06 Thread Alexandre
https://bugs.kde.org/show_bug.cgi?id=402949

Bug ID: 402949
   Summary: kinfocenter does not present the usb devices correctly
   Product: kinfocenter
   Version: 5.14.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: USB Devices
  Assignee: hubn...@gmail.com
  Reporter: alexandre...@gmail.com
  Target Milestone: ---

Created attachment 117314
  --> https://bugs.kde.org/attachment.cgi?id=117314=edit
Patch for the problem

SUMMARY
the USBview portion of kinfocenter does not present the information correclty
for devices that below the first level

STEPS TO REPRODUCE
1. Execute kinfocenter
2. List USB devices on the machine
3. 

OBSERVED RESULT

List only the first level of devices (bus 0-n) but no devices for the second
level)


EXPECTED RESULT

List all the devices on the USB bus

SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: Gentoo with kernel 4.20.0
(available in About System)
KDE Plasma Version: 5.14.4
KDE Frameworks Version: 5.53.0
Qt Version: 5.12.0

ADDITIONAL INFORMATION

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

[kamoso] [Bug 402948] New: Kamoso only ever displays mobile UI on the desktop

2019-01-06 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402948

Bug ID: 402948
   Summary: Kamoso only ever displays mobile UI on the desktop
   Product: kamoso
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aleix...@kde.org
  Reporter: n...@kde.org
  Target Milestone: ---

Kamoso from git master

When I run Kamoso on the desktop I see the mobile view, with the floating
triple-button toolbar on the bottom instead of a toolbar on top, and the left
pane collapsed behind a hamburger button instead of it being always visible.
This persists even if I make the window huge.

Kamoso should only show this view when in mobile mode or when the window is
tiny. Desktop users want a desktop UI.

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

[frameworks-kiconthemes] [Bug 402172] Compiling against Qt 5.12 breaks QIcon::themeName with Plama platform plugin

2019-01-06 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402172

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[krita] [Bug 402535] Krita memory leaks or endless loop when using freehand brush with perspective assistant

2019-01-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=402535

--- Comment #9 from genosim...@gmail.com ---
I posted a diff with a fix: https://phabricator.kde.org/D18024

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

[plasmashell] [Bug 402913] Application Shortcuts Blocked by KDE

2019-01-06 Thread Markus Ewald
https://bugs.kde.org/show_bug.cgi?id=402913

Markus Ewald  changed:

   What|Removed |Added

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

--- Comment #7 from Markus Ewald  ---
This is the output of 'xev' when it IS working after doing the
bind-then-unbding workaround:

---

KeyPress event, serial 40, synthetic NO, window 0x3e1,
root 0x1e6, subw 0x0, time 61602401, (60,-19), root:(2359,702),
state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes: 
XmbLookupString gives 0 bytes: 
XFilterEvent returns: False

KeyPress event, serial 40, synthetic NO, window 0x3e1,
root 0x1e6, subw 0x0, time 61602681, (60,-19), root:(2359,702),
state 0x8, keycode 43 (keysym 0x68, h), same_screen YES,
XLookupString gives 1 bytes: (68) "h"
XmbLookupString gives 1 bytes: (68) "h"
XFilterEvent returns: False

KeyRelease event, serial 40, synthetic NO, window 0x3e1,
root 0x1e6, subw 0x0, time 61602729, (60,-19), root:(2359,702),
state 0x8, keycode 43 (keysym 0x68, h), same_screen YES,
XLookupString gives 1 bytes: (68) "h"
XFilterEvent returns: False

KeyRelease event, serial 40, synthetic NO, window 0x3e1,
root 0x1e6, subw 0x0, time 61603145, (60,-19), root:(2359,702),
state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes: 
XFilterEvent returns: False

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

[plasmashell] [Bug 402913] Application Shortcuts Blocked by KDE

2019-01-06 Thread Markus Ewald
https://bugs.kde.org/show_bug.cgi?id=402913

--- Comment #6 from Markus Ewald  ---
This is the output of 'xev' while Alt+H is NOT working:

---

KeyPress event, serial 40, synthetic NO, window 0x3e1,
root 0x1e6, subw 0x0, time 61349601, (64,-26), root:(2370,709),
state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes: 
XmbLookupString gives 0 bytes: 
XFilterEvent returns: False

FocusOut event, serial 40, synthetic NO, window 0x3e1,
mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 40, synthetic NO, window 0x3e1,
mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 40, synthetic NO, window 0x0,
keys:  0   0   0   0   0   8   0   0   1   0   0   0   0   0   0   0   
   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

KeyRelease event, serial 40, synthetic NO, window 0x3e1,
root 0x1e6, subw 0x0, time 61349913, (64,-26), root:(2370,709),
state 0x8, keycode 43 (keysym 0x68, h), same_screen YES,
XLookupString gives 1 bytes: (68) "h"
XFilterEvent returns: False

KeyRelease event, serial 40, synthetic NO, window 0x3e1,
root 0x1e6, subw 0x0, time 61350225, (64,-26), root:(2370,709),
state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes: 
XFilterEvent returns: False

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

[plasmashell] [Bug 402913] Application Shortcuts Blocked by KDE

2019-01-06 Thread Markus Ewald
https://bugs.kde.org/show_bug.cgi?id=402913

--- Comment #5 from Markus Ewald  ---
Created attachment 117313
  --> https://bugs.kde.org/attachment.cgi?id=117313=edit
kglobalshortcutsrc at a time when Alt+H is not working

The contents of this file do not change when I apply the workaround (even after
clicking 'apply' and quitting the System Settings application).

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

[Falkon] [Bug 402947] New: PyFalkon doesn't build with pyside 5.12

2019-01-06 Thread Antonio Rojas
https://bugs.kde.org/show_bug.cgi?id=402947

Bug ID: 402947
   Summary: PyFalkon doesn't build with pyside 5.12
   Product: Falkon
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: extensions
  Assignee: now...@gmail.com
  Reporter: aro...@archlinux.org
  Target Milestone: ---

With git master:

/build/falkon/src/build/src/plugins/PyFalkon/PyFalkon/plugininterface_wrapper.cpp:
In member function ‘virtual DesktopFile PluginInterfaceWrapper::metaData()
const’:
/build/falkon/src/build/src/plugins/PyFalkon/PyFalkon/plugininterface_wrapper.cpp:177:17:
error: converting to ‘DesktopFile’ from initializer list would use explicit
constructor ‘DesktopFile::DesktopFile()’
 return {};
 ^
/build/falkon/src/build/src/plugins/PyFalkon/PyFalkon/webhittestresult_wrapper.cpp:612:31:
warning: cast between incompatible function types from ‘PyObject*
(*)(PyObject*)’ {aka ‘_object* (*)(_object*)’} to ‘PyCFunction’ {aka ‘_object*
(*)(_object*, _object*)’} [-Wcast-function-type]
 {"__copy__", (PyCFunction)Sbk_WebHitTestResult___copy__, METH_NOARGS},
   ^
/build/falkon/src/build/src/plugins/PyFalkon/PyFalkon/plugininterface_wrapper.cpp:181:17:
error: converting to ‘DesktopFile’ from initializer list would use explicit
constructor ‘DesktopFile::DesktopFile()’
 return {};
 ^
/build/falkon/src/build/src/plugins/PyFalkon/PyFalkon/plugininterface_wrapper.cpp:190:17:
error: converting to ‘DesktopFile’ from initializer list would use explicit
constructor ‘DesktopFile::DesktopFile()’
 return {};
 ^
/build/falkon/src/build/src/plugins/PyFalkon/PyFalkon/plugininterface_wrapper.cpp:196:17:
error: converting to ‘DesktopFile’ from initializer list would use explicit
constructor ‘DesktopFile::DesktopFile()’
 return {};
 ^

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

[systemsettings] [Bug 402930] After you use the image picker to change the background image, your chosen image appears in the picker, but disappears if you navigate away from the KCM and then go back

2019-01-06 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402930

--- Comment #3 from Nate Graham  ---
Created attachment 117312
  --> https://bugs.kde.org/attachment.cgi?id=117312=edit
Prospective patch

I might need a little help here, if you can spare the time. The attached patch
fixes the issue in the KCM for me, but then SDDM doesn't load after a reboot,
and I'm not really knowledgeable enough about how it works to figure out why.

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

[okular] [Bug 402945] PDF: empty print preview and no printing possible

2019-01-06 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=402945

Albert Astals Cid  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|REPORTED|RESOLVED
 CC||aa...@kde.org

--- Comment #1 from Albert Astals Cid  ---
It's a poppler bug.

Please file a bug at https://gitlab.freedesktop.org/poppler/poppler/

Reasoning, pdftops + gs has this very same problem.

As workaround you can print by using the rasterize option.

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

[okular] [Bug 402939] Annotation workflow is completely broken

2019-01-06 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=402939

Albert Astals Cid  changed:

   What|Removed |Added

 CC||aa...@kde.org
 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Albert Astals Cid  ---
So you have found we have bugs.

Congratulations, using fixed as reason since there's not really a different
better resolution for "yeah, it's broken, we know and there's several bugs
about it already"

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

[digikam] [Bug 372340] Tagged face areas on portait (vertical) oriented images are mispositioned

2019-01-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=372340

kde-b...@debdan.net changed:

   What|Removed |Added

 CC||kde-b...@debdan.net

--- Comment #12 from kde-b...@debdan.net ---
I tested it with current Digikam 6.0.0-beta3 and the bug is still there:

This shows the problem:

$ convert -size 400x240 xc:skyblue -fill white -stroke black -draw "rectangle
80, 40 320,200" draw_rect.jpg
$ exiftool -n -Orientation=1 -XMP-mwg-rs:RegionAppliedToDimensionsH=240
-XMP-mwg-rs:RegionAppliedToDimensionsW=400
-XMP-mwg-rs:RegionAppliedToDimensionsUnit=pixel
-XMP-mwg-rs:RegionAreaUnit=normalized -XMP-mwg-rs:RegionName=John
-XMP-mwg-rs:RegionType=Face -XMP-mwg-rs:RegionAreaX=0.5
-XMP-mwg-rs:RegionAreaY=0.5 -XMP-mwg-rs:RegionAreaW=0.62
-XMP-mwg-rs:RegionAreaH=0.7 draw_rect.jpg

The location of the face area stays the same if the orientation is changed to
something different from top,left:

$ exiftool -n -Orientation=8 draw_rect.jpg

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

[systemsettings] [Bug 396076] Desktop effects KCM - Window Size too small when opened from kcmshell5

2019-01-06 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=396076

Nate Graham  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kwi
   ||n/d28827626931ed9f8fbfd618b
   ||bdcdf3fdce6a5e6
   Version Fixed In||5.15.0
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #7 from Nate Graham  ---
Git commit d28827626931ed9f8fbfd618bbdcdf3fdce6a5e6 by Nate Graham.
Committed on 06/01/2019 at 23:09.
Pushed by ngraham into branch 'master'.

[kcmkwin/compositing] Port Effects KCM to QQC2

Summary:
This patch ports the Effects KCM to QQC2, which yields the following benefits:
1. General performance enhancements of only using QQC2 rather than a mix of 1
and 2
2. Some code simplification is possible
3. Improves the appearance of the checkable menu items in the dropdown menu,
fixing https://bugs.kde.org/show_bug.cgi?id=402701
4. Improves the appearance when using a fractional scale factor, fixing
https://bugs.kde.org/show_bug.cgi?id=396725
5. Fixes the incorrect size when opened from `kcmshell5`

Along the way, two visual changes are introduced as a by-product of porting:
1. The scrollbar is inline, so it overlaps some of the buttons in the content.
This is somewhat undesirable, but adopting a Kirigami scrollview would fix
this.
2. The button that displays a dropdown menu no longer has a downward-pointing
arrow to indicate as such. This is not my preference, but there's a benefit to
being consistent, and eventually we could can change this in one place to
impeove the appearance of buttons that display dropdown menus everywhere in one
fell swoop.
Related: bug 396725, bug 402701
FIXED-IN: 5.15.0

Test Plan:
All functionality still works

In System Settings, showing improved checkable menu item appearance:
{F6523385}

In `kcmshell` at 1x scale:
{F6523386}

In `kcmshell` at 1.5x scale:
{F6523387}

Reviewers: #kwin, #plasma, davidedmundson

Reviewed By: #kwin, #plasma, davidedmundson

Subscribers: davidedmundson, kwin

Tags: #kwin

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

M  +60   -63   kcmkwin/kwincompositing/qml/EffectView.qml

https://commits.kde.org/kwin/d28827626931ed9f8fbfd618bbdcdf3fdce6a5e6

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

[systemsettings] [Bug 402701] "Desktop effects" filtering checkboxes don't get checked

2019-01-06 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402701

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kwi
   ||n/d28827626931ed9f8fbfd618b
   ||bdcdf3fdce6a5e6
   Version Fixed In||5.15.0
 Status|CONFIRMED   |RESOLVED

--- Comment #4 from Nate Graham  ---
Git commit d28827626931ed9f8fbfd618bbdcdf3fdce6a5e6 by Nate Graham.
Committed on 06/01/2019 at 23:09.
Pushed by ngraham into branch 'master'.

[kcmkwin/compositing] Port Effects KCM to QQC2

Summary:
This patch ports the Effects KCM to QQC2, which yields the following benefits:
1. General performance enhancements of only using QQC2 rather than a mix of 1
and 2
2. Some code simplification is possible
3. Improves the appearance of the checkable menu items in the dropdown menu,
fixing https://bugs.kde.org/show_bug.cgi?id=402701
4. Improves the appearance when using a fractional scale factor, fixing
https://bugs.kde.org/show_bug.cgi?id=396725
5. Fixes the incorrect size when opened from `kcmshell5`

Along the way, two visual changes are introduced as a by-product of porting:
1. The scrollbar is inline, so it overlaps some of the buttons in the content.
This is somewhat undesirable, but adopting a Kirigami scrollview would fix
this.
2. The button that displays a dropdown menu no longer has a downward-pointing
arrow to indicate as such. This is not my preference, but there's a benefit to
being consistent, and eventually we could can change this in one place to
impeove the appearance of buttons that display dropdown menus everywhere in one
fell swoop.
Related: bug 396725, bug 396076
FIXED-IN: 5.15.0

Test Plan:
All functionality still works

In System Settings, showing improved checkable menu item appearance:
{F6523385}

In `kcmshell` at 1x scale:
{F6523386}

In `kcmshell` at 1.5x scale:
{F6523387}

Reviewers: #kwin, #plasma, davidedmundson

Reviewed By: #kwin, #plasma, davidedmundson

Subscribers: davidedmundson, kwin

Tags: #kwin

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

M  +60   -63   kcmkwin/kwincompositing/qml/EffectView.qml

https://commits.kde.org/kwin/d28827626931ed9f8fbfd618bbdcdf3fdce6a5e6

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

[systemsettings] [Bug 396725] Configure desktop effects dialog:reading the effect names is impossible with fractional scaling

2019-01-06 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=396725

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||5.15.0
  Latest Commit||https://commits.kde.org/kwi
   ||n/d28827626931ed9f8fbfd618b
   ||bdcdf3fdce6a5e6
 Status|CONFIRMED   |RESOLVED

--- Comment #7 from Nate Graham  ---
Git commit d28827626931ed9f8fbfd618bbdcdf3fdce6a5e6 by Nate Graham.
Committed on 06/01/2019 at 23:09.
Pushed by ngraham into branch 'master'.

[kcmkwin/compositing] Port Effects KCM to QQC2

Summary:
This patch ports the Effects KCM to QQC2, which yields the following benefits:
1. General performance enhancements of only using QQC2 rather than a mix of 1
and 2
2. Some code simplification is possible
3. Improves the appearance of the checkable menu items in the dropdown menu,
fixing https://bugs.kde.org/show_bug.cgi?id=402701
4. Improves the appearance when using a fractional scale factor, fixing
https://bugs.kde.org/show_bug.cgi?id=396725
5. Fixes the incorrect size when opened from `kcmshell5`

Along the way, two visual changes are introduced as a by-product of porting:
1. The scrollbar is inline, so it overlaps some of the buttons in the content.
This is somewhat undesirable, but adopting a Kirigami scrollview would fix
this.
2. The button that displays a dropdown menu no longer has a downward-pointing
arrow to indicate as such. This is not my preference, but there's a benefit to
being consistent, and eventually we could can change this in one place to
impeove the appearance of buttons that display dropdown menus everywhere in one
fell swoop.
Related: bug 402701, bug 396076
FIXED-IN: 5.15.0

Test Plan:
All functionality still works

In System Settings, showing improved checkable menu item appearance:
{F6523385}

In `kcmshell` at 1x scale:
{F6523386}

In `kcmshell` at 1.5x scale:
{F6523387}

Reviewers: #kwin, #plasma, davidedmundson

Reviewed By: #kwin, #plasma, davidedmundson

Subscribers: davidedmundson, kwin

Tags: #kwin

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

M  +60   -63   kcmkwin/kwincompositing/qml/EffectView.qml

https://commits.kde.org/kwin/d28827626931ed9f8fbfd618bbdcdf3fdce6a5e6

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

[kdenlive] [Bug 402946] New: Add sRGB color space support

2019-01-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=402946

Bug ID: 402946
   Summary: Add sRGB color space support
   Product: kdenlive
   Version: unspecified
  Platform: Other
OS: All
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: 21na...@gmail.com
  Target Milestone: ---

It seems sRGB is not handled since profile/preset and render options do not
mention it.

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

[digikam] [Bug 402944] crash while looking at face tags

2019-01-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=402944

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

   What|Removed |Added

  Component|general |Faces-Workflow
 CC||caulier.gil...@gmail.com

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

[kwin] [Bug 402943] KWin crashes when closing program and switching virtual desktop at the same time

2019-01-06 Thread Lukas Bartl
https://bugs.kde.org/show_bug.cgi?id=402943

--- Comment #4 from Lukas Bartl  ---
It's not a real problem, because KWin starts again immediatly. But it's still a
bug, so i reported it.

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

[digikam] [Bug 402944] crash while looking at face tags

2019-01-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=402944

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

   What|Removed |Added

Version|unspecified |6.0.0

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

[kwin] [Bug 402943] KWin crashes when closing program and switching virtual desktop at the same time

2019-01-06 Thread Lukas Bartl
https://bugs.kde.org/show_bug.cgi?id=402943

--- Comment #3 from Lukas Bartl  ---
KWin crashed again, this time with kate. I closed kate and switched virtual
desktop to post the output here und KWin crashed again. The Backtrace is the
same.

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

[kwin] [Bug 402943] KWin crashes when closing program and switching virtual desktop at the same time

2019-01-06 Thread Lukas Bartl
https://bugs.kde.org/show_bug.cgi?id=402943

--- Comment #2 from Lukas Bartl  ---
KWin-Unterstützungsinformationen:
Benutzen Sie die folgenden Informationen, wenn Sie nach Unterstützung fragen,
z. B. auf http://forum.kde.org.
Sie enthalten Informationen über die momentan laufende Instanz, welche Optionen
verwendet werden,
welcher OpenGL-Treiber verwendet wird und welche Effekte laufen.
Bitte geben Sie die unten stehenden Informationen bei einem Pastebin-Dienst wie
http://paste.kde.org ein, anstatt sie direkt in die Hilfediskussionen zu
schreiben.

==

Version
===
KWin version: 5.14.4
Qt Version: 5.12.0
Qt compile version: 5.12.0
XCB compile version: 1.13.1

Operation Mode: X11 only

Build Options
=
KWIN_BUILD_DECORATIONS: yes
KWIN_BUILD_TABBOX: yes
KWIN_BUILD_ACTIVITIES: yes
HAVE_DRM: yes
HAVE_GBM: yes
HAVE_X11_XCB: yes
HAVE_EPOXY_GLX: yes
HAVE_WAYLAND_EGL: yes

X11
===
Vendor: The X.Org Foundation
Vendor Release: 12003000
Protocol Version/Revision: 11/0
SHAPE: yes; Version: 0x11
RANDR: yes; Version: 0x14
DAMAGE: yes; Version: 0x11
Composite: yes; Version: 0x4
RENDER: yes; Version: 0xb
XFIXES: yes; Version: 0x50
SYNC: yes; Version: 0x31
GLX: yes; Version: 0x0

Decoration
==
Plugin: org.kde.breeze
Theme: 
Blur: 0
onAllDesktopsAvailable: true
alphaChannelSupported: true
closeOnDoubleClickOnMenu: false
decorationButtonsLeft: 0, 2
decorationButtonsRight: 6, 3, 4, 5
borderSize: 3
gridUnit: 12
font: DejaVu Serif Condensed,11,-1,5,50,0,0,0,0,0,Book
smallSpacing: 3
largeSpacing: 12

Platform
==
Name: KWin::X11StandalonePlatform

Options
===
focusPolicy: 0
nextFocusPrefersMouse: false
clickRaise: true
autoRaise: false
autoRaiseInterval: 0
delayFocusInterval: 0
shadeHover: false
shadeHoverInterval: 250
separateScreenFocus: false
placement: 4
focusPolicyIsReasonable: true
borderSnapZone: 10
windowSnapZone: 10
centerSnapZone: 0
snapOnlyWhenOverlapping: false
rollOverDesktops: true
focusStealingPreventionLevel: 1
legacyFullscreenSupport: false
operationTitlebarDblClick: 5000
operationMaxButtonLeftClick: 5000
operationMaxButtonMiddleClick: 5015
operationMaxButtonRightClick: 5014
commandActiveTitlebar1: 0
commandActiveTitlebar2: 30
commandActiveTitlebar3: 2
commandInactiveTitlebar1: 4
commandInactiveTitlebar2: 30
commandInactiveTitlebar3: 2
commandWindow1: 7
commandWindow2: 8
commandWindow3: 8
commandWindowWheel: 31
commandAll1: 10
commandAll2: 3
commandAll3: 14
keyCmdAllModKey: 16777251
showGeometryTip: false
condensedTitle: false
electricBorderMaximize: true
electricBorderTiling: true
electricBorderCornerRatio: 0.25
borderlessMaximizedWindows: false
killPingTimeout: 5000
hideUtilityWindowsForInactive: true
inactiveTabsSkipTaskbar: false
autogroupSimilarWindows: false
autogroupInForeground: true
compositingMode: 1
useCompositing: true
compositingInitialized: true
hiddenPreviews: 1
glSmoothScale: 2
xrenderSmoothScale: false
maxFpsInterval: 1666
refreshRate: 0
vBlankTime: 600
glStrictBinding: true
glStrictBindingFollowsDriver: true
glCoreProfile: true
glPreferBufferSwap: 101
glPlatformInterface: 1
windowsBlockCompositing: true

Screen Edges

desktopSwitching: false
desktopSwitchingMovingClients: false
cursorPushBackDistance: 1x1
timeThreshold: 150
reActivateThreshold: 350
actionTopLeft: 0
actionTop: 0
actionTopRight: 0
actionRight: 0
actionBottomRight: 0
actionBottom: 0
actionBottomLeft: 0
actionLeft: 0

Screens
===
Multi-Head: no
Active screen follows mouse:  no
Number of Screens: 1

Screen 0:
-
Name: eDP-1
Geometry: 0,0,1920x1080
Scale: 1
Refresh Rate: 59.9339


Compositing
===
Compositing is active
Compositing Type: OpenGL
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) 
OpenGL version string: 4.5 (Core Profile) Mesa 18.3.1
OpenGL platform interface: GLX
OpenGL shading language version string: 4.50
Driver: Intel
GPU class: Unknown
OpenGL version: 4.5
GLSL version: 4.50
Mesa version: 18.3.1
X server version: 1.20.3
Linux kernel version: 4.20
Direct rendering: Requires strict binding: yes
GLSL shaders:  yes
Texture NPOT support:  yes
Virtual Machine:  no
OpenGL 2 Shaders are used
Painting blocks for vertical retrace:  no

Loaded Effects:
---
trackmouse
mousemark
mouseclick
lookingglass
kwin4_effect_translucency
kwin4_effect_morphingpopups
kwin4_effect_maximize
kwin4_effect_logout
kwin4_effect_login
dimscreen
kwin4_effect_frozenapp
kwin4_effect_fade
kwin4_effect_eyeonscreen
kwin4_effect_dialogparent
slidingpopups
slideback
screenshot
magiclamp
glide
desktopgrid
cubeslide
cube
colorpicker
sheet
wobblywindows
presentwindows
highlightwindow
fallapart
blur
contrast
startupfeedback
screenedge
kscreen

Currently Active Effects:
-
blur
contrast

Effect Settings:

trackmouse:
modifiers: 335544320
mousePolling: true

mousemark:
width: 3
color: #ff

mouseclick:
color1: #ff
color2: #00ff00

[okular] [Bug 402945] New: PDF: empty print preview and no printing possible

2019-01-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=402945

Bug ID: 402945
   Summary: PDF: empty print preview and no printing possible
   Product: okular
   Version: 1.5.1
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: printing
  Assignee: okular-de...@kde.org
  Reporter: moritzhaged...@gmail.com
  Target Milestone: ---

Created attachment 117311
  --> https://bugs.kde.org/attachment.cgi?id=117311=edit
sample file

SUMMARY
Unable to print, empty print preview, empty pdf export via 'print'

The files showing this bug were created with TCPDF 6.2.12.

Opening the print preview stdout showed:
"""
DEBUG: FC_WEIGHT didn't match
rangecheck -15
rangecheck -15
org.kde.okular.generators.spectre: Generated image does not match wanted size:
[0x0] vs requested [804x1137]
QImage::scaled: Image is a null image
"""


STEPS TO REPRODUCE
1. open document with okular.
2a. open print preview
2b. print file directly

OBSERVED RESULT
a. The print preview shows a blank page
b. no file is being sent to the printer/ pdf export (unless rasterization is
enforced)

EXPECTED RESULT
a. The print preview looks just like the file is shown in okular
b. a print

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 29
(available in About System)
KDE Plasma Version: 5.14.4
KDE Frameworks Version: 5.53.0
Qt Version: 5.11.1

ADDITIONAL INFORMATION
Found some very old bugreports with no print results. As I was not sure if they
are related and were not resolved, I created this one. Please move this if
redundant.

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

[kate] [Bug 402842] Can not print with kate and kwrite

2019-01-06 Thread Potomac
https://bugs.kde.org/show_bug.cgi?id=402842

--- Comment #3 from Potomac  ---
it is in fact a bug of Qt5 when a component generates PDF, when the locale of
the user is not english then numbers inside PDF are displayed with comma
separator instead point, which triggers a malformed PDF, and an error in cups,

for example for MediaBox objects the comma is used by Qt5 which is bad :

/MediaBox [0 0 595,00 842,00]

see this archlinux thread forum :
https://bbs.archlinux.org/viewtopic.php?pid=1824924#p1824924

and my bugreport :
https://bugreports.qt.io/browse/QTBUG-72868

a workaround is to set LC_NUMERIC to "C" before running a Qt5 application :

LC_NUMERIC=C kate

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

[systemsettings] [Bug 402930] After you use the image picker to change the background image, your chosen image appears in the picker, but disappears if you navigate away from the KCM and then go back

2019-01-06 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402930

Nate Graham  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from Nate Graham  ---
Found the bug: it's storing the file path as just the filename, not the full
path. Putting a full absolute file path in the Background= key in
/usr/share/sddm/themes/breeze/theme.conf.user fixes the issue for me. Patch
coming soon...

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

[KEXI] [Bug 392112] Deleted physical tables still visible in project navigator

2019-01-06 Thread Jarosław Staniek
https://bugs.kde.org/show_bug.cgi?id=392112

Jarosław Staniek  changed:

   What|Removed |Added

  Latest Commit|https://commits.kde.org/kex |https://commits.kde.org/kex
   |i/83a672c348ca9d263e9739bb3 |i/bcebf0787f0e75de019ba92e7
   |ee5566ca8d5d702 |730fc57c2b23a30

--- Comment #8 from Jarosław Staniek  ---
Git commit bcebf0787f0e75de019ba92e7730fc57c2b23a30 by Jaroslaw Staniek.
Committed on 06/01/2019 at 21:41.
Pushed by staniek into branch '3.2'.

Skip table name if physical table is non-existing, use the new tableNames API
in migration

Summary:
FIXED-IN:3.2.0

Note: functionality of migration is not affected, it's just the code cleanup
thanks to the new API.

Test Plan: Open kdb.git/autotests/data/missingTableTest.kexi, it should not
list persons table anymore.

Reviewers: piggz

Tags: #kexi

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

# Conflicts:
#   CMakeLists.txt

M  +37   -11   src/core/kexiproject.cpp
M  +3-15   src/migration/KexiSqlMigrate.cpp
M  +0-3src/migration/KexiSqlMigrate.h
M  +0-1src/migration/mysql/mysqlmigrate.cpp
M  +0-1src/migration/postgresql/PostgresqlMigrate.cpp

https://commits.kde.org/kexi/bcebf0787f0e75de019ba92e7730fc57c2b23a30

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

[KEXI] [Bug 392753] Crash when opening a report

2019-01-06 Thread Jarosław Staniek
https://bugs.kde.org/show_bug.cgi?id=392753

Jarosław Staniek  changed:

   What|Removed |Added

 Status|CLOSED  |RESOLVED
  Latest Commit|https://commits.kde.org/kex |https://commits.kde.org/kdb
   |i/90c3ed3251ddcebee4ac4d2dc |/d1b31bd8a6fc6632f8eeab70b5
   |e1c24c857967bd3 |e9a0f1c8630c8f
   Version Fixed In|3.2.0   |3.2

--- Comment #6 from Jarosław Staniek  ---
Git commit d1b31bd8a6fc6632f8eeab70b5e9a0f1c8630c8f by Jaroslaw Staniek.
Committed on 06/01/2019 at 21:16.
Pushed by staniek into branch '3.2'.

Fix handling ORDER BY part of queries

Summary:
- new APIs
- maintain relations between connections, queries and column infos
- fix cloning queries with ORDER BY
- update and add autotests

FIXED-IN:3.2
Related: bug 393705

Test Plan:
Required: KEXI & KDb 3.2 (current master)

Test 1: Open report and query from
https://bugs.kde.org/show_bug.cgi?id=392753#c0 in design and data views.
Expected: works, no crashes

Test 2: Try these on a standard Persons and Cars test:
select id from cars order by owner;
select id from cars order by owner, model, id;
select id, model from cars order by 2, 1;

Expected: works, no crash

Reviewers: piggz

Reviewed By: piggz

Subscribers: Kexi-Devel-list

Tags: #kdb

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

M  +3-0autotests/CMakeLists.txt
A  +212  -0autotests/OrderByColumnTest.cpp [License: LGPL (v2+)]
A  +46   -0autotests/OrderByColumnTest.h [License: LGPL (v2+)]
M  +2-2src/KDbNativeStatementBuilder.cpp
M  +87   -28   src/KDbOrderByColumn.cpp
M  +40   -13   src/KDbOrderByColumn.h
M  +17   -28   src/KDbQueryColumnInfo.cpp
M  +25   -1src/KDbQueryColumnInfo.h
M  +18   -4src/KDbQuerySchema.cpp
M  +29   -1src/KDbQuerySchema_p.h

https://commits.kde.org/kdb/d1b31bd8a6fc6632f8eeab70b5e9a0f1c8630c8f

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

[KEXI] [Bug 393705] Exporting query with ORDER BY crashes KEXI

2019-01-06 Thread Jarosław Staniek
https://bugs.kde.org/show_bug.cgi?id=393705

--- Comment #10 from Jarosław Staniek  ---
Git commit d1b31bd8a6fc6632f8eeab70b5e9a0f1c8630c8f by Jaroslaw Staniek.
Committed on 06/01/2019 at 21:16.
Pushed by staniek into branch '3.2'.

Fix handling ORDER BY part of queries

Summary:
- new APIs
- maintain relations between connections, queries and column infos
- fix cloning queries with ORDER BY
- update and add autotests

FIXED-IN:3.2
Related: bug 392753

Test Plan:
Required: KEXI & KDb 3.2 (current master)

Test 1: Open report and query from
https://bugs.kde.org/show_bug.cgi?id=392753#c0 in design and data views.
Expected: works, no crashes

Test 2: Try these on a standard Persons and Cars test:
select id from cars order by owner;
select id from cars order by owner, model, id;
select id, model from cars order by 2, 1;

Expected: works, no crash

Reviewers: piggz

Reviewed By: piggz

Subscribers: Kexi-Devel-list

Tags: #kdb

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

M  +3-0autotests/CMakeLists.txt
A  +212  -0autotests/OrderByColumnTest.cpp [License: LGPL (v2+)]
A  +46   -0autotests/OrderByColumnTest.h [License: LGPL (v2+)]
M  +2-2src/KDbNativeStatementBuilder.cpp
M  +87   -28   src/KDbOrderByColumn.cpp
M  +40   -13   src/KDbOrderByColumn.h
M  +17   -28   src/KDbQueryColumnInfo.cpp
M  +25   -1src/KDbQueryColumnInfo.h
M  +18   -4src/KDbQuerySchema.cpp
M  +29   -1src/KDbQuerySchema_p.h

https://commits.kde.org/kdb/d1b31bd8a6fc6632f8eeab70b5e9a0f1c8630c8f

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

[systemsettings] [Bug 402930] After you use the image picker to change the background image, your chosen image appears in the picker, but disappears if you navigate away from the KCM and then go back

2019-01-06 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=402930

--- Comment #1 from David Edmundson  ---
Works here.
After apply and go through all the kauth stuff?

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

[digikam] [Bug 402938] Rename album an within album property fails when a subalbum exists

2019-01-06 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=402938

--- Comment #2 from Maik Qualmann  ---
Git commit 8a12004bf0b543b2f09b79ad12b35d0d5c73b3da by Maik Qualmann.
Committed on 06/01/2019 at 21:40.
Pushed by mqualmann into branch 'master'.

rename album only if renaming the folder was successful

M  +6-7core/libs/album/manager/albummanager_palbum.cpp

https://commits.kde.org/digikam/8a12004bf0b543b2f09b79ad12b35d0d5c73b3da

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

[kdevelop] [Bug 392336] libclang crashes on C++ project and kdevelop follows with double free or curruption

2019-01-06 Thread christian tacke
https://bugs.kde.org/show_bug.cgi?id=392336

--- Comment #6 from christian tacke  ---
Hi,

small update: it does not crash any more. I tried with KDevelop 5.2.3 on Fedora
and 5.3.0/1 AppImage on Ubuntu Xenial.

Sadly I did not manage to trace this problem to the clang calls - this would
have been a cool experience.

Best Regards,
Christian

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

[latte-dock] [Bug 402615] Dock crashes when opening contestual menu in application launcher widget in autohide panel

2019-01-06 Thread Alex Bradatan
https://bugs.kde.org/show_bug.cgi?id=402615

Alex Bradatan  changed:

   What|Removed |Added

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

--- Comment #5 from Alex Bradatan  ---
(In reply to Michail Vourlakos from comment #4)
> (In reply to Alex Bradatan from comment #3)
> > Updated to 0.8.4-1 (not present here but that is the version reported by
> > pacman) and the issue still persists on my setup. I tried with all
> > visibilities, alignments and locations. I also tested if it wasn't a problem
> > with plasma itself and it's not. While right clicking on the applet icon is
> > not a problem, even when the menu is opened, latte crashes when I right
> > click an item inside the application menu, specifically application
> > launchers (system settings firefox etc...); with files, directories and
> > logout option there aren't any problems.
> 
> I can't reproduce this, what is the crash report?

A fresh reinstall cleared what it seemes now an upgrade problem. Now the bug is
not present anymore, sorry for the trouble

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

[KEXI] [Bug 392112] Deleted physical tables still visible in project navigator

2019-01-06 Thread Jarosław Staniek
https://bugs.kde.org/show_bug.cgi?id=392112

--- Comment #6 from Jarosław Staniek  ---
Git commit 9978d76a494ca4dc6760158ef742660e2b4989cb by Jaroslaw Staniek.
Committed on 06/01/2019 at 21:14.
Pushed by staniek into branch '3.2'.

Add KDbConnection::drv_getTableNames for low level list of table names, make
tableNames() skip names with non-existing physical tables

Summary:
- KDbTestUtils: add convenience APIs for connecting and using db, support
connection options, use it in parser test
- Add KDbConnection::drv_getTableNames for low level list of table names, make
tableNames() skip names with non-existing physical tables
- This change is backward compatible since metadata without physical table is
not usable anyway.
FIXED-IN:3.2.0

+ Add autotest for handling missing physical tables

Test Plan: Run ctest

Reviewers: piggz

Tags: #kdb

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

M  +3-0autotests/CMakeLists.txt
A  +84   -0autotests/MissingTableTest.cpp [License: LGPL (v2+)]
A  +---autotests/data/missingTableTest.kexi

https://commits.kde.org/kdb/9978d76a494ca4dc6760158ef742660e2b4989cb

--- Comment #7 from Jarosław Staniek  ---
Git commit e5c3a99d939e9176da8a3d8809a6f48c8186bed8 by Jaroslaw Staniek.
Committed on 06/01/2019 at 21:14.
Pushed by staniek into branch '3.2'.

Add KDbConnection::drv_getTableNames for low level list of table names, make
tableNames() skip names with non-existing physical tables

This change is backward compatible since metadata without physical table is not
usable anyway.

FIXED-IN:3.2.0

M  +44   -2src/KDbConnection.cpp
M  +20   -1src/KDbConnection.h
M  +5-0src/KDbConnectionProxy.cpp
M  +5-0src/KDbConnectionProxy.h
M  +10   -1src/KDbDriverBehavior.h
M  +4-3src/drivers/mysql/MysqlDriver.cpp
M  +3-0src/drivers/postgresql/PostgresqlDriver.cpp
M  +2-0src/drivers/sqlite/SqliteDriver.cpp

https://commits.kde.org/kdb/e5c3a99d939e9176da8a3d8809a6f48c8186bed8

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

[systemsettings] [Bug 399716] System Settings crashes on open, "Fatal error while loading the sidebar view qml component".

2019-01-06 Thread Alex G
https://bugs.kde.org/show_bug.cgi?id=399716

--- Comment #4 from Alex G  ---
After lots of recompiling, I now have some stderr output that points to an
issue:


file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/main.qml:45:5:
Type CategoriesPage unavailable
CategoriesPage {
^
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/CategoriesPage.qml:26:1:
Type Kirigami.ScrollablePage unavailable
Kirigami.ScrollablePage {
^
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:135:18: Type
RefreshableScrollView unavailable
contentItem: RefreshableScrollView {
^
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml:28:1:
Type P.ScrollView unavailable
P.ScrollView {
^
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/private/ScrollView.qml:180:13:
"ScrollBar.interactive" is not available due to component versioning.
interactive: !Settings.tabletMode
^
"file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/main.qml:45:5:
Type CategoriesPage unavailable"
"file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/CategoriesPage.qml:26:1:
Type Kirigami.ScrollablePage unavailable"
"file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:135:18: Type
RefreshableScrollView unavailable"
"file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml:28:1:
Type P.ScrollView unavailable"
"file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/private/ScrollView.qml:180:13:
\"ScrollBar.interactive\" is not available due to component versioning."
Fatal error while loading the sidebar view qml component
KCrash: Application 'systemsettings5' crashing...

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

[digikam] [Bug 402938] Rename album an within album property fails when a subalbum exists

2019-01-06 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=402938

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
I can not reproduce the problem here. The problem can occur under Windows if
the album or a sub-album is opened by another program and is thus blocked. In
general, renaming with sub albums should work without problem.

Maik

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

[kwin] [Bug 402943] KWin crashes when closing program and switching virtual desktop at the same time

2019-01-06 Thread Vlad Zagorodniy
https://bugs.kde.org/show_bug.cgi?id=402943

Vlad Zagorodniy  changed:

   What|Removed |Added

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

--- Comment #1 from Vlad Zagorodniy  ---
Please post output of
qdbus org.kde.KWin /KWin supportInformation

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

[digikam] [Bug 402944] New: crash while looking at face tags

2019-01-06 Thread kavol
https://bugs.kde.org/show_bug.cgi?id=402944

Bug ID: 402944
   Summary: crash while looking at face tags
   Product: digikam
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: ka...@seznam.cz
  Target Milestone: ---

Application: digikam (6.0.0-beta3)
 (Compiled from sources)
Qt Version: 5.11.1
Frameworks Version: 5.52.0
Operating System: Linux 4.14.83-gentoo x86_64
Distribution (Platform): Gentoo Packages

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

I've opened the unconfirmed faces, deleted the first picture (that was a
misidentified car wheel, oh my ...) and when clicking on the next one to see
the whole photo, it crashed.

What might be of interest is that
a) on previous Digikam run, I've did a rescan for faces but that didn't finish,
Digikam crashed - with a message that DrKonqi can't be run
b) in between the runs, I've deleted and moved some photos in Dolphin

-- Backtrace:
Application: digiKam (digikam), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f64f48c3800 (LWP 5003))]

Thread 15 (Thread 0x7f6460dfe700 (LWP 5675)):
#0  0x7f64f25e68da in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f64ed3bea11 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib64/libQt5Core.so.5
#2  0x7f64ed3b6302 in QThreadPoolThread::run() () from
/usr/lib64/libQt5Core.so.5
#3  0x7f64ed3be3ff in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#4  0x7f64f25df9aa in start_thread () from /lib64/libpthread.so.0
#5  0x7f64eca3b15f in clone () from /lib64/libc.so.6

Thread 14 (Thread 0x7f64537fe700 (LWP 5674)):
#0  0x7f64f25e68da in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f64ed3bea11 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib64/libQt5Core.so.5
#2  0x7f64ed3b6302 in QThreadPoolThread::run() () from
/usr/lib64/libQt5Core.so.5
#3  0x7f64ed3be3ff in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#4  0x7f64f25df9aa in start_thread () from /lib64/libpthread.so.0
#5  0x7f64eca3b15f in clone () from /lib64/libc.so.6

Thread 13 (Thread 0x7f64521ab700 (LWP 5258)):
#0  0x7f64eca2adf3 in write () from /lib64/libc.so.6
#1  0x7f64ec9b63dd in _IO_file_write () from /lib64/libc.so.6
#2  0x7f64ec9b55e3 in ?? () from /lib64/libc.so.6
#3  0x7f64ec9b6c7e in _IO_file_xsputn () from /lib64/libc.so.6
#4  0x7f64ec984d46 in ?? () from /lib64/libc.so.6
#5  0x7f64ec9b8de4 in _IO_default_xsputn () from /lib64/libc.so.6
#6  0x7f64ec988df5 in vfprintf () from /lib64/libc.so.6
#7  0x7f64ec98a4a6 in ?? () from /lib64/libc.so.6
#8  0x7f64ec98781e in vfprintf () from /lib64/libc.so.6
#9  0x7f64eca4c4ad in __fprintf_chk () from /lib64/libc.so.6
#10 0x7f64ed3af88d in stderr_message_handler(QtMsgType, QMessageLogContext
const&, QString const&) () from /usr/lib64/libQt5Core.so.5
#11 0x7f64db3fff0c in (anonymous
namespace)::RemoteLogger::dbusLogger(QtMsgType, QMessageLogContext const&,
QString const&) () from /usr/lib64/libKF5AkonadiCore.so.5
#12 0x7f64ed3aaff7 in qt_message_print(QtMsgType, QMessageLogContext
const&, QString const&) () from /usr/lib64/libQt5Core.so.5
#13 0x7f64ed3ac7f8 in qt_message_output(QtMsgType, QMessageLogContext
const&, QString const&) () from /usr/lib64/libQt5Core.so.5
#14 0x7f64ed48ddc0 in QDebug::~QDebug() () from /usr/lib64/libQt5Core.so.5
#15 0x7f64f2d07687 in
Digikam::BdEngineBackendPrivate::debugOutputFailedQuery(QSqlQuery const&) const
() from /usr/lib64/libdigikamcore.so.6.0.0
#16 0x7f64f2d07c4d in
Digikam::BdEngineBackend::queryErrorHandling(Digikam::DbEngineSqlQuery&, int)
() from /usr/lib64/libdigikamcore.so.6.0.0
#17 0x7f64f2d07fcf in
Digikam::BdEngineBackend::exec(Digikam::DbEngineSqlQuery&) () from
/usr/lib64/libdigikamcore.so.6.0.0
#18 0x7f64f2d0894e in Digikam::BdEngineBackend::execQuery(QString const&,
QVariant const&, QVariant const&, QVariant const&, QVariant const&) () from
/usr/lib64/libdigikamcore.so.6.0.0
#19 0x7f64f2d089d7 in Digikam::BdEngineBackend::execSql(QString const&,
QVariant const&, QVariant const&, QVariant const&, QVariant const&,
QList*, QVariant*) () from /usr/lib64/libdigikamcore.so.6.0.0
#20 0x7f64f2d11ab2 in
Digikam::ThumbsDb::insertThumbnail(Digikam::ThumbsDbInfo const&, QVariant*) ()
from /usr/lib64/libdigikamcore.so.6.0.0
#21 0x7f64f2f3573a in
Digikam::ThumbnailCreator::storeInDatabase(Digikam::ThumbnailInfo const&,
Digikam::ThumbnailImage const&) const () from
/usr/lib64/libdigikamcore.so.6.0.0
#22 0x7f64f2f3766e in

[kwin] [Bug 402943] New: KWin crashes when closing program and switching virtual desktop at the same time

2019-01-06 Thread Lukas Bartl
https://bugs.kde.org/show_bug.cgi?id=402943

Bug ID: 402943
   Summary: KWin crashes when closing program and switching
virtual desktop at the same time
   Product: kwin
   Version: 5.14.4
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: lukiba...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.14.4)

Qt Version: 5.12.0
Frameworks Version: 5.53.0
Operating System: Linux 4.20.0-arch1-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
I closed "Keybase" und at the same time switched the virtual desktop. KWin
crashed and restarted. I can reproduce this issue sometimes.

The crash can be reproduced sometimes.

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

Thread 6 (Thread 0x7faeeebde700 (LWP 5667)):
#0  0x7faf116d6afc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7faf123d328c in  () at /usr/lib/libQt5Script.so.5
#2  0x7faf123d32a9 in  () at /usr/lib/libQt5Script.so.5
#3  0x7faf116d0a9d in start_thread () at /usr/lib/libpthread.so.0
#4  0x7faf13f56b23 in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7faeefcb4700 (LWP 5664)):
#0  0x7faf116d6afc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7faf00367c24 in  () at /usr/lib/dri/i965_dri.so
#2  0x7faf00367948 in  () at /usr/lib/dri/i965_dri.so
#3  0x7faf116d0a9d in start_thread () at /usr/lib/libpthread.so.0
#4  0x7faf13f56b23 in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7faf02c5f700 (LWP 5662)):
#0  0x7faf13f4bd16 in ppoll () at /usr/lib/libc.so.6
#1  0x7faf12af746b in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7faf12af894b in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7faf12aa458c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7faf128e85c9 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7faf10e94b89 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7faf128e99cc in  () at /usr/lib/libQt5Core.so.5
#7  0x7faf116d0a9d in start_thread () at /usr/lib/libpthread.so.0
#8  0x7faf13f56b23 in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7faf08e54700 (LWP 5654)):
#0  0x7faf13f4bd16 in ppoll () at /usr/lib/libc.so.6
#1  0x7faf12af746b in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7faf12af894b in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7faf12aa458c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7faf128e85c9 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7faf10901ba6 in  () at /usr/lib/libQt5DBus.so.5
#6  0x7faf128e99cc in  () at /usr/lib/libQt5Core.so.5
#7  0x7faf116d0a9d in start_thread () at /usr/lib/libpthread.so.0
#8  0x7faf13f56b23 in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7faf0a3cf700 (LWP 5653)):
#0  0x7faf13f4bc21 in poll () at /usr/lib/libc.so.6
#1  0x7faf1280d630 in  () at /usr/lib/libxcb.so.1
#2  0x7faf1280f2db in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#3  0x7faf0a8ee96b in  () at /usr/lib/libQt5XcbQpa.so.5
#4  0x7faf128e99cc in  () at /usr/lib/libQt5Core.so.5
#5  0x7faf116d0a9d in start_thread () at /usr/lib/libpthread.so.0
#6  0x7faf13f56b23 in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7faf0ad2a840 (LWP 5650)):
[KCrash Handler]
#6  0x7faf13e92d7f in raise () at /usr/lib/libc.so.6
#7  0x7faf13e7d672 in abort () at /usr/lib/libc.so.6
#8  0x7faf128af7fc in  () at /usr/lib/libQt5Core.so.5
#9  0x7faf1264eeda in KWin::WindowQuad::makeSubQuad(double, double, double,
double) const () at /usr/lib/libkwineffects.so.11
#10 0x7faf0807553d in  () at
/usr/lib/qt/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so
#11 0x7faf08075698 in  () at
/usr/lib/qt/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so
#12 0x7faf0807f223 in  () at
/usr/lib/qt/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so
#13 0x7faf0807f369 in  () at
/usr/lib/qt/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so
#14 0x7faf13cd756c in
KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion,
KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5
#15 0x7faf125e5266 in  () at /usr/lib/libkwin4_effect_builtins.so.1
#16 0x7faf13cd7504 in
KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion,
KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5
#17 0x7faf1255261a in  () at /usr/lib/libkwin4_effect_builtins.so.1

[Falkon] [Bug 402936] Usernames and passwords are stored for autofill as plain text in sqlite database which is the default option

2019-01-06 Thread David Rosca
https://bugs.kde.org/show_bug.cgi?id=402936

--- Comment #3 from David Rosca  ---
(In reply to Prasad Murthy from comment #2)
> We could do what firefox does or we could use for example SQLCipher to
> encrypt the sqlite database and ask the user for the master password every
> session.

That's effectively the same thing that encrypted database backend already does
though.

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

[Discover] [Bug 402942] New: no aktulalisierun

2019-01-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=402942

Bug ID: 402942
   Summary: no aktulalisierun
   Product: Discover
   Version: 5.9.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: juerg.ur...@gmx.ch
  Target Milestone: ---

SUMMARY


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.

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

2019-01-06 Thread Darkspirit
https://bugs.kde.org/show_bug.cgi?id=344433

Darkspirit  changed:

   What|Removed |Added

 CC||j...@ikenmeyer.eu

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

[latte-dock] [Bug 402615] Dock crashes when opening contestual menu in application launcher widget in autohide panel

2019-01-06 Thread Michail Vourlakos
https://bugs.kde.org/show_bug.cgi?id=402615

--- Comment #4 from Michail Vourlakos  ---
(In reply to Alex Bradatan from comment #3)
> Updated to 0.8.4-1 (not present here but that is the version reported by
> pacman) and the issue still persists on my setup. I tried with all
> visibilities, alignments and locations. I also tested if it wasn't a problem
> with plasma itself and it's not. While right clicking on the applet icon is
> not a problem, even when the menu is opened, latte crashes when I right
> click an item inside the application menu, specifically application
> launchers (system settings firefox etc...); with files, directories and
> logout option there aren't any problems.

I can't reproduce this, what is the crash report?

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

[kate] [Bug 402751] Underscores disappear in Kate part

2019-01-06 Thread Victor Porton
https://bugs.kde.org/show_bug.cgi?id=402751

--- Comment #3 from Victor Porton  ---
$ ldd /usr/bin/kate
...
libQt5Core.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
(0x7f4e2000)
...

$ dpkg -s libqt5core5a
...
Version: 5.11.1+dfsg-7ubuntu1
...

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

[latte-dock] [Bug 402615] Dock crashes when opening contestual menu in application launcher widget in autohide panel

2019-01-06 Thread Alex Bradatan
https://bugs.kde.org/show_bug.cgi?id=402615

--- Comment #3 from Alex Bradatan  ---
Updated to 0.8.4-1 (not present here but that is the version reported by
pacman) and the issue still persists on my setup. I tried with all
visibilities, alignments and locations. I also tested if it wasn't a problem
with plasma itself and it's not. While right clicking on the applet icon is not
a problem, even when the menu is opened, latte crashes when I right click an
item inside the application menu, specifically application launchers (system
settings firefox etc...); with files, directories and logout option there
aren't any problems.

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

[digikam] [Bug 402940] no thumbnails with windows client using network share

2019-01-06 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=402940

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
DigiKam does not support a network path. The network collection must be mounted
locally or connected to a drive letter.

Maik

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

[kate] [Bug 402751] Underscores disappear in Kate part

2019-01-06 Thread Dominik Haumann
https://bugs.kde.org/show_bug.cgi?id=402751

--- Comment #2 from Dominik Haumann  ---
Which version of Qt do you use?

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

2019-01-06 Thread Steffen Coenen
https://bugs.kde.org/show_bug.cgi?id=397850

Steffen Coenen  changed:

   What|Removed |Added

 CC||tarding...@googlemail.com

--- Comment #2 from Steffen Coenen  ---
This is probably a duplicate of https://bugs.kde.org/show_bug.cgi?id=344433

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

[okular] [Bug 402939] Annotation workflow is completely broken

2019-01-06 Thread DimanNe
https://bugs.kde.org/show_bug.cgi?id=402939

--- Comment #2 from DimanNe  ---
Yes, I can.

Do you know where exactly in code I can start to look?

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

[KEXI] [Bug 402923] Segmentation fault in Kexi

2019-01-06 Thread Jarosław Staniek
https://bugs.kde.org/show_bug.cgi?id=402923

--- Comment #2 from Jarosław Staniek  ---
Created attachment 117310
  --> https://bugs.kde.org/attachment.cgi?id=117310=edit
Types

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

[okular] [Bug 402939] Annotation workflow is completely broken

2019-01-06 Thread Oliver Sander
https://bugs.kde.org/show_bug.cgi?id=402939

Oliver Sander  changed:

   What|Removed |Added

 CC||oliver.san...@tu-dresden.de

--- Comment #1 from Oliver Sander  ---
> What is wrong with Okular?

Not enough manpower.  Can you code?

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

[KEXI] [Bug 402923] Segmentation fault in Kexi

2019-01-06 Thread Jarosław Staniek
https://bugs.kde.org/show_bug.cgi?id=402923

--- Comment #1 from Jarosław Staniek  ---
Hello Ivan, what widget type in the Form designer have you double clicked?
Thanks.

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

[KEXI] [Bug 402923] Segmentation fault in Kexi

2019-01-06 Thread Jarosław Staniek
https://bugs.kde.org/show_bug.cgi?id=402923

Jarosław Staniek  changed:

   What|Removed |Added

   Platform|unspecified |Archlinux Packages
 CC||stan...@kde.org
  Component|General |Forms

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

[Falkon] [Bug 402936] Usernames and passwords are stored for autofill as plain text in sqlite database which is the default option

2019-01-06 Thread Prasad Murthy
https://bugs.kde.org/show_bug.cgi?id=402936

--- Comment #2 from Prasad Murthy  ---
We could do what firefox does or we could use for example SQLCipher to encrypt
the sqlite database and ask the user for the master password every session.

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

[kstars] [Bug 402941] KStars crashes when pressing arrow key in a specific situation

2019-01-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=402941

ld_second...@outlook.com changed:

   What|Removed |Added

 CC||ld_second...@outlook.com

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

[kstars] [Bug 402941] New: KStars crashes when pressing arrow key in a specific situation

2019-01-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=402941

Bug ID: 402941
   Summary: KStars crashes when pressing arrow key in a specific
situation
   Product: kstars
   Version: 2.9.8
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: ld_second...@outlook.com
  Target Milestone: ---

SUMMARY
KStars crashes when pressing arrow key in a specific situation

STEPS TO REPRODUCE
1. Tools > "What's Interesting"
2. Click "Satellites"
3. Press any arrow key

OBSERVED RESULT
KStars crashes

EXPECTED RESULT
-

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 18.10
KDE Plasma Version: 5.13.5
KDE Frameworks Version: 5.50.0
Qt Version: 5.11.1

ADDITIONAL INFORMATION
Maybe this crash is related to the fact that the "Satellites" section has "No
Items to display". It doesn't happen with other sections.

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

[digikam] [Bug 402940] New: no thumbnails with windows client using network share

2019-01-06 Thread Christoph
https://bugs.kde.org/show_bug.cgi?id=402940

Bug ID: 402940
   Summary: no thumbnails with windows client using network share
   Product: digikam
   Version: 6.0.0
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Database-Thumbs
  Assignee: digikam-bugs-n...@kde.org
  Reporter: cca...@online.de
  Target Milestone: ---

SUMMARY
When using windows client with pictures in a network share the thumbnails for
the faces are not available.


STEPS TO REPRODUCE
1. Fresh Windows Client Install of 6.0.0 beta3
2. Edit AlbumRoot as Network Share UNC path (//192.168.178/100/Pictures/Test/) 
3. Select DB SQLlite or MYSQL
4. After initial scan, run the face recognition. 

OBSERVED RESULT
Faces are recognized but thumbnails are not generated. I checked the MYSQL DB.
No dataset is inserted in the table CustomIdentifiers. GUI shows the thumbnail
of the whole picture. These thumbnails are available and stored in the
FilePaths table.

EXPECTED RESULT
Thumbnails are available for the recognized faces.

SOFTWARE/OS VERSIONS
Windows: 10

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

[okular] [Bug 402939] New: Annotation workflow is completely broken

2019-01-06 Thread DimanNe
https://bugs.kde.org/show_bug.cgi?id=402939

Bug ID: 402939
   Summary: Annotation workflow is completely broken
   Product: okular
   Version: 1.4.3
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: PDF backend
  Assignee: okular-de...@kde.org
  Reporter: dima...@gmail.com
  Target Milestone: ---

I wanted to add my signature (image, not cryptographic one) into a pdf
document. So I decided to use the Annotation feature of Okular, found that
Stamp was what I looking for.

Here was the first problem - it is completely impossible (from the given
interface) to understand how I am supposed to add my own image in the list of
available stamps.

Well, after some googling I found your help (which is wrong, actually):
https://docs.kde.org/trunk5/en/kdegraphics/okular/configannotations.html
Using Custom Stamps
* Create the icon you want to use for your own stamp and save it in any
graphics format supported by Okular
* Click the Add button, select type Stamp and enter a name for your stamp.
* Enter the full path to your custom icon into the dropdown box in the Stamp
Symbol group

My path was "/home/dimanne/Downloads/DimanNeSignature.png" - it did not work.
After more googling I found out that I should have somehow understood that the
path must be in lowercase - https://superuser.com/a/1325085/981679
At least, you should have written it in the help, instead of making people
debug Okular with strace.

Well, after renaming to lowercase I managed to get it on my PDF (it is still
ugly since you downscale it drastically and it looks distorted, but anyway, it
was passable).

Finally, I have went all the path only to know that the signature can not be
saved in resulting (annotated) PDF -
https://bugs.kde.org/show_bug.cgi?id=383651


What is wrong with Okular?

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

[latte-dock] [Bug 402934] Latte dock autostart doesn't work

2019-01-06 Thread Tomsk
https://bugs.kde.org/show_bug.cgi?id=402934

--- Comment #9 from Tomsk  ---
Oh that was fast hotfix, thank you very much! :)

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

[digikam] [Bug 402938] New: Rename album an within album property fails when a subalbum exists

2019-01-06 Thread Loukournan29
https://bugs.kde.org/show_bug.cgi?id=402938

Bug ID: 402938
   Summary: Rename album an within album property fails when a
subalbum exists
   Product: digikam
   Version: 5.9.0
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Albums-TreeView
  Assignee: digikam-bugs-n...@kde.org
  Reporter: paul.her...@laposte.net
  Target Milestone: ---

SUMMARY
Rename album an within album property fails when a subalbum exists

STEPS TO REPRODUCE
1. Edit the properties of an album containing a subalbum
2. Modify the album name, then click on Ok

OBSERVED RESULT
1. A warn dialog indicates that the renaming as failed, and close the dialog
box
2. The photographs are not available any more within Digikam (switch albums to
check), and the album is not renamed.
3. The photographs files are still available in the file manager, and the
directory is not renamed
4. Rename again the album, but with the rename option. The warning is displayed
again. The album is renamed, but the corresponding directory. The photograph
are not available.
5. Rename again the album to the initial name. The renaming succeed, and the
photographs are available again.

Note : The album renaming with rename option has quite the same issue.



EXPECTED RESULT


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

ADDITIONAL INFORMATION

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

[krita] [Bug 402535] Krita memory leaks or endless loop when using freehand brush with perspective assistant

2019-01-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=402535

--- Comment #8 from genosim...@gmail.com ---
And i'm stuck here

https://imgur.com/a/6zEhGLa

I traced the problem to this function:
KisToolFreehandHelper::paint(KisPaintInformation&), which under some
circumstances calls paintLine(const KisPaintInformation& from, const
KisPaintInformation& to) on line 595 where to.pos() is {NaN, NaN}. This in
turn, causes all the other above mentioned symptoms.

I also found more reliable way to trigger this one. Create a "box" from
perspective assistants as in the video above, then start drawing with brush
just outside of the box. This triggers the bug instantly almost always during
my testing 

All of this was done with v4.1.7 tag from git.

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

[Falkon] [Bug 402936] Usernames and passwords are stored for autofill as plain text in sqlite database which is the default option

2019-01-06 Thread David Rosca
https://bugs.kde.org/show_bug.cgi?id=402936

David Rosca  changed:

   What|Removed |Added

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

--- Comment #1 from David Rosca  ---
KWallet/GnomeKeyring are not available on all systems, and those are only
"secure" options that could work without any user interaction.
Everything else requires some user interaction, like creating password (as what
encrypted database backend does).

You are correct, the passwords are stored in plain-text by default. Alternative
would be to generate some key (which will be stored in the profile directory)
and encrypt the password with it, but I don't really think this is any
different (both are easily accessible for anyone that have access to your local
files).

Also in case of KWallet, once a wallet is opened (usually automatically with
login) any application have access to all stored passwords, so it's not really
secure either.

I don't really see any solution to this, there is no way to have secure storage
without prompting user for password every time the browser is started, and
that's not something that most users will be willing to do.
So the default won't be changed.

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

  1   2   3   >