[plasmashell] [Bug 405547] New: Kubuntu new install, common crash

2019-03-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=405547

Bug ID: 405547
   Summary: Kubuntu new install, common crash
   Product: plasmashell
   Version: 5.12.7
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: dabbs.d...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.12.7)

Qt Version: 5.9.5
Frameworks Version: 5.44.0
Operating System: Linux 4.18.0-16-generic x86_64
Distribution: Ubuntu 18.04.2 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Watching online videos, second time this has happened, I think the h264 codec
or a similar codec is the only common theme I can see

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

Thread 32 (Thread 0x7f5e3b5ef700 (LWP 5226)):
#0  0x7f5f8a4b59f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55753424d250) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f5f8a4b59f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55753424d200, cond=0x55753424d228) at pthread_cond_wait.c:502
#2  0x7f5f8a4b59f3 in __pthread_cond_wait (cond=0x55753424d228,
mutex=0x55753424d200) at pthread_cond_wait.c:655
#3  0x7f5f8b34559b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f5f8f1166a8 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f5f8f116b0a in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7f5f8b34416d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f5f8a4af6db in start_thread (arg=0x7f5e3b5ef700) at
pthread_create.c:463
#8  0x7f5f8ac3188f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 31 (Thread 0x7f5e51467700 (LWP 4936)):
#0  0x7f5f8a4b59f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x557534719ac4) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f5f8a4b59f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x557534719a70, cond=0x557534719a98) at pthread_cond_wait.c:502
#2  0x7f5f8a4b59f3 in __pthread_cond_wait (cond=0x557534719a98,
mutex=0x557534719a70) at pthread_cond_wait.c:655
#3  0x7f5f8b34559b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f5f8f1166a8 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f5f8f116b0a in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7f5f8b34416d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f5f8a4af6db in start_thread (arg=0x7f5e51467700) at
pthread_create.c:463
#8  0x7f5f8ac3188f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 30 (Thread 0x7f5e51ffb700 (LWP 4038)):
#0  0x7f5f8a4b59f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x557533f4a824) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f5f8a4b59f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x557533f4a7d0, cond=0x557533f4a7f8) at pthread_cond_wait.c:502
#2  0x7f5f8a4b59f3 in __pthread_cond_wait (cond=0x557533f4a7f8,
mutex=0x557533f4a7d0) at pthread_cond_wait.c:655
#3  0x7f5f8b34559b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f5ecf96bad5 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f5ecf96fba8 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7f5ecf96ac8d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7f5ecf96fc02 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7f5ecf96ac8d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7f5ecf96fc02 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#10 0x7f5ecf96ac8d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#11 0x7f5ecf96fc02 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#12 0x7f5ecf96ac8d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#13 0x7f5ecf96fc02 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#14 0x7f5ecf96ac8d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#15 0x7f5ecf96fc02 in  () at
/usr/lib/x86_64-linux-gnu/li

[dolphin] [Bug 157819] Missing back and forward history

2019-03-16 Thread David Hallas
https://bugs.kde.org/show_bug.cgi?id=157819

David Hallas  changed:

   What|Removed |Added

 CC||da...@davidhallas.dk
 Status|CONFIRMED   |ASSIGNED
   Assignee|dolphin-bugs-n...@kde.org   |da...@davidhallas.dk

--- Comment #14 from David Hallas  ---
I have a WIP patch cooking here:

https://phabricator.kde.org/D19311

Feedback is _very_ welcome ;)

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

[plasma-nm] [Bug 405501] plasma-nm is not compatible with NetworkManager 1.16's native WireGuard support

2019-03-16 Thread K900
https://bugs.kde.org/show_bug.cgi?id=405501

--- Comment #2 from K900  ---
Yeah, that's what I've been doing. Also, it turns out the autoconnect setting
is actually enabled by nmcli by default for some reason, so that one isn't
plasma-nm's fault. Anyway, I might just start hacking on it when I get the time
(but please feel free to snipe me)

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

[okular] [Bug 405542] freehand line changes to panning after 1 stroke

2019-03-16 Thread Oliver Sander
https://bugs.kde.org/show_bug.cgi?id=405542

Oliver Sander  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |NOT A BUG
 CC||oliver.san...@tu-dresden.de

--- Comment #2 from Oliver Sander  ---
You have to select "freehand line" by *double*-clicking.  If you do that it
stays selected permanently.

I agree that UI-wise this is less than optimal.  Anyone for replacing double
clicks by single clicks here?

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

[Spectacle] [Bug 401259] Receiving desktop notification in telegram while taking screenshot crashes user.

2019-03-16 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=401259

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

[kmymoney] [Bug 404352] Avast reports a virus

2019-03-16 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=404352

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

[kwin] [Bug 391214] kwin crash

2019-03-16 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=391214

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

[kio-extras] [Bug 404924] EXR Previews over 1MB are not thumbnailed

2019-03-16 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=404924

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

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

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

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

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

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

[latte-dock] [Bug 404268] Cannot launch latte-dock configuration screen with mouse right-click

2019-03-16 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=404268

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.

[Discover] [Bug 404917] Discover has been crashing on launch.

2019-03-16 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=404917

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

[systemsettings] [Bug 404867] System settings crash on launch feedback page

2019-03-16 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=404867

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

[Spectacle] [Bug 396148] X-DBUS-StartupType should not be 'Multi' in desktop file

2019-03-16 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=396148

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

[karbon] [Bug 405546] New: Saving a document crashs the application

2019-03-16 Thread Ali
https://bugs.kde.org/show_bug.cgi?id=405546

Bug ID: 405546
   Summary: Saving a document crashs the application
   Product: karbon
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: ja...@gmx.net
  Reporter: overman.supermund...@gmail.com
  Target Milestone: ---

Application: karbon (3.0.1)

Qt Version: 5.9.5
Frameworks Version: 5.44.0
Operating System: Linux 4.18.0-16-generic x86_64
Distribution: Ubuntu 18.04.2 LTS

-- Information about the crash:
- What I was doing when the application crashed:
tried to save a document 
wither the document is blank (new) or had any drawing, it will always crash

The crash can be reproduced every time.

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

Thread 4 (Thread 0x7f4bba277700 (LWP 22556)):
#0  0x7f4bea79d9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x5601e0ef6e98) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f4bea79d9f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x5601e0ef6e48, cond=0x5601e0ef6e70) at pthread_cond_wait.c:502
#2  0x7f4bea79d9f3 in __pthread_cond_wait (cond=0x5601e0ef6e70,
mutex=0x5601e0ef6e48) at pthread_cond_wait.c:655
#3  0x7f4bbfac323b in  () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
#4  0x7f4bbfac2f67 in  () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
#5  0x7f4bea7976db in start_thread (arg=0x7f4bba277700) at
pthread_create.c:463
#6  0x7f4bf19cf88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f4bd3de3700 (LWP 22554)):
#0  0x7f4bf19c2bf9 in __GI___poll (fds=0x7f4bcc012eb0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f4be929e539 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f4be929e64c in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f4bf042290b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f4bf03c79ea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f4bf01e622a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f4beade5d45 in  () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f4bf01eb16d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f4bea7976db in start_thread (arg=0x7f4bd3de3700) at
pthread_create.c:463
#9  0x7f4bf19cf88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f4bdae9f700 (LWP 22553)):
#0  0x7f4bf19c2bf9 in __GI___poll (fds=0x7f4bdae9eca8, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f4be294b747 in  () at /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f4be294d36a in xcb_wait_for_event () at
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f4bdd7d52a9 in  () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f4bf01eb16d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f4bea7976db in start_thread (arg=0x7f4bdae9f700) at
pthread_create.c:463
#6  0x7f4bf19cf88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f4bf2040c80 (LWP 22552)):
[KCrash Handler]
#6  0x7f4bee019cc8 in KoStore::pos() const () at
/usr/lib/x86_64-linux-gnu/libkostore.so.15
#7  0x7f4bc29afbac in  () at /usr/lib/x86_64-linux-gnu/libfreeimage.so.3
#8  0x7f4bc29a40ed in FreeImage_GetFileTypeFromHandle () at
/usr/lib/x86_64-linux-gnu/libfreeimage.so.3
#9  0x7f4bc2c2d1de in FreeImageHandler::GetFIF(QIODevice*, QByteArray
const&) () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/imageformats/libxfreeimage.so
#10 0x7f4bc2c2e8ec in FreeimageQt5Plugin::capabilities(QIODevice*,
QByteArray const&) const () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/imageformats/libxfreeimage.so
#11 0x7f4beb404a4e in  () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#12 0x7f4beb404d2c in  () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#13 0x7f4beb4051b8 in QImageWriter::canWrite() const () at
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#14 0x7f4beb405377 in QImageWriter::write(QImage const&) () at
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#15 0x7f4beb3d8c08 in QImageData::doImageIO(QImage const*, QImageWriter*,
int) const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#16 0x7f4beb3d8e19 in QImage::save(QIODevice*, char const*, int) const ()
at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#17 0x7f4bf1605d64 in KoDocument::saveOasisPreview(KoStore*, KoXmlWriter*)
() at /usr/lib/x86_64-linux-gnu/libkomain.so.15
#18 0x7f4bf1606250 in KoDocument::saveNativeFormatODF(KoStore*, QByteArray
const&) () at /usr/lib/x86_64-linux-

