[kmymoney] [Bug 402101] Allow to reuse check numbers

2019-01-25 Thread Thomas Baumgart
https://bugs.kde.org/show_bug.cgi?id=402101

Thomas Baumgart  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||5.0.3
 Status|REPORTED|RESOLVED
  Latest Commit||https://commits.kde.org/kmy
   ||money/b1fdee150af99db313468
   ||9efcb1ca3f5aff7daaa

--- Comment #2 from Thomas Baumgart  ---
Git commit b1fdee150af99db3134689efcb1ca3f5aff7daaa by Thomas Baumgart.
Committed on 26/01/2019 at 07:16.
Pushed by tbaumgart into branch '5.0'.

Fix check number handling

KMyMoney versions prior to 5.0 allowed to re-use check numbers. This is
not possible with the current 5.0 versions. This change will bring back
the original functionality.

In case KMyMoney detects a duplicate check number it informs the user.
The user then has the possibility to assign the next free number or
leave the number as entered. It will not be cleared in this case
anymore.
FIXED-IN: 5.0.3

M  +6-4kmymoney/dialogs/keditscheduledlg.cpp
M  +1-7kmymoney/dialogs/kenterscheduledlg.cpp
M  +1-1kmymoney/dialogs/stdtransactioneditor.cpp
M  +37   -49   kmymoney/dialogs/transactioneditor.cpp
M  +6-5kmymoney/dialogs/transactioneditor.h
M  +24   -48   kmymoney/kmymoneyutils.cpp
M  +9-4kmymoney/kmymoneyutils.h
M  +0-1kmymoney/views/kgloballedgerview.cpp
M  +7-4kmymoney/views/kgloballedgerview_p.h

https://commits.kde.org/kmymoney/b1fdee150af99db3134689efcb1ca3f5aff7daaa

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

[kmymoney] [Bug 402101] Allow to reuse check numbers

2019-01-25 Thread Thomas Baumgart
https://bugs.kde.org/show_bug.cgi?id=402101

Thomas Baumgart  changed:

   What|Removed |Added

Summary|Re using check numbers  |Allow to reuse check
   ||numbers

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

[gwenview] [Bug 403613] New: Gwenview crashed when selecting another folder, while photo being watched.

2019-01-25 Thread Henk
https://bugs.kde.org/show_bug.cgi?id=403613

Bug ID: 403613
   Summary: Gwenview crashed when selecting another folder, while
photo being watched.
   Product: gwenview
   Version: unspecified
  Platform: Mint (Ubuntu based)
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: henk.dekker...@gmail.com
  Target Milestone: ---

Application: gwenview (16.04.3)

Qt Version: 5.6.1
Frameworks Version: 5.36.0
Operating System: Linux 4.15.0-43-generic x86_64
Distribution: Linux Mint 18.3 Sylvia

-- Information about the crash:
Gwenview crashed when selecting another folder, while photo being watched.

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

Thread 7 (Thread 0x7fc15de31700 (LWP 27666)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7fc1c8f13d9a in g_cond_wait_until () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc1c8ea3999 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc1c8ea3fbb in g_async_queue_timeout_pop () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fc1c8ef66aa in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fc1c8ef5c55 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7fc1c93f06ba in start_thread (arg=0x7fc15de31700) at
pthread_create.c:333
#7  0x7fc1ce1b441d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7fc13dffb700 (LWP 27598)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7fc1ce8a75f6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fc1ce8a2e2a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7fc1ce8a6808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fc1c93f06ba in start_thread (arg=0x7fc13dffb700) at
pthread_create.c:333
#5  0x7fc1ce1b441d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7fc13d7fa700 (LWP 27597)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7fc1ce8a75f6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fc1ce8a2e2a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7fc1ce8a6808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fc1c93f06ba in start_thread (arg=0x7fc13d7fa700) at
pthread_create.c:333
#5  0x7fc1ce1b441d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7fc1a8d7b700 (LWP 24759)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc1aeb5e70b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#2  0x7fc1aeb5e427 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#3  0x7fc1c93f06ba in start_thread (arg=0x7fc1a8d7b700) at
pthread_create.c:333
#4  0x7fc1ce1b441d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fc1a9ce4700 (LWP 24758)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc1aeb5e70b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#2  0x7fc1aeb5e427 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#3  0x7fc1c93f06ba in start_thread (arg=0x7fc1a9ce4700) at
pthread_create.c:333
#4  0x7fc1ce1b441d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fc1b764c700 (LWP 24757)):
#0  0x7fc1ce1a427d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fc1c8f12790 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc1c8ecee74 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc1c8ecf330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fc1c8ecf49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fc1cead037b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fc1cea78ffa in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fc1ce8a19e4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fc1d3232515 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#9  0x7fc1ce8a6808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7fc1c93f06ba in start_thread (arg=0x7fc1b764c700) at
pthread_create.c:333
#11 0x7fc1ce1b441d in clone () at

[Falkon] [Bug 403612] New: Crashes as User but Not as Root

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

Bug ID: 403612
   Summary: Crashes as User but Not as Root
   Product: Falkon
   Version: unspecified
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: merc1...@f-m.fm
  Target Milestone: ---

SUMMARY
When I run Falkon as root everything is normal, but of course I can't do that.
When I run as a user, it crashes.  

STEPS TO REPRODUCE
1. $ ./Falkon-3.0.1.AppImage
2. Could not find QtWebEngineProcess
[17828:17828:0125/220226.413028:FATAL:zygote_host_impl_linux.cc(182)] Check
failed: ReceiveFixedMessage(fds[0], kZygoteBootMessage,
sizeof(kZygoteBootMessage), _pid). 
#0 0x7f87429cc0a5 
#1 0x7f87429e1eca 
#2 0x7f8742024fc3 
#3 0x7f8742023c3b 
#4 0x7f8742024219 
#5 0x7f8741c6793a 
#6 0x7f8741c6ce76 
#7 0x7f874178a600 
#8 0x7f874178bb25 
#9 0x7f874171fa61 QtWebEngineCore::BrowserContextAdapter::defaultContext()
#10 0x7f87476d5218 QWebEngineProfile::defaultProfile()
#11 0x7f8747a15e78 MainApplication::MainApplication()
#12 0x0040358d main
#13 0x7f873c60f3d5 __libc_start_main
#14 0x004038d5 

Received signal 6
#0 0x7f87429cc0a5 
#1 0x7f874170d141 
#2 0x7f87429cc43d 
#3 0x7f873c623280 
#4 0x7f873c623207 __GI_raise
#5 0x7f873c6248f8 __GI_abort
#6 0x7f87429cbdc5 
#7 0x7f87429e21ed 
#8 0x7f8742024fc3 
#9 0x7f8742023c3b 
#10 0x7f8742024219 
#11 0x7f8741c6793a 
#12 0x7f8741c6ce76 
#13 0x7f874178a600 
#14 0x7f874178bb25 
#15 0x7f874171fa61 QtWebEngineCore::BrowserContextAdapter::defaultContext()
#16 0x7f87476d5218 QWebEngineProfile::defaultProfile()
#17 0x7f8747a15e78 MainApplication::MainApplication()
#18 0x0040358d main 
#19 0x7f873c60f3d5 __libc_start_main
#20 0x004038d5 
  r8: 7a136e50  r9: 7f873c741950 r10: 0008 r11:
0202
 r12: 7a136c20 r13: 00ac r14: 7a136e50 r15:
7a1375c0
  di: 45a4  si: 45a4  bp: 7f873d1d8320  bx:
7a1373a0
  dx: 0006  ax:   cx: 7f873c623207  sp:
7a136ab8
  ip: 7f873c623207 efl: 0202 cgf: 002b0033 erf:

 trp:  msk:  cr2:   
[end of stack trace]
Calling _exit(1). Core file will not be generated.

3. $

OBSERVED RESULT
Crashed

EXPECTED RESULT
Runned

SOFTWARE/OS VERSIONS
Linux: CentOS 7.6
KDE Plasma Version: KDE 4.14.8
KDE Frameworks Version: ?
Qt Version: 5.9.2

ADDITIONAL INFORMATION

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

[latte-dock] [Bug 403425] Notifications from system-tray widget not showing

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

--- Comment #23 from connectbha...@gmail.com ---
I compared both the new-user and current-user's home folder. Found that, the
current-user's `.config` folder, there is no latte folder (which has files like
Plasma.layout.latte, My Layout.layout.latte, etc). I copied the latte-folder
from the new-user to current-user's /home/.config folder. 

With this, I am able to make latte-panel appear again in the desktop :)

However, I checked --- still the notifications (kde-konnect ping) are not
coming.

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

[kate] [Bug 402586] Kate crashed after clicked somewhere in Kate main window

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

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

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

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

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

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

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

[Discover] [Bug 402464] Discover crashes on launch

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

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.

[plasma-browser-integration] [Bug 401598] Different icon set and plasma as name

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

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

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

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

[kmymoney] [Bug 402611] Select menu 'Settings>Configure KMyMoney' crashes program

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

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

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

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

[systemsettings] [Bug 402142] System Settings application crashes every time

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

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

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

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