[kmail2] [Bug 405545] New: Erase mail

2019-03-16 Thread Cougar
https://bugs.kde.org/show_bug.cgi?id=405545

Bug ID: 405545
   Summary: Erase mail
   Product: kmail2
   Version: 5.7.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: cougar1...@libero.it
  Target Milestone: ---

When I erase the last email, the lower part (where I see the content of email)
should be empty and not display the text of email I have erase .

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: kubuntu 18.04
KDE Plasma Version: 5.12.7
KDE Frameworks Version: 5.47.0
Qt Version: 5.9.5

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

[ksudoku] [Bug 405422] ksudoku live-git (commit 09814312d) small-game generation fails with "Unable to generate a puzzle of the chosen variant"

2019-03-16 Thread Ian Wadham
https://bugs.kde.org/show_bug.cgi?id=405422

Ian Wadham  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
   Severity|major   |normal
 Status|REPORTED|RESOLVED
   Priority|VHI |NOR

--- Comment #5 from Ian Wadham  ---
Thanks very much, Albert, for taking the time to check up on this.

It looks as if the ball is back in your court, Duncan. Maybe something has gone
wrong with your build and compile of KDE software. Looks like you have the same
version of Qt5 as current KDE development, but do you have the right KF5?

Albert is an authority on all this. He is a leading member of the
kde-games-devel mailing list and also a KDE Release Team member and there is a
release of KDE Applications 19.04 (including KSudoku) coming up on 18th April.
The branch that is due for release is here:
  https://cgit.kde.org/ksudoku.git/tree//?h=Applications%2F19.04

Instructions for cloning the repository are at
https://kde.org/applications/games/ksudoku/development.

If anything at all is wrong and there is no problem in your environment, we
would want to know. Please feel free to re-open this bug report if necessary.

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

[kleopatra] [Bug 405544] New: kleopatra crashes when clicking "gnupg system"

2019-03-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=405544

Bug ID: 405544
   Summary: kleopatra crashes when clicking "gnupg system"
   Product: kleopatra
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: aheine...@gnupg.org
  Reporter: otrapersonab...@riseup.net
CC: kdepim-b...@kde.org, m...@kde.org
  Target Milestone: ---

Application: kleopatra (3.1.3)

Qt Version: 5.11.3
Frameworks Version: 5.55.0
Operating System: Linux 4.20.15-200.fc29.x86_64 x86_64
Distribution: "Fedora release 29 (Twenty Nine)"

-- Information about the crash:
as the title mentions, kleopatra crashes when clicking "gnupg system" if widget
style is set to kvantum
it happened with (kvantum) Arc and Breeze themes

crashes stopped when widget style was switched back to "Breeze"

The crash can be reproduced every time.

-- Backtrace:
Application: Kleopatra (kleopatra), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5d78e43940 (LWP 9416))]

Thread 4 (Thread 0x7f5d68a46700 (LWP 9441)):
#0  0x7f5d7e69373c in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f5d7d2c5923 in QWaitCondition::wait(QMutex*, unsigned long) () from
/lib64/libQt5Core.so.5
#2  0x563c5879216e in ?? ()
#3  0x7f5d7d2c52fb in ?? () from /lib64/libQt5Core.so.5
#4  0x7f5d7e68d58e in start_thread () from /lib64/libpthread.so.0
#5  0x7f5d7ce036a3 in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f5d6a468700 (LWP 9418)):
#0  0x7f5d7e696df4 in read () from /lib64/libpthread.so.0
#1  0x7f5d79996e90 in ?? () from /lib64/libglib-2.0.so.0
#2  0x7f5d7994fe9b in g_main_context_check () from /lib64/libglib-2.0.so.0
#3  0x7f5d79950350 in ?? () from /lib64/libglib-2.0.so.0
#4  0x7f5d799504d0 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#5  0x7f5d7d4a55ab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#6  0x7f5d7d453e0b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#7  0x7f5d7d2bbe86 in QThread::exec() () from /lib64/libQt5Core.so.5
#8  0x7f5d7e550f89 in ?? () from /lib64/libQt5DBus.so.5
#9  0x7f5d7d2c52fb in ?? () from /lib64/libQt5Core.so.5
#10 0x7f5d7e68d58e in start_thread () from /lib64/libpthread.so.0
#11 0x7f5d7ce036a3 in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f5d6bb80700 (LWP 9417)):
#0  0x7f5d7cdf8421 in poll () from /lib64/libc.so.6
#1  0x7f5d7ba8939f in ?? () from /lib64/libxcb.so.1
#2  0x7f5d7ba8b01a in xcb_wait_for_event () from /lib64/libxcb.so.1
#3  0x7f5d6bd31bf9 in ?? () from /lib64/libQt5XcbQpa.so.5
#4  0x7f5d7d2c52fb in ?? () from /lib64/libQt5Core.so.5
#5  0x7f5d7e68d58e in start_thread () from /lib64/libpthread.so.0
#6  0x7f5d7ce036a3 in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f5d78e43940 (LWP 9416)):
[KCrash Handler]
#6  0x7f5d6ac57e1f in Kvantum::Style::styleHint(QStyle::StyleHint,
QStyleOption const*, QWidget const*, QStyleHintReturn*) const () from
/usr/lib64/qt5/plugins/styles/libkvantum.so
#7  0x7f5d7ef4ac15 in KDHorizontalLine::paintEvent(QPaintEvent*) () from
/lib64/libKF5Libkleo.so.5
#8  0x7f5d7dd85378 in QWidget::event(QEvent*) () from
/lib64/libQt5Widgets.so.5
#9  0x7f5d7de29ac2 in QFrame::event(QEvent*) () from
/lib64/libQt5Widgets.so.5
#10 0x7f5d7dd46285 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#11 0x7f5d7dd4d9a0 in QApplication::notify(QObject*, QEvent*) () from
/lib64/libQt5Widgets.so.5
#12 0x7f5d7d454ec6 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#13 0x7f5d7dd7de9e in QWidgetPrivate::sendPaintEvent(QRegion const&) ()
from /lib64/libQt5Widgets.so.5
#14 0x7f5d7dd7e757 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion
const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from
/lib64/libQt5Widgets.so.5
#15 0x7f5d7dd7f351 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*,
QList const&, int, QRegion const&, QPoint const&, int, QPainter*,
QWidgetBackingStore*) () from /lib64/libQt5Widgets.so.5
#16 0x7f5d7dd7f240 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*,
QList const&, int, QRegion const&, QPoint const&, int, QPainter*,
QWidgetBackingStore*) () from /lib64/libQt5Widgets.so.5
#17 0x7f5d7dd7f240 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*,
QList const&, int, QRegion const&, QPoint const&, int, QPainter*,
QWidgetBackingStore*) () from /lib64/libQt5Widgets.so.5
#18 0x7f5d7dd7f240 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*,
QList const&, int, QRegion const&, QPoint const&, int, QPainter*,
QWidgetBackingStore*) () from /lib64/libQt5Widgets.so.5
#19 0x7f5d

[okular] [Bug 405543] New: can't open drag-and-dropped files

2019-03-16 Thread Mikel Pérez
https://bugs.kde.org/show_bug.cgi?id=405543

Bug ID: 405543
   Summary: can't open drag-and-dropped files
   Product: okular
   Version: unspecified
  Platform: Flatpak
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: i...@mikelpr.com
  Target Milestone: ---

SUMMARY
can't open files dnd'd into the window with the flatpak


STEPS TO REPRODUCE
1. drag a file from dolphin into okular

OBSERVED RESULT
it can't find the file (because it's sandboxed)

EXPECTED RESULT
being able to open the file

SOFTWARE/OS VERSIONS
Linux: Fedora 29 
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.55.0
Qt Version: 5.11.3

ADDITIONAL INFORMATION
opening from File->Open does work (uses a portal)

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

[okular] [Bug 405542] freehand line changes to panning after 1 stroke

2019-03-16 Thread Mikel Pérez
https://bugs.kde.org/show_bug.cgi?id=405542

--- Comment #1 from Mikel Pérez  ---
also present on okular 1.7.70 flatpak

(I guess it has always been this way. I think it's terrible behaviour - many
people don't sign with 1 stroke)

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

[kdeconnect] [Bug 398936] Spotify and Kde connect notifications

2019-03-16 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=398936

Nicolas Fella  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED
 CC||nicolas.fe...@gmx.de

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

[kdeconnect] [Bug 401843] Notification on lockscreen shows artist "Unbekannt" (Unknown) when playing a media

2019-03-16 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=401843

Nicolas Fella  changed:

   What|Removed |Added

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

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

[okular] [Bug 405542] New: freehand line changes to panning after 1 stroke

2019-03-16 Thread Mikel Pérez
https://bugs.kde.org/show_bug.cgi?id=405542

Bug ID: 405542
   Summary: freehand line changes to panning after 1 stroke
   Product: okular
   Version: 1.6.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: PDF backend
  Assignee: okular-de...@kde.org
  Reporter: i...@mikelpr.com
  Target Milestone: ---

STEPS TO REPRODUCE
1. open the reviews/annotations panel
2. select freehand line
3. draw something

OBSERVED RESULT
after one stroke, it switches back to moving/panning the document

EXPECTED RESULT
stay in draw mode

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 29
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.55.0
Qt Version: 5.11.3

ADDITIONAL INFORMATION
my signature requires more than one stroke and this is a deal breaker

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

[kate] [Bug 405415] [Kate] [Feature request] Please provide an APT install package which does not depends on KDE, similar to kdiff3

2019-03-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=405415

--- Comment #3 from kke...@gmail.com ---
Thanks. I generally use Xbuntu, (ubuntu with xfce4 only), which by default does
not have qt stuffs and KDE. So it requires 250-300MB disk for Kate
installation.

I just gave a try on a clean Debian 9 VM. Installation of kdiff3 requires
311MB, while kdiff3-qt requires 31MB. I think kdiff3-qt only includes the
minimal QT stuffs instead of whole QT.

Thanks, anyway. I don't think I will switch to KDE from xfce since xfce runs
fast. I will just use Geany instead of Kate as a workaround.

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

[plasma-nm] [Bug 405501] plasma-nm is not compatible with NetworkManager 1.16's native WireGuard support

2019-03-16 Thread Bruce Anderson
https://bugs.kde.org/show_bug.cgi?id=405501

Bruce Anderson  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Bruce Anderson  ---
This is going to take a while to fix because the configuration data for
WireGuard connections has totally changed starting in the new version of
NetworkManager. As a sidenote it appears that nm-connection-editor has not been
updated to handle the change either.

In the meantime to make it so the WireGuard connections do not automatically
start on login you can issue:
  nmcli connection modify  connection.autoconnect no

Then to start and stop the connection unfortunately it appears you will need to
use:
  nmcli connection  
because at least for me, the WireGuard connections don't show up on the popup
menu to be connected using the plasma-nm interface.

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

[kaffeine] [Bug 405278] [feature request] EPG from xmltv

2019-03-16 Thread higuita
https://bugs.kde.org/show_bug.cgi?id=405278

--- Comment #19 from higuita  ---
> That would be way harder. The code is basically selecting between a list
> of all channels or a list with EPG channels, each stored on different
> data structures.

ok, thanks, i understand... this isn't critical, it's just a nice to have thing
:)

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

[systemsettings] [Bug 386748] Some icons are missing in tooltips

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=386748

--- Comment #16 from Nate Graham  ---
I'll give it a try tomorrow or the next day if I can rustle up the time...

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

[kmymoney] [Bug 405383] Add python3 support for weboob plugin

2019-03-16 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=405383

--- Comment #2 from Jack  ---
No, it is not a joke.  Did you even bother to search the term, or check the KMM
cmake options?

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

[plasma-integration] [Bug 405331] KDE Neon Dev: Password not centered in Login Screen

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=405331

Nate Graham  changed:

   What|Removed |Added

 CC||sit...@kde.org

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

[plasma-integration] [Bug 405331] KDE Neon Dev: Password not centered in Login Screen

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=405331

Nate Graham  changed:

   What|Removed |Added

   Target Milestone|1.0 |---
Product|plasmashell |plasma-integration
  Component|Look & Feel package |general

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

[plasmashell] [Bug 405331] KDE Neon Dev: Password not centered in Login Screen

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=405331

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #2 from Nate Graham  ---
Yeah.

If you look closely, the bullets were never vertically centered before, but now
it's more noticeable as a side effect of fixing the bug that made the password
field jump in height when you started typing.

This is on;y a problem on Neon because Neon uses a fontconfig file that falls
back to the Noto Symbols font to get the bullet chatacter, which happens to be
taller than Noto Sans. The solution here is to use a different character for
the bullet.

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

[dolphin] [Bug 405343] Typing invokes filter function (like Gnome Nautilus)

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=405343

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #2 from Nate Graham  ---
Nope, sorry. Type-ahead and filtering are used for different things; you're
proposing removing the type-ahead functionality entirely. In Nautilus, this is
actually one of the most complained-about feature removals (see
https://bugzilla.gnome.org/show_bug.cgi?id=680118) and I don't have any
interest in going down that path. I personally consider it to be an
anti-feature in GNOME and I find it to be just awful wherever it's implemented.

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

[konsole] [Bug 405345] Impossible to print "bold red". Bold is always printed as intense/light color

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=405345

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #2 from Nate Graham  ---
Fixed just a few days ago in the upcoming KDE Applications 19.04.0. :)

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

[kmymoney] [Bug 405383] Add python3 support for weboob plugin

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=405383

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

--- Comment #1 from Nate Graham  ---
"weboob"? Umm, is this a joke?

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

[frameworks-baloo] [Bug 405247] baloo (baloo_file_extractor) should report what file is causing it problems

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=405247

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #3 from Nate Graham  ---
The problem with writing the file it's currently indexing to some log somewhere
is that this would be a huge privacy violation and we'd be storing a lot of
potentially sensitive and personally-identifiable information in that log file.

`balooctl monitor` already does show you which file it's working on; is there a
reason why that's not sufficient?

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

[kate] [Bug 405415] [Kate] [Feature request] Please provide an APT install package which does not depends on KDE, similar to kdiff3

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=405415

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #2 from Nate Graham  ---
Distros provide the packages; you'll need to ask your distro for a different
kind of package.

However, I'm not sure what's in the kdiff-qt package, but if an app requires a
dependent library, it's gonna need to get that library somehow. Options include
installing the library separately via the package manager and dynamically
linking against it, or bundling the library with the app itself--which means no
outside dependencies, but then the app bundle itself is very large. But you
have to pay the piper somehow. :)