[kdenlive] [Bug 388506] Crash when opening the modify clip dialog

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

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

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

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

[Spectacle] [Bug 402424] Active window with titlebars does not capture whole maximized window

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

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.

[latte-dock] [Bug 403611] New: Audio indicator volume change causes inconsistency and confusion

2019-01-25 Thread evea
https://bugs.kde.org/show_bug.cgi?id=403611

Bug ID: 403611
   Summary: Audio indicator volume change causes inconsistency and
confusion
   Product: latte-dock
   Version: 0.8.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: everm...@pc-portal.at
  Target Milestone: ---

If "Show indicator for audio streams" is enabled, there is an Audio Icon shown
on icons which have an active audio stream, which on its own is a great feature
as it is an indicator.

The problem is that it also changes the basic functionality of Latte dock. 
What I mean is that normally you hover over an icon and either scroll up to
open or scroll the application or down to just scroll through open
applications.

But if you have the feature enabled, you can accidentally hover over the small
indicator and it will change the volume of the application without indication,
instead of scrolling through the application as expected.
I personally only noticed this after realizing that all my applications are set
to different volumes, so I never knew this was actually an feature.

So this add confusion and inconsistency to expected workflow.


A good solution would be to add a sub option "change volume when scrolling",
which should not be enabled by default.

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

[latte-dock] [Bug 403425] Notifications from system-tray widget not showing

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

--- Comment #22 from connectbha...@gmail.com ---
(In reply to Michail Vourlakos from comment #21)
> ok, lets wait for some feedback

I just tried. With a new user, everything works fine:
1) latte-dock comes alive on the desktop when started through krunner
2) when system-panel widget is added, all notifications work, like e.g.
kde-konnect ping, low-battery indication.

So, looks like there is something missing/wrong in my main user-id. 

1. Can you help with me figure out what i should be looking at in my home
profile?
2. Is there a thorough reset (removing and reinstalling) of latte that I can
do? 

Note - I have already tried building the latte-dock from github package. That
didnt help. Also, I used the uninstall script in this package to remove
everything.

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

[plasmashell] [Bug 403542] Login Screen, the keyboard layout displays “us” whatever the current layout until a key is pressed

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