What 300mb dependent libraries does your distro's Kate package require? It
almost sounds like maybe you don't already have Qt on your system, and the
package manager is going to install it to get Kate.

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

[dolphin] [Bug 405425] error en dependencias, no se puede instalar, eliminado despues ultima actualización

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=405425

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #1 from Nate Graham  ---
Dependency issues are specific to distros and not the fault of Dolphin itself.

In the future, please fill out the template instead of leaving it blank.
English helps too. :)

For more information, see https://community.kde.org/Get_Involved/Bug_Reporting

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

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

2019-03-16 Thread Andre Kovacs
https://bugs.kde.org/show_bug.cgi?id=405437

--- Comment #47 from Andre Kovacs  ---
The only two things I could figure out that could be different in my machines
are macports (instead of homebrew), Python environment, and upgrade (instead of
fresh install).
Tomorrow I'll try to remove all macport installed libraries that were required
to build the universal (i386+x86_64) version of the INDI Webcam driver with
support for QT Kit.
But, unfortunately, I cannot change any Python setup, for professional reasons.

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

[latte-dock] [Bug 405511] Outline option for panel background

2019-03-16 Thread Michail Vourlakos
https://bugs.kde.org/show_bug.cgi?id=405511

Michail Vourlakos  changed:

   What|Removed |Added

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

--- Comment #1 from Michail Vourlakos  ---
already added in master version

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

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

2019-03-16 Thread Rob
https://bugs.kde.org/show_bug.cgi?id=405437

--- Comment #46 from Rob  ---
It would be a good idea to figure out what about your system is different, but
it indeed appears to work on most Sierra and High Sierra machines.  I will try
to run some tests this weekend to see if I can figure it out.

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

[latte-dock] [Bug 404266] [feature] - option to set scrolling action for empty areas

2019-03-16 Thread Michail Vourlakos
https://bugs.kde.org/show_bug.cgi?id=404266

Michail Vourlakos  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
  Latest Commit||https://commits.kde.org/lat
   ||te-dock/33c584cc0839ebfcb33
   ||822beff2ab1ee9c07cf17

--- Comment #5 from Michail Vourlakos  ---
Git commit 33c584cc0839ebfcb33822beff2ab1ee9c07cf17 by Michail Vourlakos.
Committed on 16/03/2019 at 22:49.
Pushed by mvourlakos into branch 'master'.

Mouse wheel action for empty areas

--User can now choose for the panel empty areas
a sroll wheel behavior:
-Scroll Desktops
-Scroll Activities
-Scroll Tasks

M  +9-0containment/package/contents/config/main.xml
M  +59   -0containment/package/contents/ui/RootMouseArea.qml
A  +49   -0containment/package/contents/ui/loaders/Pager.qml [License:
GPL (v2+)]
A  +115  -0containment/package/contents/ui/loaders/Tasks.qml [License:
GPL (v2+)]
M  +1-0containment/package/contents/ui/main.qml
M  +9-0liblatte2/types.h
M  +76   -30   shell/package/contents/configuration/pages/BehaviorConfig.qml

https://commits.kde.org/latte-dock/33c584cc0839ebfcb33822beff2ab1ee9c07cf17

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

[KBibTeX] [Bug 403893] Wrong escaping written to file

2019-03-16 Thread Thomas Fischer
https://bugs.kde.org/show_bug.cgi?id=403893

--- Comment #1 from Thomas Fischer  ---
Created attachment 118852
  --> https://bugs.kde.org/attachment.cgi?id=118852&action=edit
Fixing format string for dotless-i and dotless-j in EncoderLaTeX::encode

I think I have narrowed down this bug. Please test this patch and confirm if it
fixes your problem.

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

[KBibTeX] [Bug 403893] Wrong escaping written to file

2019-03-16 Thread Thomas Fischer
https://bugs.kde.org/show_bug.cgi?id=403893

Thomas Fischer  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

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

[frameworks-kio] [Bug 385189] Save dialog: Return key only bound to Save button when text field has focus

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=385189

--- Comment #8 from Nate Graham  ---
Ah you're right!

Seems like good patch material. :)

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

[frameworks-kio] [Bug 385189] Save dialog: Return key only bound to Save button when text field has focus

2019-03-16 Thread Méven Car
https://bugs.kde.org/show_bug.cgi?id=385189

--- Comment #7 from Méven Car  ---
I believe this is always reproducible in fact, it is just that the steps to
reproduce must be followed precisely.

STEPS TO REPRODUCE
1. Save a file in any KDE program in a way that triggers the Save dialog
2. Modify the filename to your liking
3. Navigate to the location that you want to save the file to, either using the
places panel or the main navigation view
4. Hit the return or enter key

I believe the bug is due to the KDirOperator widget not notifying the
kfilewidget when the user press enter/return.

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

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

2019-03-16 Thread Rob
https://bugs.kde.org/show_bug.cgi?id=405437

--- Comment #45 from Rob  ---
But that is what I did.  The whole point is that I got python, netpbm, numpy,
pyfits, and astrometry.net all wrapped up inside the app.  None of them are
built with homebrew, it is all built independent of that.  And they do not
require you to install any of that because when we first started with kstars on
Mac, that was a real nightmare to get them all installed and working.

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

[kdeconnect] [Bug 400030] Media controls in KDE Plasma for the phone

2019-03-16 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=400030

Nicolas Fella  changed:

   What|Removed |Added

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

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

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

2019-03-16 Thread Andre Kovacs
https://bugs.kde.org/show_bug.cgi?id=405437

--- Comment #44 from Andre Kovacs  ---
My guess is that we should try to get Astrometry.net to build and work on its
own, because the KStars astrometry module works just fine with the older
version of the Astrometry.net binaries.
But never managed to get a local version of Astrometry.net to work.

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

[krita] [Bug 405540] Brush Outline are white in Krita nightly build

2019-03-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=405540

--- Comment #1 from reptilli...@live.com ---
Found out something, when I reverted back to e6f675, the brush outline are
completely gone. Didn't happened before I installed the latest Jenkins beta as
of this date or the reported version. 

Also, tablet support are broken in the latest build, but not sure if I should
report that seeing as QT support is experimental. Now, they act like a mouse
would, well, mostly.

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

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

2019-03-16 Thread Andre Kovacs
https://bugs.kde.org/show_bug.cgi?id=405437

--- Comment #43 from Andre Kovacs  ---
Since I'm a new High Sierra user, I don't know what surprises Apple left to us
in this version.
El Capitan was really traumatic to me, so I postponed the upgrade afterwards as
long as I could.

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

[digikam] [Bug 405149] The "File Name" in the thumbnail view is not visible

2019-03-16 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=405149

Maik Qualmann  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED
   Version Fixed In||6.1.0

--- Comment #2 from Maik Qualmann  ---
I close the bug now, the file name is possible in the thumbnail view, if it is
activated in the setup.

Maik

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

[Discover] [Bug 405132] Discover reports no updates No Internet connectivity

2019-03-16 Thread Gene Soo
https://bugs.kde.org/show_bug.cgi?id=405132

--- Comment #2 from Gene Soo  ---
Discover reported No Internet Connection. Web browsing completely worked
and SUDO APT commands worked to perform standard maintenance update and app
installs in spite of the negative connection report from Discover.

Gene

On Sat, Mar 16, 2019 at 3:11 PM Aleix Pol  wrote:

> https://bugs.kde.org/show_bug.cgi?id=405132
>
> --- Comment #1 from Aleix Pol  ---
> And you have proper internet connection?
> Do you get a similar issue with apt or any other client?
>
> --
> You are receiving this mail because:
> You reported the bug.

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

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

2019-03-16 Thread Rob
https://bugs.kde.org/show_bug.cgi?id=405437

--- Comment #41 from Rob  ---
I do have a Sierra virtual machine.  I could build kstars in that and it would
definitely be built on an older computer than yours so then the illegal
instruction error would most likely go away if the Mac OS X version is the
issue.

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

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

2019-03-16 Thread Rob
https://bugs.kde.org/show_bug.cgi?id=405437

--- Comment #42 from Rob  ---
The goal is to be able to build kstars on any computer Sierra or newer and then
have it work on any computer Sierra or newer.  But maybe its not there yet
fully?

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

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

2019-03-16 Thread Rob
https://bugs.kde.org/show_bug.cgi?id=405437

--- Comment #40 from Rob  ---
"Another issue I forgot to mention was that Mac OS is complaining about the
developer identity of the app. I had to use the trick of opening the app by
right-click+open in Finder to be able to use it."

This will always be true unless somebody wants to pay a yearly premium for a
developer license and then code sign it.

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

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

2019-03-16 Thread Rob
https://bugs.kde.org/show_bug.cgi?id=405437

--- Comment #39 from Rob  ---
Actually I downloaded the High Sierra installer from apple and I installed it
in my parallels virtual machine.  It is totally fresh.

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

[plasmashell] [Bug 405495] Request: Option to disable minimization of active window

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=405495

Nate Graham  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #3 from Nate Graham  ---
I would actually not mind having feature myself--especially when using an
Icons-Only task manager more or less replicating the macOS Dock paradigm.

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

[okular] [Bug 405462] wrong display of annotation

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=405462

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

--- Comment #4 from Nate Graham  ---
(In reply to Tobias Deiminger from comment #3)
> Albert already suggested a solution which should work here too:
> > Actually fixing this pdf "the right way" is not hard,
> > we just need https://paste.kde.org/pk6wzgiqs in poppler
> > and then a "backendPaintsStamp" or similar in the
> > okular core annotation.
Did that ever get into Popper?

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

[plasmashell] [Bug 405454] Desktop names don't appear in the pager applet, only "..."

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=405454

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

--- Comment #4 from Nate Graham  ---
(In reply to Kai Uwe Broulik from comment #2)
> Your wife indeed has very good memory! Just checked the old sourcecode and
> it had a special case for this:
> 
> // When containment is in this position [ie. horizontal] we are not limited
> by low width and we can
> // afford increasing width of applet to be able to display every name of
> desktops
Yeah, it probably makes sense to bring that back if we can.

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

[elisa] [Bug 405144] Hamburger menu and settings window show fonts badly rendered when fractional display scaling is used

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=405144

Nate Graham  changed:

   What|Removed |Added

 Depends on||405541

--- Comment #2 from Nate Graham  ---
This is because they use QtQuickControls 1, which always looks bad with
fractional scale factors. I tried my hand at porting these parts of the UI to
use QQC2, and that fixes the problem. But I ran into an issue: QQC2 menu items
are much more difficult to assign keyboard shortcuts to (Bug 405541).


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=405541
[Bug 405541] Cannot get keyboard shortcut to visibly appear in QQC2 MenuItem
-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kirigami] [Bug 405541] Cannot get keyboard shortcut to visibly appear in QQC2 MenuItem

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=405541

Nate Graham  changed:

   What|Removed |Added

 Blocks||405144


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=405144
[Bug 405144] Hamburger menu and settings window show fonts badly rendered when
fractional display scaling is used
-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kirigami] [Bug 405541] New: Cannot get keyboard shortcut to visibly appear in QQC2 MenuItem

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=405541

Bug ID: 405541
   Summary: Cannot get keyboard shortcut to visibly appear in QQC2
MenuItem
   Product: frameworks-kirigami
   Version: Master
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: notm...@gmail.com
  Reporter: n...@kde.org
  Target Milestone: Not decided

In trying to port a QQC1 menu in ELisa to QQC2, I ran into an issue of being
unable to replicate the full functionality available in QQC1, with the menu
items having keyboard shortcuts that appear on the right-side of their menu
items.


Here's the original code (from
https://cgit.kde.org/elisa.git/tree/src/qml/ApplicationMenu.qml:)

import QtQuick 2.7
import QtQuick.Controls 1.4

Menu {
MenuItem {
text: configureAction.text
shortcut: configureAction.shortcut
iconName: elisa.iconName(configureAction.icon)
onTriggered: configureAction.trigger()
}
}


And here's a QQC2 version:


import QtQuick 2.7
import QtQuick.Controls 2.5

Menu {
MenuItem {
text: configureAction.text
icon.name: elisa.iconName(configureAction.icon)
onTriggered: configureAction.trigger()
visible: configureAction.text !== ""

Shortcut {
sequence: configureAction.shortcut
context: Qt.ApplicationShortcut
onActivated: configureAction.trigger()
}
}
}

With this, the shortcut works, but the does not visible appear in the menu
itself.



Or consider the following alternative using Actions in the Menu


import QtQuick 2.7
import QtQuick.Controls 2.5
Menu {
Action {
text: configureAction.text
shortcut: configureAction.shortcut
icon.name: elisa.iconName(configureAction.icon)
onTriggered: configureAction.trigger()
}
}

With this, the shortcut neither works, nor visibly appears in the menu.


I feel like one or both of these should work.

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

[kmail2] [Bug 405530] no "ham" status icon

2019-03-16 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=405530

Christophe Giboudeaux  changed:

   What|Removed |Added

 Resolution|INTENTIONAL |NOT A BUG

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

[Discover] [Bug 398237] Discover app re-fetches updates when opened from the Plasmoid that the Plasmoid already seems to know about

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=398237

Nate Graham  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
   Version Fixed In||5.16.0
 Resolution|--- |FIXED
  Latest Commit||https://cgit.kde.org/discov
   ||er.git/commit/?id=2d8c028cd
   ||3955055289f3109fce2e3068fd2
   ||dd7d

--- Comment #9 from Nate Graham  ---
In fact, that's just what we ended up doing. :)

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

[digikam] [Bug 405519] Google Maps not shown (blank map window)

2019-03-16 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=405519

--- Comment #8 from Maik Qualmann  ---
The poor quality of Nouveau and due to the quite frequent kernel updates on
openSUSE Tumbleweed and recompilation of the proprietary NVIDIA driver, I
switched to AMD.

Maik

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

[kio-extras] [Bug 331240] Folder preview does not consider files larger than 3MB in size

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=331240

--- Comment #11 from Nate Graham  ---
This is strange. With seemingly identical settings, I am able to reproduce the
issue on my Manjaro machine, but not my Neon machine.

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

[frameworks-kio] [Bug 385189] Save dialog: Return key only bound to Save button when text field has focus

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=385189

--- Comment #6 from Nate Graham  ---
I'm the opposite! I can reproduce with Kate but it works fine for me in
Spectacle! :p

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

[plasmashell] [Bug 347326] Usability regression: resizing widgets in plasma 5

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=347326

--- Comment #5 from Nate Graham  ---
Sounds like a good patch opportunity. :)

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

[digikam] [Bug 405512] Meta Key Not Useful For Key Modifier In Windows

2019-03-16 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=405512

--- Comment #7 from Maik Qualmann  ---
Ok, we have Meta + Ctrl + F1 for album. With Ctrl + Alt + F1 we are on the
console under Linux. This will be a puzzle and OSX is not there yet.

Maik

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

[plasmashell] [Bug 405495] Request: Option to disable minimization of active window

2019-03-16 Thread Rob
https://bugs.kde.org/show_bug.cgi?id=405495

--- Comment #2 from Rob  ---
That's correct - the window is being displayed, though I do not realize it.
Doing nothing would be just fine. This would be so much better than seeing the
contents of another window. A quick blink or flash of the tab or the tab's
current-window indicator might offer good feedback. Grateful either way :-)

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

[kwin] [Bug 400658] Impossible to walk through all apps or all windows of the current app on Wayland

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=400658

Nate Graham  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk,
   ||vladz...@gmail.com

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

[kwin] [Bug 400658] Impossible to walk through all apps or all windows of the current app on Wayland

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=400658

--- Comment #12 from Nate Graham  ---
None, it appears to be a duplicate. Migrating the most relevant comment there
over to here:

> My .config/kcminputrc contains that keyboard section:
> 
> ===
> [Keyboard]
> KeyboardRepeating=0
> NumLock=0
> RepeatDelay=600
> RepeatRate=25
> ===
> 
> I don't know what's wrong here, but if I remove that keyboard section the
> Alt + Tab behaves as normal.

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

[Powerdevil] [Bug 405508] powerdevil is not clever when the battery is very big

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=405508

--- Comment #6 from Nate Graham  ---
Yeah, accepting floating-point numbers in the spinbox could make sense.

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

[kwin] [Bug 400658] Impossible to walk through all apps or all windows of the current app on Wayland

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=400658

Nate Graham  changed:

   What|Removed |Added

 CC||tro...@free.fr

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

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

[kwin] [Bug 403315] Cannot navigate through windows via Alt+Tab

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=403315

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #13 from Nate Graham  ---


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

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

[systemsettings] [Bug 386748] Some icons are missing in tooltips

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=386748

--- Comment #15 from Nate Graham  ---
This can be fixed with code similar to
https://cgit.kde.org/kinfocenter.git/commit/?id=23fa369831709f43a3100476b00ced10a1123f7f

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

[kio-extras] [Bug 401170] Preview of text files is blurry with fractional display scaling

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=401170

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #4 from Nate Graham  ---
Yep, this was probably fixed with
https://cgit.kde.org/kiconthemes.git/commit/?id=89344923c00b7bc502f5c24be50027b457d82177

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

[digikam] [Bug 405519] Google Maps not shown (blank map window)

2019-03-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=405519

--- Comment #7 from caulier.gil...@gmail.com ---
Maik,

It work, even if i can see these kernel warnings on the console :

digikam.geoiface: 
digikam.geoiface: located data:
QUrl("file:///usr/local/share/digikam/geoiface/backend-googlemaps.html")
digikam.geoiface: Maps Loading Progress:  10 %
digikam.geoiface: Maps Loading Progress:  70 %
digikam.geoiface: Maps Loading Progress:  90 %
digikam.geoiface: Maps Loading Progress:  100 %
digikam.geoiface: Map Loading Completed:  true
digikam.geoiface: "SATELLITE"
digikam.geoiface: "backend googlemaps is ready!"
digikam.geoiface: "googlemaps:17"
digikam.geoiface: Maps Loading Progress:  100 %
digikam.geoiface: Maps Loading Progress:  100 %
digikam.geoiface: "(event)MTSATELLITE"
digikam.geoiface: "(event)ZC"
digikam.geoiface: Maps Loading Progress:  10 %
digikam.geoiface: Maps Loading Progress:  100 %
digikam.geoiface: Maps Loading Progress:  100 %
digikam.geoiface: Maps Loading Progress:  10 %
digikam.geoiface: Maps Loading Progress:  100 %
digikam.geoiface: Maps Loading Progress:  100 %
digikam.geoiface: "(event)id"
digikam.geoiface: "created cluster 0: 1 tiles"
digikam.geoiface: "level 7: 1 non empty tiles sorted into 1 clusters (1
searched)"
digikam.geoiface: start updateclusters
digikam.geoiface: end updateclusters
digikam.geoiface: QVariant(QPersistentModelIndex,
QModelIndex(0,0,0x397fb00,QStandardItemModel(0x24c7590))) QSize(44, 58)
nouveau: kernel rejected pushbuf: Aucun fichier ou dossier de ce type
nouveau: ch13: krec 0 pushes 0 bufs 1 relocs 0
nouveau: ch13: buf  0002 0004 0004 
nouveau: kernel rejected pushbuf: Aucun fichier ou dossier de ce type
nouveau: ch13: krec 0 pushes 0 bufs 1 relocs 0
nouveau: ch13: buf  0004 0004 0004 
nouveau: ch13: buf 0001 0006 0004  0004
digikam.geoiface: "(event)id"
digikam.geoiface: "created cluster 0: 1 tiles"
digikam.geoiface: "level 7: 1 non empty tiles sorted into 1 clusters (1
searched)"
digikam.geoiface: start updateclusters
digikam.geoiface: end updateclusters
digikam.geoiface: "(event)id"
digikam.geoiface: "created cluster 0: 1 tiles"
digikam.geoiface: "level 7: 1 non empty tiles sorted into 1 clusters (1
searched)"
digikam.geoiface: start updateclusters
digikam.geoiface: end updateclusters

Gilles

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

[digikam] [Bug 405519] Google Maps not shown (blank map window)

2019-03-16 Thread Kristian
https://bugs.kde.org/show_bug.cgi?id=405519

--- Comment #6 from Kristian  ---
I'm using NVIDIA with proprietary driver on Arch Linux (extra/nvidia-340xx
340.107-68).

$ glxinfo | grep -i "vendor\|rendering"
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
client glx vendor string: NVIDIA Corporation
OpenGL vendor string: NVIDIA Corporation
GL_NV_parameter_buffer_object2, GL_NV_path_rendering, 
GL_NV_parameter_buffer_object2, GL_NV_path_rendering, 

$ lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GT218M [NVS 3100M] (rev
a2)

$ lsmod | grep "kms\|drm"
drm   499712  3 nvidia
agpgart53248  3 intel_agp,intel_gtt,drm

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

[digikam] [Bug 405512] Meta Key Not Useful For Key Modifier In Windows

2019-03-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=405512

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

   What|Removed |Added

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

--- Comment #6 from caulier.gil...@gmail.com ---
Look LR keyboard Shortcuts :

https://www.lightroomqueen.com/keyboard-shortcuts/lrcc6/

There is no META key used here. So It sound a good compromise to drop META key
in digiKam.

Gilles

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

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

2019-03-16 Thread Andre Kovacs
https://bugs.kde.org/show_bug.cgi?id=405437

--- Comment #38 from Andre Kovacs  ---
When you built your High Sierra machine you installed from scratch or upgraded
from El Capitan?

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

[Discover] [Bug 385754] [Flatpak] The number of updates available shown by Discover and its tray icon don't match

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=385754

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||5.16.0

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

[Discover] [Bug 405533] Just open Discover when left-clicking on the Update notifier system tray item

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=405533

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||5.16.0

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

[Discover] [Bug 403333] Can pull down on Updates page to check for updates while already updating

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=40

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||5.15.4

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

[frameworks-kirigami] [Bug 404827] Use window color set (gray background) for cards views

2019-03-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=404827

--- Comment #4 from Nate Graham  ---
Git commit 094c9d947e17768397aca8572865799f0650f594 by Nate Graham.
Committed on 16/03/2019 at 20:41.
Pushed by ngraham into branch 'Plasma/5.15'.

Restore proper background color on list and sources pages

Summary:
Kirigami changed the defaults in 49856625cc4fb7136099ce69bfb92d99a5bca480, so
we have to
adapt in Discover.

Test Plan: {F6687104}

Reviewers: apol, #discover_software_store

Subscribers: plasma-devel

Tags: #plasma

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

M  +6-0discover/qml/ApplicationsListPage.qml
M  +6-0discover/qml/BrowsingPage.qml
M  +6-0discover/qml/SourcesPage.qml

https://commits.kde.org/discover/094c9d947e17768397aca8572865799f0650f594

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

[digikam] [Bug 405512] Meta Key Not Useful For Key Modifier In Windows

2019-03-16 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=405512

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #5 from Maik Qualmann  ---
Gilles, what do you think? Change all Meta modifiers to Ctrl + Alt? Only on
Windows? I am thinking of the longtime users. Different key combination between
the operating system is likely to cause confusion. At the moment I would just
like to change Meta + A as it is a global shortcut key under Windows10.

Maik

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

[krita] [Bug 405540] New: Brush Outline are white in Krita nightly build

2019-03-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=405540

Bug ID: 405540
   Summary: Brush Outline are white in Krita nightly build
   Product: krita
   Version: nightly build (please specify the git hash!)
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Brush engines
  Assignee: krita-bugs-n...@kde.org
  Reporter: reptilli...@live.com
  Target Milestone: ---

SUMMARY
When I tried to paint, it took me a while to notice that I actually don't have
any idea on where I am painting. The source? The fact that the brush outline is
now white on a white canvas. It was not like this before.