--- Comment #2 from 21na...@gmail.com ---
(In reply to David Edmundson from comment #1)
> That's not plasma, nor even plasma's SDDM theme.
It seems to be the display manager “sddm” with the theme “Debian Maui”.

Sorry for the inconvenience.

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

[okular] [Bug 403534] Wrong and misleading definition of a certificate’s subject

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

Albert Astals Cid  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||aa...@kde.org
 Resolution|--- |NOT A BUG

--- Comment #3 from Albert Astals Cid  ---
"I was confused and interpreted ‘The person/company that made the signature’ as
‘The person/company that made the certificate’ (which is the issuer)."

So yeah, not a bug.

If you're interested in trying it, see
https://tsdgeos.blogspot.com/2019/01/okular-pdf-signature-certificate.html

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

[okular] [Bug 403514] [Feature Request] advanced search - multiple strings at a time - match any of the words/strings

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

--- Comment #4 from Albert Astals Cid  ---
What you are suggesting is a new method of search for multiple groups of
strings at the same time, that'd be doable i guess, but don't see myself
implementing it.

You may want to open a new wish describing it in case someone has time to work
on it.

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

[umbrello] [Bug 403515] Ports on component diagram are randomly disappeared

2019-01-25 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=403515

--- Comment #9 from Ralf Habacker  ---
Another problem with this example is that in component "UserAdminAccounts"
ports are located inside the component, where in most other places ports are
located over the component border (see for example
https://www.uml-diagrams.org/port.html)  Moving such a ports let it jumps to
the top of the component.

A fix would be to adjust the vertical or horizontal position of such ports on
loading. If the port is located on top/bottom the vertical position need to be
adjusted and the horizontal position if located at the left/right border.

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

[frameworks-knewstuff] [Bug 391111] Rating doesn't work; all GHNS dialogs always display "Unknown Open Collaboration Service API error

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

Nate Graham  changed:

   What|Removed |Added

 CC||teamfes...@gmail.com

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

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

[okular] [Bug 403514] [Feature Request] advanced search - multiple strings at a time - match any of the words/strings

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

--- Comment #3 from vjera.t...@gmail.com ---
My bad, I should have put in more effort to find it. I'm using it now and it is
awesome. I'm sorry for the false alarm and thank you very much for Your answer.
It is not something I need right now, but could I make it work in case of "baby
lion", "baby zebra"? 

I went through Okular Handbook
(https://docs.kde.org/trunk5/en/kdegraphics/okular/okular.pdf) real quick and
haven't find any information on Thumbnail search, perhaps I missed it, but in
my opinion this could go under Advanced Features- but now I am no longer sure
if I've missed this feature in all or some of other Linux PDF readers I've
checked as well (in search of this particular feature), or they are relay not
offering it :| 

Thank you once again, I'm really happy it turned out my favorite PDF reader
already has this feature :)

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

[frameworks-attica] [Bug 388825] Collaboration API error - Cannot download icon theme

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

Nate Graham  changed:

   What|Removed |Added

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

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


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

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

[plasmashell] [Bug 403596] Slack tray icon not working in Plasma

2019-01-25 Thread Ryan
https://bugs.kde.org/show_bug.cgi?id=403596

--- Comment #6 from Ryan  ---
I also contacted Slack about this problem.  Seems they are working on a fix,
here is their response:

--

 Michelle Jones (Slack)

Jan 25, 11:16 AM PST

Hi there. This is the right place for a bug report, thanks for submitting it.
Our Linux team is actually already aware of this one and working on a fix for
it. I've added your ticket to the bug report so that as soon as it's fixed I
can let you know. I'm sorry for the inconvenience in the meantime.

Best,
Michelle

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

[kdelibs] [Bug 220656] libattica should not be required to build

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #1 from Nate Graham  ---
No longer relevant with Frameworks 5, since everything's now split into its own
package and only truly mandatory dependencies are marked as mandatory.

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

[umbrello] [Bug 403515] Ports on component diagram are randomly disappeared

2019-01-25 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=403515

Ralf Habacker  changed:

   What|Removed |Added

   Version Fixed In||2.27.2 (KDE Applications
   ||18.12.2)
 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/umb
   ||rello/bc435c590cf357818f99a
   ||1e9120a023e1ea5a380
 Resolution|--- |FIXED

--- Comment #7 from Ralf Habacker  ---
Git commit bc435c590cf357818f99a1e9120a023e1ea5a380 by Ralf Habacker.
Committed on 25/01/2019 at 23:47.
Pushed by habacker into branch 'Applications/18.12'.

When deleting port widgets, also delete the corresponding UML port
FIXED-IN:2.27.2 (KDE Applications 18.12.2)

M  +8-0umbrello/umlwidgets/portwidget.cpp

https://commits.kde.org/umbrello/bc435c590cf357818f99a1e9120a023e1ea5a380

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

[umbrello] [Bug 403515] Ports on component diagram are randomly disappeared

2019-01-25 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=403515

Ralf Habacker  changed:

   What|Removed |Added

   Version Fixed In||2.27.2 (KDE Applications
   ||18.12.2)
 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/umb
   ||rello/bc435c590cf357818f99a
   ||1e9120a023e1ea5a380
 Resolution|--- |FIXED

--- Comment #8 from Ralf Habacker  ---
Git commit f0afd735dc1aaf66da208951b96377a421b3653e by Ralf Habacker.
Committed on 25/01/2019 at 17:05.
Pushed by habacker into branch 'Applications/18.12'.

Fix center position for showing port widgets

Port widgets are childs of component widgets, for which pos() returns
local position. Therefore we need to use scenePos() to get the
absolute scene position.

M  +1-1umbrello/umllistview.cpp

https://commits.kde.org/umbrello/f0afd735dc1aaf66da208951b96377a421b3653e

--- Comment #7 from Ralf Habacker  ---
Git commit bc435c590cf357818f99a1e9120a023e1ea5a380 by Ralf Habacker.
Committed on 25/01/2019 at 23:47.
Pushed by habacker into branch 'Applications/18.12'.

When deleting port widgets, also delete the corresponding UML port
FIXED-IN:2.27.2 (KDE Applications 18.12.2)

M  +8-0umbrello/umlwidgets/portwidget.cpp

https://commits.kde.org/umbrello/bc435c590cf357818f99a1e9120a023e1ea5a380

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

[umbrello] [Bug 116354] Find in diagram function

2019-01-25 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=116354

--- Comment #12 from Ralf Habacker  ---
Git commit 3d476963180c3de82827c8e0963fbc03463b2669 by Ralf Habacker.
Committed on 25/01/2019 at 23:47.
Pushed by habacker into branch 'Applications/18.12'.

Add "show" and "properties" to context menu of tree view item types 'category'
and 'artifact'

M  +5-4umbrello/menus/umllistviewpopupmenu.cpp

https://commits.kde.org/umbrello/3d476963180c3de82827c8e0963fbc03463b2669

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

[frameworks-knewstuff] [Bug 403610] All GHNS dialogs always display "Unknown Open Collaboration Service API error. (999)" message on the bottom

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

Nate Graham  changed:

   What|Removed |Added

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

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


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

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

[frameworks-knewstuff] [Bug 391111] Rating doesn't work; all GHNS dialogs always display "Unknown Open Collaboration Service API error

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

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

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

[frameworks-knewstuff] [Bug 391111] Rating doesn't work; all GHNS dialogs always display "Unknown Open Collaboration Service API error

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

Nate Graham  changed:

   What|Removed |Added

   Priority|NOR |VHI
 CC||n...@kde.org
Summary|rating broken   |Rating doesn't work; all
   ||GHNS dialogs always display
   ||"Unknown Open Collaboration
   ||Service API error

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

[frameworks-knewstuff] [Bug 391111] Rating doesn't work; all GHNS dialogs always display "Unknown Open Collaboration Service API error

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

Nate Graham  changed:

   What|Removed |Added

 CC||malc...@whsg.info

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

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

[systemsettings] [Bug 397513] https://download.kde.org/ocs/providers.xml failed

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

--- Comment #6 from Nate Graham  ---


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

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

[systemsettings] [Bug 397513] https://download.kde.org/ocs/providers.xml failed

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

Nate Graham  changed:

   What|Removed |Added

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

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


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

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

[frameworks-knewstuff] [Bug 403610] All GHNS dialogs always display "Unknown Open Collaboration Service API error. (999)" message on the bottom

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

Nate Graham  changed:

   What|Removed |Added

 CC||malc...@whsg.info

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

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

[frameworks-knewstuff] [Bug 403610] New: All GHNS dialogs always display "Unknown Open Collaboration Service API error. (999)" message on the bottom

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

Bug ID: 403610
   Summary: All GHNS dialogs always display "Unknown Open
Collaboration Service API error. (999)" message on the
bottom
   Product: frameworks-knewstuff
   Version: 5.53.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jpwhit...@kde.org
  Reporter: n...@kde.org
CC: kdelibs-b...@kde.org
  Target Milestone: ---

In every GHNS dialog I've ever interacted with, on every distro, with every
plasma version, all of them have displayed an error message on the bottom that
says "Unknown Open Collaboration Service API error. (999)". It is reproducible
at will just by opening a GHNS dialog on Neon, Kubuntu, Manjaro, etc. There
doesn't seem to be any real adverse effect, since the content always loads just
fine.

We should make this stop, since it makes users nervous and reduces the
trustworthiness of KDE software in general and GHNS functionality in
particular.

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

[konversation] [Bug 403609] New: Znc password issue

2019-01-25 Thread Marco Londero
https://bugs.kde.org/show_bug.cgi?id=403609

Bug ID: 403609
   Summary: Znc password issue
   Product: konversation
   Version: 1.7.5
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konversation-de...@kde.org
  Reporter: the.sond...@gmail.com
  Target Milestone: ---

Hi, i've tried to log into my znc service but it was telling me that there was
an invalid password. I tried to change it removing the space character in it,
now i can log into znc without any problem. So the issue i think is due to the
blank space character.

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

[kmymoney] [Bug 403396] KMyMoney 5.0.2 crashes on import of OFX file

2019-01-25 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=403396

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #4 from Jack  ---
Is there any chance of compiling libofx with debug info?  That might give a
better idea of exactly what is causing the crash.

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

[kmymoney] [Bug 398133] Transaction types

2019-01-25 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=398133

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #8 from Jack  ---
If that Phabricator review (see comment #2) is committed (I just made a minor
comment) then should this be closed, or changed to a wishlist for the new
transaction type?

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

[kwin] [Bug 392412] KWin crash when KWin script handler for clientRemoved

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

--- Comment #9 from Vlad Zagorodniy  ---
Yes, it will be included in 5.15.

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

[kwin] [Bug 392412] KWin crash when KWin script handler for clientRemoved

2019-01-25 Thread Gonzalo Peci
https://bugs.kde.org/show_bug.cgi?id=392412

--- Comment #8 from Gonzalo Peci  ---
(In reply to Vlad Zagorodniy from comment #6)
> Git commit 8af6d4f5dc74385a9d52820562162dc190f452ff by Vlad Zagorodniy.
> Committed on 26/11/2018 at 08:50.
> Pushed by vladz into branch 'master'.
> 
> [x11] Emit clientRemoved after client was removed
> 
> Summary:
> Currently, there is a guarantee that a client, which is about to be removed,
> is no longer in the stacking order(both in constrained and unconstrained)
> when Workspace::removeClient is called. However, because the client gets
> removed from m_allClients after clientRemoved is emitted, it can be
> re-inserted back into the stacking order.
> 
> In general, the pattern is to do some work and then notify others about
> what you've done by emitting a signal. In the case of
> Workspace::removeClient,
> we emit clientRemoved way before the client actually gets removed.
> Related: bug 400854
> 
> Test Plan:
> * Enable the following script:
> 
> ```lang=js
> workspace.clientAdded.connect(function (client) {
> if (client.skipTaskbar || client.modal || client.transient) {
> return;
> }
> workspace.desktops = workspace.desktops + 1;
> workspace.currentDesktop = workspace.desktops;
> client.desktop = workspace.currentDesktop;
> });
> 
> workspace.clientRemoved.connect(function (client) {
> if (client.skipTaskbar || client.modal || client.transient) {
> return;
> }
> workspace.desktops = workspace.desktops - 1;
> });
> ```
> 
> * Open an app, close the app.
> 
> Reviewers: #kwin, graesslin
> 
> Reviewed By: #kwin, graesslin
> 
> Subscribers: graesslin, kwin
> 
> Tags: #kwin
> 
> Differential Revision: https://phabricator.kde.org/D17069
> 
> M  +2-2workspace.cpp
> 
> https://commits.kde.org/kwin/8af6d4f5dc74385a9d52820562162dc190f452ff

Do you know if this will be included in 15.5? Amazing that this was fix by the
way. Sorry I could not provide debug symbols.

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

[kmymoney] [Bug 403608] New: SaveAs defaults to "wrong" file path

2019-01-25 Thread JAH
https://bugs.kde.org/show_bug.cgi?id=403608

Bug ID: 403608
   Summary: SaveAs defaults to "wrong" file path
   Product: kmymoney
   Version: 5.0.0
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: file
  Assignee: kmymoney-de...@kde.org
  Reporter: vanques...@gmail.com
  Target Milestone: ---

SUMMARY:
When using "File > SaveAs" the offered path defaults to the last location a
file was saved to even if that path has nothing to do with origins of the
currently open file.

STEPS TO REPRODUCE
1. Open file /home/Jack/MyCash1.kmy
2. Save file
3. Open file /home/Dad/PaCash2.kmy
4. Use File > SaveAs 

OBSERVED RESULT
The SaveAs path defaults to /home/Jack/

EXPECTED RESULT
The SaveAs path should default to /home/Dad/ (which is the origin of the
currently open file and the standard GUI behaviour).

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Opensuse 15.1 with Plasma 5
(available in About System)
KDE Plasma Version: 5.12.6
KDE Frameworks Version: 5.45.0
Qt Version: 5.9.4.

ADDITIONAL INFORMATION
This exceptional behaviour is contrary to standard behaviour of SaveAs in other
desktop applications and consequently makes it easy to inadvertently write the
file to the wrong location (potentially overwriting identically named files
irrevocably).

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

[latte-dock] [Bug 403602] Circle Notification displays number if the Sound badge is already displayed

2019-01-25 Thread Viorel-Cătălin Răpițeanu
https://bugs.kde.org/show_bug.cgi?id=403602

--- Comment #7 from Viorel-Cătălin Răpițeanu  ---
This behaviour can be reproduced by setting the display scale to 1.5. I've
tested this both on my machine and in the VM and it's reproducible.

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

[kdeconnect] [Bug 403607] [Test] Crash report test

2019-01-25 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=403607

Nicolas Fella  changed:

   What|Removed |Added

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

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

[kdeconnect] [Bug 403607] New: [Test] Crash report test

2019-01-25 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=403607

Bug ID: 403607
   Summary: [Test] Crash report test
   Product: kdeconnect
   Version: 1.3.3
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: nicolas.fe...@gmx.de
  Target Milestone: ---

Application: kdeconnectd (1.3.3)

Qt Version: 5.12.0
Frameworks Version: 5.54.0
Operating System: Linux 4.19.16-1-MANJARO x86_64
Distribution: "Manjaro Linux"

-- Information about the crash:
- What I was doing when the application crashed: kill -SEGV $(pidof
kdeconnectd)

Foo

ewkncwec
wec
wec
ewc
wec
wec
we
cwe
cwe
cw
ec
wec
wec
we
cwe

The crash can be reproduced every time.

-- Backtrace:
Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd935912800 (LWP 8736))]

Thread 4 (Thread 0x7fd9319f1700 (LWP 8739)):
#0  0x7fd93a7b2985 in ?? () from /usr/lib/libQt5Core.so.5
#1  0x7fd938b25e0a in g_main_context_prepare () from
/usr/lib/libglib-2.0.so.0
#2  0x7fd938b26466 in ?? () from /usr/lib/libglib-2.0.so.0
#3  0x7fd938b2662e in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#4  0x7fd93a7b2a54 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#5  0x7fd93a75b8bc in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#6  0x7fd93a59f579 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#7  0x7fd93a5a097c in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7fd939966a9d in start_thread () from /usr/lib/libpthread.so.0
#9  0x7fd93a0ebb23 in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7fd9321f2700 (LWP 8738)):
#0  0x7fd938b543c7 in g_ptr_array_set_size () from
/usr/lib/libglib-2.0.so.0
#1  0x7fd938b25cf6 in g_main_context_prepare () from
/usr/lib/libglib-2.0.so.0
#2  0x7fd938b26466 in ?? () from /usr/lib/libglib-2.0.so.0
#3  0x7fd938b2662e in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#4  0x7fd93a7b2a54 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#5  0x7fd93a75b8bc in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#6  0x7fd93a59f579 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#7  0x7fd93aa27ba6 in ?? () from /usr/lib/libQt5DBus.so.5
#8  0x7fd93a5a097c in ?? () from /usr/lib/libQt5Core.so.5
#9  0x7fd939966a9d in start_thread () from /usr/lib/libpthread.so.0
#10 0x7fd93a0ebb23 in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7fd9344a6700 (LWP 8737)):
#0  0x7fd93a0e0c21 in poll () from /usr/lib/libc.so.6
#1  0x7fd9389ae630 in ?? () from /usr/lib/libxcb.so.1
#2  0x7fd9389b02db in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7fd9354698c9 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#4  0x7fd93a5a097c in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7fd939966a9d in start_thread () from /usr/lib/libpthread.so.0
#6  0x7fd93a0ebb23 in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7fd935912800 (LWP 8736)):
[KCrash Handler]
#6  0x7fd93a0e0c21 in poll () from /usr/lib/libc.so.6
#7  0x7fd938b26540 in ?? () from /usr/lib/libglib-2.0.so.0
#8  0x7fd938b2662e in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#9  0x7fd93a7b2a39 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#10 0x7fd93a75b8bc in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#11 0x7fd93a763bc6 in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#12 0x5624ae22667d in main ()
[Inferior 1 (process 8736) detached]

Possible duplicates by query: bug 403391, bug 403101, bug 403058, bug 402924,
bug 402799.

Reported using DrKonqi

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

[kwin] [Bug 403601] KWin crash on boot

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

Vlad Zagorodniy  changed:

   What|Removed |Added

 Resolution|--- |BACKTRACE
 Status|REPORTED|NEEDSINFO

--- Comment #1 from Vlad Zagorodniy  ---
> Application: kwin_x11 (5.8.9)

Hmm, this is quite old KDE Plasma version. Can you reproduce the crash in more
modern versions?

Apparently the crash happens somewhere in libxcb, though it would be great to
have a backtrace with debug symbols.

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

[latte-dock] [Bug 403602] Circle Notification displays number if the Sound badge is already displayed

2019-01-25 Thread Viorel-Cătălin Răpițeanu
https://bugs.kde.org/show_bug.cgi?id=403602

--- Comment #6 from Viorel-Cătălin Răpițeanu  ---
It looks like the NVidia proprietary driver doesn't use 96 as DPI. This is...
amusing... :D

If I'm forcing my kwin to use 96 as DPI, this issue doesn't happen anymore. So
forcing a different DPI (probably higher) will trigger this issue? I have to
look on this a bit more. However, everything is looking as expected right now
(size-wise).

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

[digikam] [Bug 256714] Add export to screenshots.debian.net

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

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

   What|Removed |Added

  Component|Export-WishForNewTools  |Export-DebianScreenshots

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

[kwin] [Bug 403606] KWin freezes when opening multiple modal windows

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

Vlad Zagorodniy  changed:

   What|Removed |Added

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

--- Comment #1 from Vlad Zagorodniy  ---
Works fine for me.

- Can open yakuake, for example, but its UI does not update
- Switch to other tty, pkill qbittorrent, switch back, everything goes back to
normal

If KWin were "frozen", then you wouldn't be able to see Yakuake.

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

[digikam] [Bug 340934] Crash while starting image viewer with pictures selected by stars

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

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

   What|Removed |Added

  Component|Portability |Export-GLViewer

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

[digikam] [Bug 249072] Crash under kubuntu 10.04

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

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

   What|Removed |Added

  Component|Portability |Export-GLViewer

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

[digikam] [Bug 243381] signal: Segmentation fault

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

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

   What|Removed |Added

  Component|Portability |Export-GLViewer

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

[digikam] [Bug 202637] Crash trying to start export tool

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

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

   What|Removed |Added

  Component|Portability |Export-GLViewer

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

[okular] [Bug 403514] [Feature Request] advanced search - multiple strings at a time - match any of the words/strings

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

Albert Astals Cid  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 CC||aa...@kde.org
 Status|REPORTED|RESOLVED

--- Comment #2 from Albert Astals Cid  ---
Or you could use the thumbnail search feature that has exactly what you want

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

[digikam] [Bug 256544] Image viewer crash report

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

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

   What|Removed |Added

  Component|Portability |Export-GLViewer

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

[okular] [Bug 377460] Please add ability to "Edit metadata (document info)

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

Albert Astals Cid  changed:

   What|Removed |Added

 CC||el...@lattash.uk

--- Comment #2 from Albert Astals Cid  ---
*** Bug 403521 has been marked as a duplicate of this bug. ***

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

[okular] [Bug 403521] Provide ability to edit pdf metadata

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

Albert Astals Cid  changed:

   What|Removed |Added

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

--- Comment #2 from Albert Astals Cid  ---


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

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

[latte-dock] [Bug 403605] Firefox as a default pinned application for all layouts

2019-01-25 Thread Viorel-Cătălin Răpițeanu
https://bugs.kde.org/show_bug.cgi?id=403605

--- Comment #2 from Viorel-Cătălin Răpițeanu  ---
(In reply to Michail Vourlakos from comment #1)
> This is distros responsibility...
> 
> Latte provides presets which are simple text-based latte layout files. Any
> distro can alter these presets to its own liking...
> 
> the presets files can be found at: "shell/package/contents/presets/"

Yes, I've already taken a look at them. That's why I wasn't even sure you
should do/can do something about this.

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

[kwin] [Bug 403606] New: KWin freezes when opening multiple modal windows

2019-01-25 Thread José Rebelo
https://bugs.kde.org/show_bug.cgi?id=403606

Bug ID: 403606
   Summary: KWin freezes when opening multiple modal windows
   Product: kwin
   Version: 5.14.5
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: core
  Assignee: kwin-bugs-n...@kde.org
  Reporter: josereb...@outlook.com
  Target Milestone: ---

SUMMARY
The entire window manager becomes unresponsive when opening multiple modal
windows at the same time (for example, with qBittorrent, haven't tried to
reproduce with other programs).

STEPS TO REPRODUCE
1. Open qBittorrent
2. Click a magnet link on your web browser (a modal window opens)
3. Without closing the previous window, click a second magnet (a second modal
window opens)

OBSERVED RESULT
- Everything freezes, can't open application launcher / interact with windows
- Can open yakuake, for example, but its UI does not update
- Switch to other tty, pkill qbittorrent, switch back, everything goes back to
normal

EXPECTED RESULT
- Kwin not to freeze

SOFTWARE/OS VERSIONS
Arch Linux x64, updated
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.12.0

ADDITIONAL INFORMATION
Xorg, no DM (only xinit)

Apologies if this issue is in the wrong category / duplicated. I searched
around and did not find anything similar.

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

[latte-dock] [Bug 403602] Circle Notification displays number if the Sound badge is already displayed

2019-01-25 Thread Viorel-Cătălin Răpițeanu
https://bugs.kde.org/show_bug.cgi?id=403602

--- Comment #5 from Viorel-Cătălin Răpițeanu  ---
(In reply to Michail Vourlakos from comment #4)
> (In reply to Viorel-Cătălin Răpițeanu from comment #3)
> > I've retried this using the git repo and the issue can still be seen. This
> > is interesting...
> 
> probably you play with it in your system and see what is causing it

I've retried this in a newly created VM using the same os and software and it
seems that you are right. This behaviour can't be seen there. Not only this,
but it looks that the badges length and font size is very different.
On my Machine using the NVidia proprietary drivers, the badges are way wider
and the font is way bigger (as it can probably be observed from the video).

The interesting part is that the scaling in both machines are set to 1 (don't
magnify)... I'll take a closer look at this issue and I'll update the ticket as
soon as I find something.

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

[kpat] [Bug 403564] Solver in Grandfather reports winnable games as unwinnable

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

Albert Astals Cid  changed:

   What|Removed |Added

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

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

[Falkon] [Bug 402805] Right and middle mouse don't work sometimes

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

--- Comment #4 from k...@trummer.xyz ---
There is no pattern of sites where it happens, but it only seems to happen
after a while of having Falkon open.

So, a tab will start not registering right/middle clicks anymore, but when I
restart Falkon, right/middle clicks in that tab work.

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

[latte-dock] [Bug 403605] Firefox as a default pinned application for all layouts

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

Michail Vourlakos  changed:

   What|Removed |Added

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

--- Comment #1 from Michail Vourlakos  ---
This is distros responsibility...

Latte provides presets which are simple text-based latte layout files. Any
distro can alter these presets to its own liking...

the presets files can be found at: "shell/package/contents/presets/"

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

[latte-dock] [Bug 403605] New: Firefox as a default pinned application for all layouts

2019-01-25 Thread Viorel-Cătălin Răpițeanu
https://bugs.kde.org/show_bug.cgi?id=403605

Bug ID: 403605
   Summary: Firefox as a default pinned application for all
layouts
   Product: latte-dock
   Version: git (master)
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: rapiteanu.cata...@gmail.com
  Target Milestone: ---

SUMMARY
By default, all layouts use Firefox as a pinned application. Some systems (like
Arch Linux) don't install Firefox with KDE since Firefox is not part of the KDE
ecosistem.

STEPS TO REPRODUCE
1. Use any default layouts. They all have firefox as a pinned application, even
if firefox is not installed on the system.

OBSERVED RESULT
Each layout have an invalid firefox.desktop application to  the dock.

EXPECTED RESULT
Honestly, I have no ideea. I'm not sure you should even care if firefox is
installed. This is the user's/distro-maker's job. I'm not sure you could do
something about this even if you wanted...


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.14.90
KDE Plasma Version: 5.14.90
KDE Frameworks Version: 5.54.0
Qt Version: 5.12.0-3

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

[Discover] [Bug 403544] Arrow (→) is displayed as box in package update descriptions

2019-01-25 Thread Øystein Steffensen-Alværvik
https://bugs.kde.org/show_bug.cgi?id=403544

--- Comment #3 from Øystein Steffensen-Alværvik  ---
Ah, yes, you're right, thanks for the diligence. I can confirm that my system
cannot display that specific symbol.

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

[kmymoney] [Bug 403487] No bankdata for payeeidentifier_iban_bic available

2019-01-25 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=403487

--- Comment #1 from Ralf Habacker  ---
Git commit 59e70ffa6d93cc279bd6aca0a741ca56b5ecb036 by Ralf Habacker.
Committed on 25/01/2019 at 21:40.
Pushed by habacker into branch '4.8-alkimia-onlinequote'.

Add actual bankdata files to not been bound on internet access for generating
sqlite database

A  +16434 -0kmymoney/plugins/ibanbicdata/germany/bankdata.de.txt
A  +3329 -0kmymoney/plugins/ibanbicdata/switzerland/bankdata.ch.txt

https://commits.kde.org/kmymoney/59e70ffa6d93cc279bd6aca0a741ca56b5ecb036

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

[kmymoney] [Bug 403487] No bankdata for payeeidentifier_iban_bic available

2019-01-25 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=403487

--- Comment #2 from Ralf Habacker  ---
Git commit 76334b052397119d2a0cc27a90d3987bf642bf05 by Ralf Habacker.
Committed on 25/01/2019 at 21:40.
Pushed by habacker into branch '4.8-alkimia-onlinequote'.

Restore support for generating bank data sqlite databases

M  +2-0kmymoney/payeeidentifier/ibanandbic/CMakeLists.txt
M  +3-1kmymoney/payeeidentifier/ibanandbic/ibanbicdata.h
M  +10   -12  
kmymoney/payeeidentifier/ibanandbic/tests/internationalaccountidentifiertest.cpp
M  +2-2kmymoney/plugins/ibanbicdata/CMakeLists.txt
M  +23   -1kmymoney/plugins/ibanbicdata/germany/CMakeLists.txt
M  +1-1kmymoney/plugins/ibanbicdata/germany/germany.py
M  +24   -2kmymoney/plugins/ibanbicdata/switzerland/CMakeLists.txt

https://commits.kde.org/kmymoney/76334b052397119d2a0cc27a90d3987bf642bf05

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

[latte-dock] [Bug 403602] Circle Notification displays number if the Sound badge is already displayed

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

--- Comment #4 from Michail Vourlakos  ---
(In reply to Viorel-Cătălin Răpițeanu from comment #3)
> I've retried this using the git repo and the issue can still be seen. This
> is interesting...

probably you play with it in your system and see what is causing it

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

[latte-dock] [Bug 403602] Circle Notification displays number if the Sound badge is already displayed

2019-01-25 Thread Viorel-Cătălin Răpițeanu
https://bugs.kde.org/show_bug.cgi?id=403602

--- Comment #3 from Viorel-Cătălin Răpițeanu  ---
I've retried this using the git repo and the issue can still be seen. This is
interesting...

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

[kontact] [Bug 403604] New: kmail does not update main message body area when showing empty email (keeps previous email body)

2019-01-25 Thread Jens
https://bugs.kde.org/show_bug.cgi?id=403604

Bug ID: 403604
   Summary: kmail does not update main message body area when
showing empty email (keeps previous email body)
   Product: kontact
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: mail
  Assignee: kdepim-b...@kde.org
  Reporter: jens-bugs.kde@spamfreemail.de
  Target Milestone: ---

SUMMARY
kmail does not display mail (at all) when it has no content, even if
attachments exist.

STEPS TO REPRODUCE
1. create empty plain text mail with attachment (7z file in my case) from MS
Outlook 2016 (in my case, I don't know if this matters)
2. send this to kmail account
3. view with kmail

OBSERVED RESULT
kmail does not display, but also does not empty, the message body area. It just
keeps displaying the previously displayed message

EXPECTED RESULT
kmail should show an empty message body and the attachment area (or an icon for
the attachment(s)). 

SOFTWARE/OS VERSIONS
Windows: -
MacOS: -
Linux/KDE Plasma: KDE Neon 18.04 with all updates applied, KMail 5.10.1
(available in About System)

ADDITIONAL INFORMATION

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

[latte-dock] [Bug 403419] [feature] Manually choose the dark/light color

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

Michail Vourlakos  changed:

   What|Removed |Added

   Severity|normal  |wishlist
Summary|[Feature request] Manually  |[feature] Manually choose
   |choose the dark/light color |the dark/light color

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

[latte-dock] [Bug 403023] [feature] - items overlap when there are too many widgets on the dock

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

Michail Vourlakos  changed:

   What|Removed |Added

   Severity|normal  |wishlist

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

[latte-dock] [Bug 403023] [feature] - items overlap when there are too many widgets on the dock

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

--- Comment #6 from Michail Vourlakos  ---
(In reply to Savor d'Isavano from comment #5)
> (In reply to Michail Vourlakos from comment #4)
> > (In reply to Savor d'Isavano from comment #3)
> > > (In reply to Savor d'Isavano from comment #2)
> > > > (In reply to Michail Vourlakos from comment #1)
> left/right edges the content will scroll. (I'm okay with mouse wheel too).

sounds ok for me... I will leave it open for some time in case someone tries to
implement this... personally I am not that much interested

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

[latte-dock] [Bug 403425] Notifications from system-tray widget not showing

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

Michail Vourlakos  changed:

   What|Removed |Added

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

--- Comment #21 from Michail Vourlakos  ---
ok, lets wait for some feedback

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

[latte-dock] [Bug 403023] [feature] - items overlap when there are too many widgets on the dock

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

Michail Vourlakos  changed:

   What|Removed |Added

Summary|Items overlap when there|[feature] - items overlap
   |are too many widgets on the |when there are too many
   |dock|widgets on the dock

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

[dolphin] [Bug 403603] New: Dolphin crashea cuando mueve archivos hacia una partición NTFS

2019-01-25 Thread Abel Sendon
https://bugs.kde.org/show_bug.cgi?id=403603

Bug ID: 403603
   Summary: Dolphin crashea cuando mueve archivos hacia una
partición NTFS
   Product: dolphin
   Version: 17.12.3
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: abelnicolas1...@gmail.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

Application: dolphin (17.12.3)
 (Compiled from sources)
Qt Version: 5.9.5
Frameworks Version: 5.44.0
Operating System: Linux 4.15.0-43-generic x86_64
Distribution: Ubuntu 18.04.1 LTS

-- Information about the crash:
Todas las veces que se mueve uno o más archivos, dolphin se cierra al terminar
la operación cuando la particion de destino es del tipo NTFS.

Cuando es del tipo exfat manda el siguiente mensaje: 
"Acceso denegado a  /nombre/del/archivo/copiado"
pero en este caso no se cierra.

El archivo de origen en ambos casos está en una particion ext4, y también la
operación concluye correctamente.

The crash can be reproduced every time.

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

Thread 3 (Thread 0x7f7f969d9700 (LWP 9983)):
#0  0x7f7fbdcd8bf9 in __GI___poll (fds=0x7f7f900049b0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f7fb0c34539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f7fb0c3464c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f7fb7eec90b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f7fb7e919ea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f7fb7cb022a in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f7fb7cb516d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f7fb2da56db in start_thread (arg=0x7f7f969d9700) at
pthread_create.c:463
#8  0x7f7fbdce588f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f7f9700 (LWP 9981)):
#0  0x7f7fbdcd8bf9 in __GI___poll (fds=0x7f7f9801ab90, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f7fb0c34539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f7fb0c3464c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f7fb7eec90b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f7fb7e919ea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f7fb7cb022a in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f7fb8369d45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f7fb7cb516d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f7fb2da56db in start_thread (arg=0x7f7f9700) at
pthread_create.c:463
#9  0x7f7fbdce588f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f7fbe44b6c0 (LWP 9979)):
[KCrash Handler]
#6  0x7f7fb9845a94 in KJob::isAutoDelete() const () from
/usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#7  0x7f7fb9845ae1 in KJob::finishJob(bool) () from
/usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#8  0x7f7fbc2322f9 in KIO::FileCopyJob::slotResult(KJob*) () from
/usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#9  0x7f7fb7ec26cf in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f7fb9844fdc in KJob::result(KJob*, KJob::QPrivateSignal) () from
/usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#11 0x7f7fb9845b11 in KJob::finishJob(bool) () from
/usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#12 0x7f7fbc241628 in KIO::SimpleJob::slotFinished() () from
/usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#13 0x7f7fbc23f9db in KIO::SimpleJob::slotError(int, QString const&) ()
from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#14 0x7f7fb7ec26cf in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7f7fbc217186 in KIO::SlaveInterface::error(int, QString const&) ()
from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#16 0x7f7fbc21b222 in KIO::SlaveInterface::dispatch(int, QByteArray const&)
() from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#17 0x7f7fbc217807 in KIO::SlaveInterface::dispatch() () from
/usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#18 0x7f7fbc21cd01 in KIO::Slave::gotInput() () from
/usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#19 0x7f7fb7ec25b5 in QMetaObject::activate(QObject*, int, int, void**) ()
from 

[latte-dock] [Bug 401184] Latte Dock - Global Keyboard Shortcuts Stop Working / Multiple Entries Created

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

Michail Vourlakos  changed:

   What|Removed |Added

   Severity|normal  |major

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

[latte-dock] [Bug 403600] Smoth animation when the notification badge is shrinking to a circle and the sound badge appears

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

Michail Vourlakos  changed:

   What|Removed |Added

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

--- Comment #1 from Michail Vourlakos  ---
sounds logical but I think that this one wouldnt work out well for two reasons:

1. Animate the badge is easy but it should animate also the opengl mask that
"eats" the icon in order for the animation to llok nice

2. [1] is dangerous for crashes in many cases so I could live with the current
implementation

of course you are free to experiment with this and report back your findings

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

[latte-dock] [Bug 403602] Circle Notification displays number if the Sound badge is already displayed

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

--- Comment #2 from Michail Vourlakos  ---
sorry cant reproduce that one

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

[latte-dock] [Bug 403602] Circle Notification displays number if the Sound badge is already displayed

2019-01-25 Thread Viorel-Cătălin Răpițeanu
https://bugs.kde.org/show_bug.cgi?id=403602

--- Comment #1 from Viorel-Cătălin Răpițeanu  ---
Video of the issue (with sound!):
https://drive.google.com/open?id=1EfGPw4YjNz4VzzFTDsWyFoXUMeoEGGhZ

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

[latte-dock] [Bug 403602] New: Circle Notification displays number if the Sound badge is already displayed

2019-01-25 Thread Viorel-Cătălin Răpițeanu
https://bugs.kde.org/show_bug.cgi?id=403602

Bug ID: 403602
   Summary: Circle Notification displays number if the Sound badge
is already displayed
   Product: latte-dock
   Version: git (master)
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: rapiteanu.cata...@gmail.com
  Target Milestone: ---

SUMMARY
Circle Notification will display the selected number if the Sound badge is
already displayed.

STEPS TO REPRODUCE
1. Open an application that already plays sound (like chromium).
2. Add a notification to that application

OBSERVED RESULT
The notification number is being displayed inside the circle notification.

EXPECTED RESULT
Only the circle notification should appear.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.14.90
KDE Plasma Version: 5.14.90
KDE Frameworks Version: 5.54.0
Qt Version: 5.12.0-3

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

[krita] [Bug 403576] Cannot edit transparency masks as greyscale images

2019-01-25 Thread Brendan
https://bugs.kde.org/show_bug.cgi?id=403576

Brendan  changed:

   What|Removed |Added

 Resolution|NOT A BUG   |---
 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED

--- Comment #2 from Brendan  ---
I can't do that either. When I click on the preview for the global selection
mask, the exact same problem occurs; I can paint to the mask but not see it in
greyscale. I thought they were similar enough to fall under the same bug, but I
can setup a separate bug if you think it won't just get closed as duplicate.

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

[kwin] [Bug 403601] New: KWin crash on boot

2019-01-25 Thread tai133
https://bugs.kde.org/show_bug.cgi?id=403601

Bug ID: 403601
   Summary: KWin crash on boot
   Product: kwin
   Version: 5.8.9
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: tsi...@wavecable.com
  Target Milestone: ---

Application: kwin_x11 (5.8.9)
 (Compiled from sources)
Qt Version: 5.6.1
Frameworks Version: 5.36.0
Operating System: Linux 4.4.0-141-generic x86_64
Distribution: Ubuntu 16.04.5 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Booting virtualbox guest after extended (45 day) shutdown

-- Backtrace:
Application: KWin (kwin_x11), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7fd182394940 (LWP 2641))]

Thread 5 (Thread 0x7fd16099f700 (LWP 2739)):
[KCrash Handler]
#6  0x7fd181dc3428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7fd181dc502a in __GI_abort () at abort.c:89
#8  0x7fd17fabbf41 in QMessageLogger::fatal(char const*, ...) const () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fd162c211b4 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.platforms/KWinX11Platform.so
#10 0x7fd17fcd5c24 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7fd17fce20b8 in QTimer::timerEvent(QTimerEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7fd17fcd66d3 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7fd1805deafc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x7fd1805e4036 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x7fd17fca92a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7fd17fcfd24e in QTimerInfoList::activateTimers() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7fd17fcfbb04 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x7fd17fca6ffa in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x7fd17facf9e4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7fd17fad4808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x7fd17bb456ba in start_thread (arg=0x7fd16099f700) at
pthread_create.c:333
#22 0x7fd181e9541d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7fd1619a0700 (LWP 2728)):
#0  0x7fd17fcaaf27 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7fd17fcfba02 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fd17fca6ffa in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7fd17facf9e4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fd17ac9f6b5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#5  0x7fd17fad4808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fd17bb456ba in start_thread (arg=0x7fd1619a0700) at
pthread_create.c:333
#7  0x7fd181e9541d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fd163640700 (LWP 2694)):
#0  __libc_disable_asynccancel () at
../sysdeps/unix/sysv/linux/x86_64/cancellation.S:98
#1  0x7fd181e8b5df in select () at ../sysdeps/unix/syscall-template.S:84
#2  0x7fd17fcf9bcf in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7fd17fcfb60e in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fd17fcfbb22 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fd17fca6ffa in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fd17facf9e4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fd1824bc515 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#8  0x7fd17fad4808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fd17bb456ba in start_thread (arg=0x7fd163640700) at
pthread_create.c:333
#10 0x7fd181e9541d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fd16931e700 (LWP 2676)):
#0  0x7fd181e8974d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  

[latte-dock] [Bug 403598] The panel shuffles the position of all pinned and unpinned applications

2019-01-25 Thread Viorel-Cătălin Răpițeanu
https://bugs.kde.org/show_bug.cgi?id=403598

--- Comment #4 from Viorel-Cătălin Răpițeanu  ---
(In reply to Michail Vourlakos from comment #3)
> This is a plasma libtaskmanager issue that needs to be reported upstream if
> there is a way to reproduce with plasma taskmanagers

I'm not exactly sure how can I reproduce this issue using plasma's
taskmanagers...

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

[latte-dock] [Bug 403600] New: Smoth animation when the notification badge is shrinking to a circle and the sound badge appears

2019-01-25 Thread Viorel-Cătălin Răpițeanu
https://bugs.kde.org/show_bug.cgi?id=403600

Bug ID: 403600
   Summary: Smoth animation when the notification badge is
shrinking to a circle and the sound badge appears
   Product: latte-dock
   Version: git (master)
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: plasmoid
  Assignee: mvourla...@gmail.com
  Reporter: rapiteanu.cata...@gmail.com
  Target Milestone: ---

SUMMARY
The smooth transition would look a bit better for the moment when the
notification bar is shrinking to a circle position and the sound badge apears.
I think that this is the only transition that is missing.

STEPS TO REPRODUCE
1. Chromium with a 9 notification badge.
2. Make Chromium play a song.

OBSERVED RESULT
1. The Notification badge is instantly conversed into a circle without any kind
of transition in between.

EXPECTED RESULT
1. The should be a transition between the 2 final states.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.14.90
KDE Plasma Version: 5.14.90
KDE Frameworks Version: 5.54.0
Qt Version: 5.12.0-3

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

[krita] [Bug 403599] New: Append .paintingassistant extension by default

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

Bug ID: 403599
   Summary: Append .paintingassistant extension by default
   Product: krita
   Version: 4.1.7
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Tool/Assistants
  Assignee: krita-bugs-n...@kde.org
  Reporter: b...@beuc.net
  Target Milestone: ---

SUMMARY

STEPS TO REPRODUCE

When saving an assistant, I didn't know what extension to use.
I left it blank expecting Krita to fill in for me.

OBSERVED RESULT

Instead there was no extension ("test" input -> "test." file).

More importantly: when trying to open said assistant, Krita would filter the
extensions to either "Krita Assistant", without letting me know what extension
it was looking for, or "Support files", which filters "test." as well as other
extensions I tried (e.g. ".assistant"). I had to copy/paste the exact filename
to make Krita open it.

I eventually found the ".paintingassistant" extension by chance in a 3rd-party
tutorial video.

EXPECTED RESULT

1. Krita fills in the .paintingassistant when saving an assistant
2. Krita offers the option to open any extension when loading an assistant
3. Krita mentions the .paintingassistant in the file type, e.g. "Krita
Assistant (*.paintingassistant)", rather than just "Krita Assistant"

Incidentally
4. The file dialog title ("Save Assistant") is translated in French as
"Assistant for Saving" rather than "Saving the Assistant" - not sure where to
report this :)

SOFTWARE/OS VERSIONS
Krita 4.1 branch / GNU/Linux

ADDITIONAL INFORMATION

I looked in the code and saw that parts of Krita use QFileDialog (which could
use setDefaultSuffix for this simple case), but this save dialog uses
KoFileDialog - so I'm not sure how this should be fixed.

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

[latte-dock] [Bug 403598] The panel shuffles the position of all pinned and unpinned applications

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

--- Comment #3 from Michail Vourlakos  ---
This is a plasma libtaskmanager issue that needs to be reported upstream if
there is a way to reproduce with plasma taskmanagers

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

[latte-dock] [Bug 403598] The panel shuffles the position of all pinned and unpinned applications

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

--- Comment #2 from Michail Vourlakos  ---
This is a plasma libtaskmanager issue that needs to be reported upstream if
there is a way to reproduce with plasma taskmanagers

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

[digikam] [Bug 403456] Export to Dropbox: New Album in Dropbox not visible

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

--- Comment #6 from Maik Qualmann  ---
Git commit aa6952465e5b8865df79158a0664fdd75ae6cac3 by Maik Qualmann.
Committed on 25/01/2019 at 20:39.
Pushed by mqualmann into branch 'master'.

read next Dropbox folder list if available

M  +57   -23   core/utilities/assistants/webservices/dropbox/dbtalker.cpp
M  +1-1core/utilities/assistants/webservices/dropbox/dbtalker.h

https://commits.kde.org/digikam/aa6952465e5b8865df79158a0664fdd75ae6cac3

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

[latte-dock] [Bug 403598] The panel shuffles the position of all pinned and unpinned applications

2019-01-25 Thread Viorel-Cătălin Răpițeanu
https://bugs.kde.org/show_bug.cgi?id=403598

--- Comment #1 from Viorel-Cătălin Răpițeanu  ---
Video of the issue:
https://drive.google.com/open?id=1CgoLXPHfpClDgDnDts-QC-l9w31nmy-4

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

[latte-dock] [Bug 403598] New: The panel shuffles the position of all pinned and unpinned applications

2019-01-25 Thread Viorel-Cătălin Răpițeanu
https://bugs.kde.org/show_bug.cgi?id=403598

Bug ID: 403598
   Summary: The panel shuffles the position of all pinned and
unpinned applications
   Product: latte-dock
   Version: git (master)
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: rapiteanu.cata...@gmail.com
  Target Milestone: ---

SUMMARY
When the Latte Dock is restarted, the position of all pinned and unpinned
applications are shuffled. This is restored when the applications are focused
again.

STEPS TO REPRODUCE
1. Stop the Latte Dock. # kill -2 $(pgrep latte)  
2. Launch again the Latte Dock.

OBSERVED RESULT
1. The position of all pinned and unpinned applications are shuffled


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.14.90
KDE Plasma Version: 5.14.90
KDE Frameworks Version: 5.54.0
Qt Version: 5.12.0-3

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

[akregator] [Bug 398516] UI - Akregator comments section font seems to be hard coded. Font is tiny on a 4k monitor

2019-01-25 Thread walter
https://bugs.kde.org/show_bug.cgi?id=398516

--- Comment #4 from walter  ---
I attatched a screenshot of Kontact with Akregator open, and the font
selection setup. Note the comments under "Read more of this story" font is
perhaps half the size of my font selection, and I can't change it.


On Fri, Jan 18, 2019 at 8:33 PM Bug Janitor Service <
bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=398516
>
> --- 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 reported the bug.

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

[kate] [Bug 403583] Backup on save prefix/suffix as contextually determined string, e.g. a timestamp

2019-01-25 Thread Kåre Särs
https://bugs.kde.org/show_bug.cgi?id=403583

Kåre Särs  changed:

   What|Removed |Added

 CC||kare.s...@iki.fi
   Severity|normal  |wishlist

--- Comment #2 from Kåre Särs  ---
Thanks! I think it is a good wish :)

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

[kmymoney] [Bug 394780] Make 4.8.3 release

2019-01-25 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=394780
Bug 394780 depends on bug 384985, which changed state.

Bug 384985 Summary: Incomplete german translation of stable kmymoney
https://bugs.kde.org/show_bug.cgi?id=384985

   What|Removed |Added

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

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

[plasmashell] [Bug 403596] Slack tray icon not working in Plasma

2019-01-25 Thread Ryan
https://bugs.kde.org/show_bug.cgi?id=403596

--- Comment #5 from Ryan  ---
(In reply to Ryan from comment #4)
> (In reply to David Edmundson from comment #3)
> > Oh, that's good news.
> > 
> > Next:
> > 
> > Run
> > 
> >  qdbus org.kde.StatusNotifierWatcher /StatusNotifierWatcher
> > org.kde.StatusNotifierWatcher.RegisteredStatusNotifierItems 
> > 
> > 
> > That'll give you a list in the form
> > 
> > :1.32/StatusNotifierItem
> > 
> > 
> > Run 
> > 
> > qdbus :1.32 /StatusNotifierItemorg.kde.StatusNotifierItem.Title
> > qdbus :1.32 /StatusNotifierItem   
> > org.kde.StatusNotifierItem.AttentionIconName
> > qdbus :1.32 /StatusNotifierItemorg.kde.StatusNotifierItem.IconName
> > qdbus :1.32 /StatusNotifierItemorg.kde.StatusNotifierItem.IconTheme
> > qdbus :1.32 /StatusNotifierIte
> > org.kde.StatusNotifierItem.IconThemePath
> > qdbus :1.32 /StatusNotifierIte org.kde.StatusNotifierItem.Status
> > 
> > (where :1.32 and potentially "/StatusNotifierItem" are from that list above.
> 
> ace@grape:~$ qdbus :1.86 /org/ayatana/NotificationItem/Slack1   
> org.kde.StatusNotifierItem.Title
> slack
> ace@grape:~$ qdbus :1.86 /org/ayatana/NotificationItem/Slack1   
> org.kde.StatusNotifierItem.AttentionIconName
> 
> ace@grape:~$ qdbus :1.86 /org/ayatana/NotificationItem/Slack1   
> org.kde.StatusNotifierItem.IconName
> chrome_app_indicator2_8b0f938d131432377066b29db2acc344
> ace@grape:~$ qdbus :1.86 /org/ayatana/NotificationItem/Slack1   
> org.kde.StatusNotifierItem.IconTheme
> Error: org.freedesktop.DBus.Error.UnknownMethod
> No such method 'IconTheme'
> ace@grape:~$ qdbus :1.86 /org/ayatana/NotificationItem/Slack1   
> org.kde.StatusNotifierItem.IconThemePath
> /run/user/1000/snap.slack/.org.chromium.Chromium.kAlzqv/icons
> ace@grape:~$ qdbus :1.86 /org/ayatana/NotificationItem/Slack1   
> org.kde.StatusNotifierItem.Status


Above is the result for my KDE Neon using the snap.

Below is the output my Kubuntu 18.04 machine using the PPA:

ace@cherry:~$ qdbus :1.1775 /org/ayatana/NotificationItem/Slack1   
org.kde.StatusNotifierItem.Title
slack
ace@cherry:~$ qdbus :1.1775 /org/ayatana/NotificationItem/Slack1   
org.kde.StatusNotifierItem.AttentionIconName

ace@cherry:~$ qdbus :1.1775 /org/ayatana/NotificationItem/Slack1   
org.kde.StatusNotifierItem.IconName
chrome_app_indicator2_e349fb9bb0990f3749c2bd64bd1521d3
ace@cherry:~$ qdbus :1.1775 /org/ayatana/NotificationItem/Slack1   
org.kde.StatusNotifierItem.IconTheme
Error: org.freedesktop.DBus.Error.UnknownMethod
No such method 'IconTheme'
ace@cherry:~$ qdbus :1.1775 /org/ayatana/NotificationItem/Slack1   
org.kde.StatusNotifierItem.IconThemePath
/tmp/.org.chromium.Chromium.LQtajH/icons
ace@cherry:~$ qdbus :1.1775 /org/ayatana/NotificationItem/Slack1   
org.kde.StatusNotifierItem.Status
Active

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

[kmymoney] [Bug 384985] Incomplete german translation of stable kmymoney

2019-01-25 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=384985

Ralf Habacker  changed:

   What|Removed |Added

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

--- Comment #3 from Ralf Habacker  ---
Changes has been applied to svn.

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

[Discover] [Bug 403544] Arrow (→) is displayed as box in package update descriptions

2019-01-25 Thread Karl Ove Hufthammer
https://bugs.kde.org/show_bug.cgi?id=403544

Karl Ove Hufthammer  changed:

   What|Removed |Added

 CC||k...@huftis.org

--- Comment #2 from Karl Ove Hufthammer  ---
I think you are confused about the arrows, Øystein. Discover uses the ⮕ arrow,
not the → arrow.

But the ⮕ character is not very well supported in fonts commonly found on Linux
or Windows. Source:
http://www.fileformat.info/info/unicode/char/2b95/fontsupport.htm

On the other, the → character *is* well supported:
http://www.fileformat.info/info/unicode/char/2192/fontsupport.htm
If it’s not included in the user’s default UI font, it is extremely like that
at least one of the fallback fonts Qt automatically uses supports it.

And, IMHO, the ⮕ arrow looks much too bold, and doesn’t fit with the rest of
the text in Discover.

For these two reasons, I recommend changing the ⮕ arrow into a → arrow.

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

[plasmashell] [Bug 403596] Slack tray icon not working in Plasma

2019-01-25 Thread Ryan
https://bugs.kde.org/show_bug.cgi?id=403596

--- Comment #4 from Ryan  ---
(In reply to David Edmundson from comment #3)
> Oh, that's good news.
> 
> Next:
> 
> Run
> 
>  qdbus org.kde.StatusNotifierWatcher /StatusNotifierWatcher
> org.kde.StatusNotifierWatcher.RegisteredStatusNotifierItems 
> 
> 
> That'll give you a list in the form
> 
> :1.32/StatusNotifierItem
> 
> 
> Run 
> 
> qdbus :1.32 /StatusNotifierItemorg.kde.StatusNotifierItem.Title
> qdbus :1.32 /StatusNotifierItem   
> org.kde.StatusNotifierItem.AttentionIconName
> qdbus :1.32 /StatusNotifierItemorg.kde.StatusNotifierItem.IconName
> qdbus :1.32 /StatusNotifierItemorg.kde.StatusNotifierItem.IconTheme
> qdbus :1.32 /StatusNotifierIte
> org.kde.StatusNotifierItem.IconThemePath
> qdbus :1.32 /StatusNotifierIte org.kde.StatusNotifierItem.Status
> 
> (where :1.32 and potentially "/StatusNotifierItem" are from that list above.

ace@grape:~$ qdbus :1.86 /org/ayatana/NotificationItem/Slack1   
org.kde.StatusNotifierItem.Title
slack
ace@grape:~$ qdbus :1.86 /org/ayatana/NotificationItem/Slack1   
org.kde.StatusNotifierItem.AttentionIconName

ace@grape:~$ qdbus :1.86 /org/ayatana/NotificationItem/Slack1   
org.kde.StatusNotifierItem.IconName
chrome_app_indicator2_8b0f938d131432377066b29db2acc344
ace@grape:~$ qdbus :1.86 /org/ayatana/NotificationItem/Slack1   
org.kde.StatusNotifierItem.IconTheme
Error: org.freedesktop.DBus.Error.UnknownMethod
No such method 'IconTheme'
ace@grape:~$ qdbus :1.86 /org/ayatana/NotificationItem/Slack1   
org.kde.StatusNotifierItem.IconThemePath
/run/user/1000/snap.slack/.org.chromium.Chromium.kAlzqv/icons
ace@grape:~$ qdbus :1.86 /org/ayatana/NotificationItem/Slack1   
org.kde.StatusNotifierItem.Status

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

[digikam] [Bug 403594] Export to Google - Album List incomplete

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

Maik Qualmann  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
   Version Fixed In||6.0.0
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/dig
   ||ikam/7aeef15a9b73a0d4c07cda
   ||fbc8d10414c215be2c

--- Comment #1 from Maik Qualmann  ---
Git commit 7aeef15a9b73a0d4c07cdafbc8d10414c215be2c by Maik Qualmann.
Committed on 25/01/2019 at 18:57.
Pushed by mqualmann into branch 'master'.

read next album list page if available
FIXED-IN: 6.0.0

M  +2-1NEWS
M  +33   -10   core/utilities/assistants/webservices/google/gphoto/gptalker.cpp
M  +4-4core/utilities/assistants/webservices/google/gphoto/gptalker.h

https://commits.kde.org/digikam/7aeef15a9b73a0d4c07cdafbc8d10414c215be2c

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

[Discover] [Bug 403597] New: Discover Crashes upon opening

2019-01-25 Thread Melvin Garcia
https://bugs.kde.org/show_bug.cgi?id=403597

Bug ID: 403597
   Summary: Discover Crashes upon opening
   Product: Discover
   Version: 5.14.5
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: virtualspect...@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.14.5)

Qt Version: 5.11.2
Frameworks Version: 5.54.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: I just opened Discover
normally.

- Unusual behavior I noticed: Discover crashes upon opening the app. It doesn't
even load, I just get a notification about it crashing.

The crash can be reproduced every time.

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

Thread 10 (Thread 0x7fddc9081700 (LWP 17491)):
#0  0x7fde0f6f70b4 in __GI___libc_read (fd=39, buf=0x7fddc9080b90,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x7fde09ca9cd0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fde09c65027 in g_main_context_check () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fde09c654e0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fde09c6564c in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fde1003604b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fde0ffda30a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fde0fe05bba in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fde0fe10adb in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fde0be016db in start_thread (arg=0x7fddc9081700) at
pthread_create.c:463
#10 0x7fde0f70888f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 9 (Thread 0x7fddcbb87700 (LWP 17486)):
#0  0x7fde0be09054 in __GI___pthread_getspecific (key=4) at
pthread_getspecific.c:60
#1  0x7fde09c8d5f0 in g_thread_self () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fde09c6563d in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fde1003604b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fde0ffda30a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fde0fe05bba in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fde0fe10adb in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fde0be016db in start_thread (arg=0x7fddcbb87700) at
pthread_create.c:463
#8  0x7fde0f70888f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 8 (Thread 0x7fddd707b700 (LWP 17484)):
#0  0x7fde0f6fbbf9 in __GI___poll (fds=0x7fddcc003de0, nfds=1,
timeout=10050) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fde09c65539 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fde09c6564c in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fde1003604b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fde0ffda30a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fde0fe05bba in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fde0fe10adb in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fde0be016db in start_thread (arg=0x7fddd707b700) at
pthread_create.c:463
#8  0x7fde0f70888f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 7 (Thread 0x7fdddc9a0700 (LWP 17483)):
#0  0x7fde0f6fbbf9 in __GI___poll (fds=0x5559d40810c0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fde09c65539 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fde09c658d2 in g_main_loop_run () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fdddf8f9026 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x7fde09c8d105 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fde0be016db in start_thread (arg=0x7fdddc9a0700) at
pthread_create.c:463
#6  0x7fde0f70888f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7f1a1700 (LWP 17482)):
#0  0x7fde0f6f70b4 in __GI___libc_read (fd=14, buf=0x7f1a0ce0,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x7fde09ca9cd0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fde09c65027 in g_main_context_check () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  

[plasmashell] [Bug 403596] Slack tray icon not working in Plasma

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

--- Comment #3 from David Edmundson  ---
Oh, that's good news.

Next:

Run

 qdbus org.kde.StatusNotifierWatcher /StatusNotifierWatcher
org.kde.StatusNotifierWatcher.RegisteredStatusNotifierItems 


That'll give you a list in the form

:1.32/StatusNotifierItem


Run 

qdbus :1.32 /StatusNotifierItemorg.kde.StatusNotifierItem.Title
qdbus :1.32 /StatusNotifierItem   
org.kde.StatusNotifierItem.AttentionIconName
qdbus :1.32 /StatusNotifierItemorg.kde.StatusNotifierItem.IconName
qdbus :1.32 /StatusNotifierItemorg.kde.StatusNotifierItem.IconTheme
qdbus :1.32 /StatusNotifierIte org.kde.StatusNotifierItem.IconThemePath
qdbus :1.32 /StatusNotifierIte org.kde.StatusNotifierItem.Status

(where :1.32 and potentially "/StatusNotifierItem" are from that list above.

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

[plasmashell] [Bug 403596] Slack tray icon not working in Plasma

2019-01-25 Thread Ryan
https://bugs.kde.org/show_bug.cgi?id=403596

--- Comment #2 from Ryan  ---
(In reply to David Edmundson from comment #1)
> If you run "killall xembedsniproxy" does that icon disappear or stay?

It stays

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

  1   2   >