STEPS TO REPRODUCE
1. Just paint.

OBSERVED RESULT
White brush outline on white canvas. It shows up on black fills, but not on
white fills.

EXPECTED RESULT
I am able to see where I am going to paint without having to guess blindly.

SOFTWARE/OS VERSIONS
Windows: Microsoft Windows 10 Home Version 10.0.17134 Build 17134
Software - Krita 4.2.0-pre-alpha (git 0492ac7) - Source from Jenkins
Graphic Card - NVIDIA Quadro K4200
OpenGL Enabled


ADDITIONAL INFORMATION

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

[kstars] [Bug 405539] New: Slews without hiccough

2019-03-16 Thread Jean-Claude
https://bugs.kde.org/show_bug.cgi?id=405539

Bug ID: 405539
   Summary: Slews without hiccough
   Product: kstars
   Version: 3.1.1
  Platform: Other
OS: OS X
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: jcjes...@free.fr
  Target Milestone: ---

SUMMARY
When you type N or S, KStars slews VERY smoothly to the North or South.
But when the scope slews to a target it does it with a hiccough.
I know it's not a priority but this would make KStars even nicer to use !

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
MacOS: 10.14
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 405538] New: KWin crash, then opening telegram from system tray

2019-03-16 Thread carl
https://bugs.kde.org/show_bug.cgi?id=405538

Bug ID: 405538
   Summary: KWin crash, then opening telegram from system tray
   Product: kwin
   Version: 5.15.2
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: schwanc...@protonmail.com
  Target Milestone: ---

Application: kwin_x11 (5.15.2)

Qt Version: 5.12.1
Frameworks Version: 5.56.0
Operating System: Linux 5.0.0-arch1-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed: I clicked on the telegram
system tray (latte dock) button, this switched the virtual desktop and crashed
KWin, KWin automaticly restarted after.

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 0x7f6acf05b880 (LWP 9900))]

Thread 7 (Thread 0x7f6ac7fff700 (LWP 10656)):
#0  0x7f6ad5675afc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f6ad668cc4c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt5Core.so.5
#2  0x7f6ad668cd3a in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#3  0x7f6ad51ae92d in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f6ad51aeb9c in  () at /usr/lib/libQt5Quick.so.5
#5  0x7f6ad668696c in  () at /usr/lib/libQt5Core.so.5
#6  0x7f6ad566fa9d in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f6ad7d27b23 in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f6ac5196700 (LWP 10334)):
#0  0x7f6ad7d1cd16 in ppoll () at /usr/lib/libc.so.6
#1  0x7f6ad6894bab in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f6ad689608b in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f6ad6841b2c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f6ad6685569 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f6ad668696c in  () at /usr/lib/libQt5Core.so.5
#6  0x7f6ad566fa9d in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f6ad7d27b23 in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f6aabfff700 (LWP 9915)):
#0  0x7f6ad5675afc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f6ad617b28c in  () at /usr/lib/libQt5Script.so.5
#2  0x7f6ad617b2a9 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f6ad566fa9d in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f6ad7d27b23 in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f6ac77fe700 (LWP 9910)):
#0  0x7f6ad7d1cd16 in ppoll () at /usr/lib/libc.so.6
#1  0x7f6ad6894bab in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f6ad689608b in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f6ad6841b2c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f6ad6685569 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f6ad4e2c969 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7f6ad668696c in  () at /usr/lib/libQt5Core.so.5
#7  0x7f6ad566fa9d in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f6ad7d27b23 in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f6acda05700 (LWP 9904)):
#0  0x7f6ad7d1cd16 in ppoll () at /usr/lib/libc.so.6
#1  0x7f6ad6894bab in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f6ad689608b in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f6ad6841b2c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f6ad6685569 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f6ad4890ba6 in  () at /usr/lib/libQt5DBus.so.5
#6  0x7f6ad668696c in  () at /usr/lib/libQt5Core.so.5
#7  0x7f6ad566fa9d in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f6ad7d27b23 in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f6ace8aa700 (LWP 9903)):
#0  0x7f6ad7d1cc21 in poll () at /usr/lib/libc.so.6
#1  0x7f6ad65aa630 in  () at /usr/lib/libxcb.so.1
#2  0x7f6ad65ac2db in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#3  0x7f6acebb0949 in  () at /usr/lib/libQt5XcbQpa.so.5
#4  0x7f6ad668696c in  () at /usr/lib/libQt5Core.so.5
#5  0x7f6ad566fa9d in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f6ad7d27b23 in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f6acf05b880 (LWP 9900)):
[KCrash Handler]
#6  0x7f6ad7c63d7f in raise () at /usr/lib/libc.so.6
#7  0x7f6ad7c4e672 in abort () at /usr/lib/libc.so.6
#8  0x7f6ad664c7fc in  () at /usr/lib/libQt5Core.so.5
#9  0x7f6ad63ed12a in KWin::WindowQuad::makeSubQuad(do

[digikam] [Bug 405537] Strange behavior with tag in attached file

2019-03-16 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=405537

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
Your keyword is included in "Iptc.Application2.Keywords" though not
in "Xmp.dc.subject". This behavior you can set in the digiKam-> Settings->
Metadata-> Advanced and there Iptc.Application2.Keywords move higher. Programs
store tags in different metadata fields. You have to tell digiKam which one to
import.

Exiftool:
Keywords : 2018 06 Schottland, Kelpies, Lightroom43, r4
Subject : 2018 06 Schottland, Kelpies, Lightroom43

Maik

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

[digikam] [Bug 349268] Be able to copy the uploaded url

2019-03-16 Thread Osipov Oleg
https://bugs.kde.org/show_bug.cgi?id=349268

--- Comment #3 from Osipov Oleg  ---
Just tested Spectacle 18.04.3, fedora:
After exporing to imgur:
1. the URL is shown on the screen;
2. URL is NOT copied to clipboard nor mouse buffer automaticaly;
3. URL on the screen CAN be rightclicked and copied to clipboard;
4. after short time address DISAPPEARS from window and cannot be brought back.
A very strange behavior. In my first test I was so glad to see a copyable URL
so I did not got it copied in time. May that disappear-after-5-secs thing be
removed please? Otherwise everything is fine now.

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

[Discover] [Bug 403333] Can pull down on Updates page to check for updates while already updating

2019-03-16 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=40

Aleix Pol  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/dis
   ||cover/84f70236f4d98ee53c83e
   ||c7fa30a396754e332ad
 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #1 from Aleix Pol  ---
Git commit 84f70236f4d98ee53c83ec7fa30a396754e332ad by Aleix Pol.
Committed on 16/03/2019 at 20:13.
Pushed by apol into branch 'Plasma/5.15'.

Don't allow refreshing during updates

M  +1-0discover/qml/UpdatesPage.qml

https://commits.kde.org/discover/84f70236f4d98ee53c83ec7fa30a396754e332ad

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

[digikam] [Bug 405537] Strange behavior with tag in attached file

2019-03-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=405537

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

   What|Removed |Added

  Component|general |Metadata-Engine
 CC||caulier.gil...@gmail.com

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

[Discover] [Bug 405533] Just open Discover when left-clicking on the Update notifier system tray item

2019-03-16 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=405533

Aleix Pol  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/dis
   ||cover/2d8c028cd3955055289f3
   ||109fce2e3068fd2dd7d
 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Aleix Pol  ---
Git commit 2d8c028cd3955055289f3109fce2e3068fd2dd7d by Aleix Pol.
Committed on 16/03/2019 at 20:07.
Pushed by apol into branch 'master'.

Don't calculate updates on the updates notification plasmoid
Related: bug 385754

M  +0-9libdiscover/backends/DummyBackend/DummyNotifier.cpp
M  +2-2libdiscover/backends/DummyBackend/DummyNotifier.h
M  +35   -40   libdiscover/backends/FlatpakBackend/FlatpakNotifier.cpp
M  +12   -9libdiscover/backends/FlatpakBackend/FlatpakNotifier.h
M  +5-4libdiscover/backends/PackageKitBackend/PackageKitNotifier.cpp
M  +2-2libdiscover/backends/PackageKitBackend/PackageKitNotifier.h
M  +3-2libdiscover/notifiers/BackendNotifierModule.h
M  +11   -49   notifier/DiscoverNotifier.cpp
M  +5-12   notifier/DiscoverNotifier.h
D  +0-84   notifier/plasmoid/contents/ui/Full.qml
M  +48   -1notifier/plasmoid/contents/ui/main.qml

https://commits.kde.org/discover/2d8c028cd3955055289f3109fce2e3068fd2dd7d

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

[Discover] [Bug 385754] [Flatpak] The number of updates available shown by Discover and its tray icon don't match

2019-03-16 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=385754

Aleix Pol  changed:

   What|Removed |Added

  Latest Commit|https://commits.kde.org/dis |https://commits.kde.org/dis
   |cover/50cbb53afdaca8bd91aa8 |cover/2d8c028cd3955055289f3
   |aec2b66ecc18b147d58 |109fce2e3068fd2dd7d
 Resolution|--- |FIXED
 Status|REOPENED|RESOLVED

--- Comment #30 from Aleix Pol  ---
Git commit 2d8c028cd3955055289f3109fce2e3068fd2dd7d by Aleix Pol.
Committed on 16/03/2019 at 20:07.
Pushed by apol into branch 'master'.

Don't calculate updates on the updates notification plasmoid
Related: bug 405533

M  +0-9libdiscover/backends/DummyBackend/DummyNotifier.cpp
M  +2-2libdiscover/backends/DummyBackend/DummyNotifier.h
M  +35   -40   libdiscover/backends/FlatpakBackend/FlatpakNotifier.cpp
M  +12   -9libdiscover/backends/FlatpakBackend/FlatpakNotifier.h
M  +5-4libdiscover/backends/PackageKitBackend/PackageKitNotifier.cpp
M  +2-2libdiscover/backends/PackageKitBackend/PackageKitNotifier.h
M  +3-2libdiscover/notifiers/BackendNotifierModule.h
M  +11   -49   notifier/DiscoverNotifier.cpp
M  +5-12   notifier/DiscoverNotifier.h
D  +0-84   notifier/plasmoid/contents/ui/Full.qml
M  +48   -1notifier/plasmoid/contents/ui/main.qml

https://commits.kde.org/discover/2d8c028cd3955055289f3109fce2e3068fd2dd7d

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

[Discover] [Bug 405132] Discover reports no updates No Internet connectivity

2019-03-16 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=405132

--- Comment #1 from Aleix Pol  ---
And you have proper internet connection?
Do you get a similar issue with apt or any other client?

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

[kscreenlocker] [Bug 375536] Password error after suspend / sleep / lock

2019-03-16 Thread Reuben
https://bugs.kde.org/show_bug.cgi?id=375536

--- Comment #17 from Reuben  ---
I spoke too soon. I left the laptop for a couple hours and it suspended; the
keyboard was unresponsive (to KDE) when I returned. Alt sysrq reisub worked,
but I couldn't restart X or switch to different TTYs.

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

[digikam] [Bug 405537] New: Strange behavior with tag in attached file

2019-03-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=405537

Bug ID: 405537
   Summary: Strange behavior with tag in attached file
   Product: digikam
   Version: 6.1.0
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: harald.a...@web.de
  Target Milestone: ---

Created attachment 118850
  --> https://bugs.kde.org/attachment.cgi?id=118850&action=edit
Sample file

SUMMARY

The attached file contains a tag "r4", which is visible in Windows Explorer,
Exiftool, Irfanview, Picasa, but not in digiKam. 

Also, after adding a tag externally, digiKam refreshes and "Photograph
Properties" disappear.


STEPS TO REPRODUCE
1. Load file into digiKam
   => Tag "r4" is not shown in "Properties" page on the right side.
2. In Windows Explorer, add a Tag "r5" after "r4"
   => Properties in digiKam refresh automatically. Tags r4 and r5 are now
shown. However, "Photograph Properties" disappear.
3. In Windows Explorer, remove Tag "r5".
   => This time, digiKam does not refresh.
3. In Windows Explorer, rename file to DSC06938a.jpg.
   => digiKam refreshes. "Photograph Properties" are visible again, as is tag
r4.


SOFTWARE/OS VERSIONS
Windows: Win7 32bit


ADDITIONAL INFORMATION

I have the same behavior with all my files; the attached is just a sample.
Might be interesting to know that the other tags were exported from Lightroom,
while the tag "r4" was added later using exiftool.

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

[frameworks-kio] [Bug 405282] Date in file conflit dialog does not respect regional settings

2019-03-16 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=405282

Patrick Silva  changed:

   What|Removed |Added

 CC||lasse.li...@gmail.com

--- Comment #1 from Patrick Silva  ---
*** Bug 405534 has been marked as a duplicate of this bug. ***

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

[frameworks-kio] [Bug 405534] Incorrect Finnish date format in KIO overwrite dialog

2019-03-16 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=405534

Patrick Silva  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com
 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #2 from Patrick Silva  ---


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

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

[krita] [Bug 405536] New: Krita does not draw transformed cloned layer when the original is hidden and colorized.

2019-03-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=405536

Bug ID: 405536
   Summary: Krita does not draw transformed cloned layer when the
original is hidden and colorized.
   Product: krita
   Version: 4.1.7
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Tools/Transform
  Assignee: krita-bugs-n...@kde.org
  Reporter: dieter.de.moi...@gmail.com
  Target Milestone: ---

Created attachment 118849
  --> https://bugs.kde.org/attachment.cgi?id=118849&action=edit
The drawing with the issue

SUMMARY
Krita does not draw a transformed cloned layer when the original is hidden and
colorized. The issue occurs after closing and reopening the file. 


STEPS TO REPRODUCE
1/ Create a new paint (or vector) layer
2/ Draw a circle 
3/ Add a colorize mask, fill the circle with a color and make the outside
transparent
4/ Select original layer and add a clone layer 
5/ Add a transformation mask to the cloned layer
6/ Move the circle on the cloned layer to a different place
7/ Hide the original layer => Now only the cloned/transformed circle is shown
8/ Save this drawing, close the file and reopen it. => Nothing is shown now
10/ Unhide the orginal layer => Now two circle are shown
11/ Hide the original layer again => We now see again only the
cloned/transformed circle

test_clone2.kra attached is my resulting file, which can be used to reproduce
this

EXPECTED RESULT
1/ After opening the file, I'd expect the same drawing as when last saved
(consistent results).
2/ The cloned circle shown at any time.

WORKAROUND
Select the original layer and add it in a group. Instead of cloning the
original layer, clone the group and transform this one.

SOFTWARE/OS VERSIONS
Krita
  Version: 4.1.7.101

Qt
  Version (compiled): 5.11.3
  Version (loaded): 5.11.3

OS Information
  Build ABI: x86_64-little_endian-lp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: linux
  Kernel Version: 4.20.13-200.fc29.x86_64
  Pretty Productname: Fedora 29 (Workstation Edition)
  Product Type: fedora
  Product Version: 29

OpenGL Info
  **OpenGL not initialized**

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

[KBibTeX] [Bug 403793] error in saving unicode-8

2019-03-16 Thread Thomas Fischer
https://bugs.kde.org/show_bug.cgi?id=403793

Thomas Fischer  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |FIXED
   Version Fixed In||0.9
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from Thomas Fischer  ---
I noticed that your bug report mentioned version 0.8.2 whereas my test was on
the latest development version. Due to a re-write, the bug should not exist in
0.9 and any later version, including the master branch.

Please test it yourself. Use the quick start to run KBibTeX [1] with the
following command:
bash run-kbibtex.sh "https://anongit.kde.org/kbibtex.git"; "kbibtex/0.9"

[1]
https://userbase.kde.org/KBibTeX/Development#Quick_Start_to_Run_KBibTeX_from_Git

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

  1   2   3   >