[elisa] [Bug 406499] elisa git fails to build on High Sierra

2019-04-14 Thread Yurii Kolesnykov
https://bugs.kde.org/show_bug.cgi?id=406499

--- Comment #2 from Yurii Kolesnykov  ---
(In reply to Nate Graham from comment #1)
> ld: symbol(s) not found for architecture x86_64
> 
> Sounds like you don't have all the right dependencies installed. I'd contact
> the homebrew folks to see if their tap/cask/keg/whatever it's called is
> up-to-date and bug-free.

It's actually me, I maintain this tap and had created this formula two days
ago. You can examine formula here:
https://github.com/KDE-mac/homebrew-kde/blob/master/Formula/elisa.rb

Also, I want to mention, that brew builds formulas in sandbox and recursively
exposes only those dependencies that was mentioned explicitly.

I don't have a build issue on 10.14 (Mojave), but I don't see the GUI in my
build, release and nightly Jenkins builds. Also, ninja doesn't work with elisa
for me. I will report those issues separately.

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

[elisa] [Bug 406499] elisa git fails to build on High Sierra

2019-04-14 Thread Yurii Kolesnykov
https://bugs.kde.org/show_bug.cgi?id=406499

--- Comment #3 from Yurii Kolesnykov  ---
> all the right dependencies installed

Isn't this must be solved by CMake, which must fail during configure?

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

[korgac] [Bug 406521] New: korgac crash on start up

2019-04-14 Thread Chili81
https://bugs.kde.org/show_bug.cgi?id=406521

Bug ID: 406521
   Summary: korgac crash on start up
   Product: korgac
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: markus.holb...@gmail.com
  Target Milestone: ---

Created attachment 119407
  --> https://bugs.kde.org/attachment.cgi?id=119407&action=edit
crash log

SUMMARY


STEPS TO REPRODUCE
1. restart PC
2. 
3. 

OBSERVED RESULT
crash: korgac PID: 1719 Signal: Segmentation fault (11) 

EXPECTED RESULT
normal start without crash

SOFTWARE/OS VERSIONS
Windows: -
macOS: -
Linux/KDE Plasma: KDE Neon 5.15
(available in About System)
KDE Plasma Version:  5.15.4
KDE Frameworks Version: 5.57.0
Qt Version: 5.12.0
Kernel 4.15.0-47-generic
64bit OS

ADDITIONAL INFORMATION
Application: KOrganizer-Erinnerungsmodul (korgac), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fdc2c86e880 (LWP 1719))]

Thread 5 (Thread 0x7fdc05423700 (LWP 1815)):
#0  0x7fdc2664cbf9 in __GI___poll (fds=0x7fdbfc003ce0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fdc1d5c4539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fdc1d5c464c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fdc271a715b in QEventDispatcherGlib::processEvents
(this=0x7fdbfc000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x7fdc2714864a in QEventLoop::exec (this=this@entry=0x7fdc05422d20,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#5  0x7fdc26f7041a in QThread::exec (this=) at
thread/qthread.cpp:531
#6  0x7fdc26f71bc2 in QThreadPrivate::start (arg=0x558489c18a80) at
thread/qthread_unix.cpp:361
#7  0x7fdc1f33f6db in start_thread (arg=0x7fdc05423700) at
pthread_create.c:463
#8  0x7fdc2665988f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7fdc05c24700 (LWP 1810)):
#0  0x7fdc2664cbf9 in __GI___poll (fds=0x7fdbf80049b0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fdc1d5c4539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fdc1d5c464c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fdc271a715b in QEventDispatcherGlib::processEvents
(this=0x7fdbf8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x7fdc2714864a in QEventLoop::exec (this=this@entry=0x7fdc05c23d20,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#5  0x7fdc26f7041a in QThread::exec (this=) at
thread/qthread.cpp:531
#6  0x7fdc26f71bc2 in QThreadPrivate::start (arg=0x558489c3a1c0) at
thread/qthread_unix.cpp:361
#7  0x7fdc1f33f6db in start_thread (arg=0x7fdc05c24700) at
pthread_create.c:463
#8  0x7fdc2665988f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7fdc0703e700 (LWP 1804)):
#0  0x7fdc2664cbf9 in __GI___poll (fds=0x558489c79920, nfds=1,
timeout=7169) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fdc1d5c4539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fdc1d5c464c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fdc271a715b in QEventDispatcherGlib::processEvents
(this=0x7fdc0b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x7fdc2714864a in QEventLoop::exec (this=this@entry=0x7fdc0703dcf0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#5  0x7fdc26f7041a in QThread::exec (this=) at
thread/qthread.cpp:531
#6  0x7fdc27615015 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7fdc26f71bc2 in QThreadPrivate::start (arg=0x7fdc2788cd80) at
thread/qthread_unix.cpp:361
#8  0x7fdc1f33f6db in start_thread (arg=0x7fdc0703e700) at
pthread_create.c:463
#9  0x7fdc2665988f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7fdc0dc13700 (LWP 1785)):
#0  0x7fdc2664cbf9 in __GI___poll (fds=0x7fdc0dc12c38, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fdc1f96d747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fdc1f96f36a in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fdc0ef8732a in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7fdc26f71bc2 in QThreadPrivate::start (arg=0x558489b6aa90) at
thread/qthread_unix.cpp:361
#5  0x7fdc1f33f6db in start_thread (arg=0x7fdc0dc13700) at
pthread_create.c:463
#6  0x7fdc2665988f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7fdc2c86e880 (LWP 1719)):
[KCrash Handler]
#6  0x7fdc2b96f9c9 in Akonadi::BlockAlarmsAttribute::isAlarmTypeBlocked
(this=this@entry=0x55848a21e7a0, type=KCalCore::Alarm::Displa

[korgac] [Bug 406521] korgac crash on start up

2019-04-14 Thread Chili81
https://bugs.kde.org/show_bug.cgi?id=406521

--- Comment #1 from Chili81  ---
Version 5.10.3

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

[okular] [Bug 406489] Can not save image in pdf file use okular

2019-04-14 Thread widon1104
https://bugs.kde.org/show_bug.cgi?id=406489

--- Comment #3 from widon1104  ---
Take a screenshot of the image is not a good solution.
If I take a screenshot of the image I will get a bad resolution image and
sometimes the image is so big and hard to take a screenshot.
I find the gnome evince have this feature to save the image, so I use evince
now.

I hope okular will add this feature to make okular better.

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

[Skanlite] [Bug 370972] Scanned image is bad

2019-04-14 Thread Kåre Särs
https://bugs.kde.org/show_bug.cgi?id=370972

Kåre Särs  changed:

   What|Removed |Added

 CC||linuxdav...@gmail.com

--- Comment #46 from Kåre Särs  ---
*** Bug 356124 has been marked as a duplicate of this bug. ***

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

[libksane] [Bug 356124] Problem when start Skanlite and take a photo

2019-04-14 Thread Kåre Särs
https://bugs.kde.org/show_bug.cgi?id=356124

Kåre Särs  changed:

   What|Removed |Added

Version|1.1 |unspecified
Product|Skanlite|libksane
   Version Fixed In||KDE Applications 18.12
  Component|general |general
 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #14 from Kåre Särs  ---
This bug should be fixed by commit:

https://commits.kde.org/libksane/ef39d6cfd6c97880061e6ebb32c9c611e372f920

And included in KDE applications release 18.12

I missed this bug report when the fix was made.

This one was first, but the fix-commit was done to the other so marking this as
a duplicate to get the information here as well.

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

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

[dolphin] [Bug 406506] Wish - Show metadata of files stored on locations non-indexed by baloo

2019-04-14 Thread Méven Car
https://bugs.kde.org/show_bug.cgi?id=406506

Méven Car  changed:

   What|Removed |Added

 CC||meve...@gmail.com

--- Comment #2 from Méven Car  ---


Or index temporarily (without history) all the files loaded in dolphin when it
is not in an indexed path.
Or short-circuit baloo and extract metadata the same sort of way KPreviewJob
does.

Volatile storage/temporary storage is a common use case, we could offer
metadata there as well.

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

[frameworks-kglobalaccel] [Bug 406426] kglobalaccel5 crashes often

2019-04-14 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=406426

--- Comment #5 from Laurent Montel  ---
I will investigate it.

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

[okular] [Bug 395497] Menubar - No text

2019-04-14 Thread Jan Przybylak
https://bugs.kde.org/show_bug.cgi?id=395497

--- Comment #13 from Jan Przybylak  ---
Yes.
Also:
`journalctl` does not return helpful results. If there are other logs that
could help, I'm happy to send them

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

[plasmashell] [Bug 364766] Graphics distorted after suspend/resume with nvidia

2019-04-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=364766

techxga...@outlook.com changed:

   What|Removed |Added

 CC||techxga...@outlook.com

--- Comment #88 from techxga...@outlook.com ---
(In reply to David Edmundson from comment #86)
> Git commit c244729b67714f2c3c471815b1cdafa6ac5e8d9d by David Edmundson.
> Committed on 07/04/2019 at 15:35.
> Pushed by davidedmundson into branch 'master'.
> 
> Enable glGetGraphicsResetStatus support by default on Qt >= 5.13
> 
> Summary:
> I added support in Qt for handling Nvidia's glGetGraphicsResetStatus
> flag, which reports when it has lost it's context and the visual state
> needs refreshing.
> 
> As it required some changes in various other parts of Qt and Plasma this
> was opt-in behind a QSurfaceFormat flag which I exposed to Plasma users
> via a config option. Since Qt5.12.2 everything seems to work nicely.
> 
> This patch enables support on Qt >= 5.13 to play safe.

I have Qt 5.12.2 on Kubuntu 19.04, and the flickering graphics happens from
boot.  Would this update fix that as well? 

https://bugs.kde.org/show_bug.cgi?id=405920#c5

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

[Falkon] [Bug 391327] Saving passwords doesn't work on some sites

2019-04-14 Thread Jan Przybylak
https://bugs.kde.org/show_bug.cgi?id=391327

Jan Przybylak  changed:

   What|Removed |Added

 CC||jplx...@gmail.com

--- Comment #11 from Jan Przybylak  ---
What about an option in the right-click menu? If detecting is currently not
possible on some sites, I think that would be a viable workaround.

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

[konsole] [Bug 406522] New: super+fn keys not working in emacs

2019-04-14 Thread Ernesto
https://bugs.kde.org/show_bug.cgi?id=406522

Bug ID: 406522
   Summary: super+fn keys not working in emacs
   Product: konsole
   Version: 17.12.3
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: keyboard
  Assignee: konsole-de...@kde.org
  Reporter: erjoa...@gmail.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. In a console window, run headless emacs: "emaccs -nw -Q"
2. Invoke the `describe-key` command, e.g. `C-h k` or `M-x describe-key`
3. Type super+F1 () (or super+F2, etc)


OBSERVED RESULT

The observed behavior is that emacs does not interpret the keypress as ""

This is what emacs receives and interprets, from the `view-lossage` command:


 C-h k [describe-key]
 ESC O 1 P [self-insert-command]

The result is that P is inserted.


EXPECTED RESULT
I expect that emacs interprets an  key sequence



I'm not too familiar with either the escape sequences into which konsole maps a
keypress like super+F1, or the configuration in emacs that may be needed to
interpret these escape sequences correctly, so I'm not sure whether this is a
problem on the konsole or emacs side.

Is there a known recipe for allowing super+F1 and other FN keys to be mapped
correctly from konsole to emacs?



SOFTWARE/OS VERSIONS 
Debian 9.8
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

Dependencies: 
4:16.12.0-4 - konsole-kpart (5 4:16.12.0-4) kio (0 (null)) libc6 (2 2.14)
libkf5completion5 (2 4.97.0) libkf5configcore5 (2 4.98.0) libkf5configgui5 (2
4.97.0) libkf5configwidgets5 (2 4.96.0) libkf5coreaddons5 (2 5.2.0)
libkf5crash5 (2 5.15.0) libkf5dbusaddons5 (2 4.99.0) libkf5i18n5 (2 4.97.0)
libkf5iconthemes5 (2 4.96.0) libkf5kiowidgets5 (2 4.96.0) libkf5notifyconfig5
(2 4.96.0) libkf5widgetsaddons5 (2 4.96.0) libkf5windowsystem5 (2 4.96.0)
libkf5xmlgui5 (2 4.98.0) libqt5core5a (2 5.7.0) libqt5gui5 (2 5.7.0)
libqt5widgets5 (2 5.4) libstdc++6 (2 4.1.1) 


$ konsole --version
konsole 16.12.0

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

[dolphin] [Bug 406506] Wish - Show metadata of files stored on locations non-indexed by baloo

2019-04-14 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=406506

--- Comment #3 from Patrick Silva  ---
Ntfs file system of internal hard disks is just an example.
Currently Dolphin also does not show metadata of files stored
in removable devices formatted with any file system.

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

[krita] [Bug 395891] New option in crop tool: crop only a current frame

2019-04-14 Thread Tymond
https://bugs.kde.org/show_bug.cgi?id=395891

--- Comment #2 from Tymond  ---
There are two options in Crop Tool now: crop a layer or crop a canvas (+ all
content on all layers round the boundaries of the new canvas size). The first
option doesn't change the document/canvas size. I want the first option, just
applied to only one frame instead of all frames on the layer.

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

[okular] [Bug 406489] Can not save image in pdf file use okular

2019-04-14 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=406489

Albert Astals Cid  changed:

   What|Removed |Added

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

--- Comment #4 from Albert Astals Cid  ---
Yes, it's a valid wish.

As point of control kpdf used to have this and i think there's still some code
in Okular that pretends to support it, we just never finished that feature.

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

[Bluedevil] [Bug 406523] New: KDE not auto accepting file transfer for all/trustworthy Bluetooth devices

2019-04-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=406523

Bug ID: 406523
   Summary: KDE not auto accepting file transfer for
all/trustworthy Bluetooth devices
   Product: Bluedevil
   Version: 5.14.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: system tray
  Assignee: now...@gmail.com
  Reporter: crptdng...@gmx.net
  Target Milestone: ---

SUMMARY
Although enabled in KDE system settings for Bluetooth, KDE does not accept
incoming files from Android device automatically.

STEPS TO REPRODUCE
1. Enable a BT adapter on KDE, name it, make it visible always,
2. KDE Bluetooth Extended settings "(Erweiterte Einstellungen") for BT adapter:
enter a download directory and enable "autoaccept files" for all BT devices,
3. pair Android phone (Samsung Galaxy S8, Android 9) via BT,
4. on Android phone: select a few photos and start file transfer to KDE BT
adapter,

OBSERVED RESULT
4. For each photo, file transfer has to be accepted on KDE systray notification
(NOK).

EXPECTED RESULT
4. for each photo, file transfer should be accepted automatically by KDE and
all files should be downloaded to download directory.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian GNU/Linux 
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3
ADDITIONAL INFORMATION
Kernel-Version: 5.0.7-towo.4-siduction-amd64

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

[elisa] [Bug 406524] New: Playlist display issue when removing first track of the playlist

2019-04-14 Thread Jerome Guidon
https://bugs.kde.org/show_bug.cgi?id=406524

Bug ID: 406524
   Summary: Playlist display issue when removing first track of
the playlist
   Product: elisa
   Version: 0.3.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: gui...@live.fr
  Target Milestone: ---

Created attachment 119408
  --> https://bugs.kde.org/attachment.cgi?id=119408&action=edit
the first track is not visible

SUMMARY
When I remove the first track of the playlist, the new first track is not
visible, like if the opacity of the row was 0.


STEPS TO REPRODUCE
1. Have some tracks in the playlist
2. remove the first track

OBSERVED RESULT
The new first track is not visible, like if the opacity of the row was 0. See
the attachement after the action (the first track in the playlist)

EXPECTED RESULT
The first row in the playlist should look the same as the others below

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Kde Neon
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 5.57.0
Qt Version: 5.12.0
Elisa Version : current master branch (April 2019)

ADDITIONAL INFORMATION
I discovered the issue while testing for another task
(https://phabricator.kde.org/D19610 ). I could investigate a little bit and
found the bug originated from the commit
fc9736e1d124f40002d835890af82a6103a0c322 . I tried to figure out why the
section caused the issue for I cannot explain it yet.

I will try to keep on looking but any help is welcomed :)

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

[kmymoney] [Bug 406525] New: Subtotals are not correctly aggregated when (sub-)categories have the same name

2019-04-14 Thread Thomas Baumgart
https://bugs.kde.org/show_bug.cgi?id=406525

Bug ID: 406525
   Summary: Subtotals are not correctly aggregated when
(sub-)categories have the same name
   Product: kmymoney
   Version: 5.0.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: reports
  Assignee: kmymoney-de...@kde.org
  Reporter: tbaumg...@kde.org
  Target Milestone: ---

Created attachment 119409
  --> https://bugs.kde.org/attachment.cgi?id=119409&action=edit
Testfile showing the problem

STEPS TO REPRODUCE
1. Load the attached test file
2. Open a transaction by category report

OBSERVED RESULT
Subtotal for Expense:Category A is missing
Subtotal for Expense is missing
Amount of Subtotal Income:Category A is wrong

EXPECTED RESULT
Subtotal for Expense:Category A is present
Subtotal for Expense is present
All reported amounts are correct

ADDITIONAL INFORMATION:
This only shows up if a the category type (e.g. income, expense) and the
sub-category name change and the top-level category name is the same.

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

[krusader] [Bug 406201] Calculating space of all directories at once

2019-04-14 Thread Davide Gianforte
https://bugs.kde.org/show_bug.cgi?id=406201

Davide Gianforte  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway

2019-04-14 Thread Jan Przybylak
https://bugs.kde.org/show_bug.cgi?id=75324

--- Comment #96 from Jan Przybylak  ---
I agree, if there are existing solutions, I'd just use those.
I don't know however if GVfs lacks required features that KIO has or there are
other reasons not to use it in KDE.

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

[krita] [Bug 406490] Filter only applies to visible area of the canvas instead of all pixel data in layer.

2019-04-14 Thread Boudewijn Rempt
https://bugs.kde.org/show_bug.cgi?id=406490

--- Comment #3 from Boudewijn Rempt  ---
It's a rather fundamental thing to change, so merely adding a checkbox isn't
going to work. Filters themselves are applied using multiple threads, where
possible. Vectorization might be a good idea... But have you thought of using a
filter mask?

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

[krusader] [Bug 397398] Misleading ‘Created’ date in file properties

2019-04-14 Thread Alex Bikadorov
https://bugs.kde.org/show_bug.cgi?id=397398

Alex Bikadorov  changed:

   What|Removed |Added

 Status|REOPENED|ASSIGNED
 CC||alex.bikado...@kdemail.net

--- Comment #6 from Alex Bikadorov  ---
Thanks for the information Méven!

Supporting statx with ifdef logic may be too costly. But we should at least fix
the mix-up of creation time and ctime.

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

[kwin] [Bug 406526] New: Request: Removal of destructive window shortcuts

2019-04-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=406526

Bug ID: 406526
   Summary: Request: Removal of destructive window shortcuts
   Product: kwin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: plane.wan...@gmail.com
  Target Milestone: ---

Currently KWin still supports destructive window shortcuts like "Close window".
That's a problem, an admin might have enabled it or changed the default
shortcut for all users because it's so obvious to the admin but unexpected to
users. Then a user might accidentely close one of its windows and lose data
because they used the wrong shortcut. 

Therefore I suggest to remove all destructive shortcuts in KWin in order to
make it more user friendly and to have a predictable user interface with
explicit and clear destructive actions.

STEPS TO REPRODUCE
1. Change the default shortcut for "Close window" from  to something
like 
2. Ask an experience Windows user to open the task manager on Plasma
3. The Windows user might use the shortcut , which opens the
task manager on Windows

OBSERVED RESULT
The task manager doesn't open but the currently focused window gets closed and
the user might lose data.

EXPECTED RESULT
The window shouldn't close because someone hit the wrong shortcut.

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

[kwin] [Bug 406527] New: Request: Removal of destructive window shortcuts

2019-04-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=406527

Bug ID: 406527
   Summary: Request: Removal of destructive window shortcuts
   Product: kwin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: plane.wan...@gmail.com
  Target Milestone: ---

Currently KWin still supports destructive window shortcuts like "Close window".
That's a problem, an admin might have enabled it or changed the default
shortcut for all users because it's so obvious to the admin but unexpected to
users. Then a user might accidentely close one of its windows and lose data
because they used the wrong shortcut. 

Therefore I suggest to remove all destructive shortcuts in KWin in order to
make it more user friendly and to have a predictable user interface with
explicit and clear destructive actions.

STEPS TO REPRODUCE
1. Change the default shortcut for "Close window" from  to something
like 
2. Ask an experience Windows user to open the task manager on Plasma
3. The Windows user might use the shortcut , which opens the
task manager on Windows

OBSERVED RESULT
The task manager doesn't open but the currently focused window gets closed and
the user might lose data.

EXPECTED RESULT
The window shouldn't close because someone hit the wrong shortcut.

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

[kwin] [Bug 406526] Request: Removal of destructive window shortcuts

2019-04-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=406526

--- Comment #1 from plane.wan...@gmail.com ---
*** Bug 406527 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 406527] Request: Removal of destructive window shortcuts

2019-04-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=406527

plane.wan...@gmail.com changed:

   What|Removed |Added

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

--- Comment #1 from plane.wan...@gmail.com ---


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

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

[kmymoney] [Bug 406525] Subtotals are not correctly aggregated when (sub-)categories have the same name

2019-04-14 Thread Thomas Baumgart
https://bugs.kde.org/show_bug.cgi?id=406525

Thomas Baumgart  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
   Version Fixed In||5.0.4
  Latest Commit||https://commits.kde.org/kmy
   ||money/4b7bbe834886c5ebe7fba
   ||86a68290dec4c1850bd
 Resolution|--- |FIXED

--- Comment #1 from Thomas Baumgart  ---
Git commit 4b7bbe834886c5ebe7fba86a68290dec4c1850bd by Thomas Baumgart.
Committed on 14/04/2019 at 11:50.
Pushed by tbaumgart into branch '5.0'.

Fix subtotals

Subtotals in e.g transaction reports are not correctly calculated and
shown. This only shows up if a the category type (e.g. income, expense)
and the sub-category name change and the top-level category name is the
same.

This change fixes the problem so that all sub-totals are calculated and
presented correctly.
FIXED-IN: 5.0.4

M  +71   -63   kmymoney/plugins/views/reports/core/querytable.cpp

https://commits.kde.org/kmymoney/4b7bbe834886c5ebe7fba86a68290dec4c1850bd

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

[krita] [Bug 395891] New option in crop tool: crop only a current frame

2019-04-14 Thread Scott Petrovic
https://bugs.kde.org/show_bug.cgi?id=395891

--- Comment #3 from Scott Petrovic  ---
Ahh ok. It is in the tool options for the Crop tool. The section is called
"Applies to". I think that is what you are referring to.

I think that makes sense then. Yes, I think that would make this a bug.
Cropping with "applies to layer" should only affect the current animation frame
selected, not all frames for the layer.

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

[frameworks-kglobalaccel] [Bug 406528] New: kglobalaccel5, signal: Segmentation fault

2019-04-14 Thread Paweł Krzak
https://bugs.kde.org/show_bug.cgi?id=406528

Bug ID: 406528
   Summary: kglobalaccel5, signal: Segmentation fault
   Product: frameworks-kglobalaccel
   Version: 5.57.0
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: krzak.pa...@gmail.com
  Target Milestone: ---

Hello!
Today, I made update (apt-get dist-upgrade) for my Linux NEON LTS v18.04 x64
distribution. After reboot the system I have got problem with kglobalaccel5
package. Systems reports: KDE (kglobalaccel5), signal: Segmentation fault.
Currently, shortcuts doesnt't work (at least in my case).


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Linux NEON x64 18.04 LTS
KDE Plasma Version: 5.12 LTS
KDE Frameworks Version: 5.57
Qt Version: 5.12

Stack-trace:
Application: Usługa globalnych skrótów KDE (kglobalaccel5), signal:
Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe09715d800 (LWP 1747))]

Thread 3 (Thread 0x7fe07e8b8700 (LWP 1765)):
#0  0x7fe0951150b4 in __GI___libc_read (fd=6, buf=0x7fe07e8b7b60,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x7fe091cadcd0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fe091c69027 in g_main_context_check () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fe091c694e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fe091c6964c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fe095a5c15b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fe0959fd64a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fe09582541a in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fe094706015 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#9  0x7fe095826bc2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7fe093d4d6db in start_thread (arg=0x7fe07e8b8700) at
pthread_create.c:463
#11 0x7fe09512688f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7fe08b276700 (LWP 1757)):
#0  0x7fe095119bf9 in __GI___poll (fds=0x7fe08b275cb8, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fe090f56747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fe090f5836a in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fe08c7f132a in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7fe095826bc2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fe093d4d6db in start_thread (arg=0x7fe08b276700) at
pthread_create.c:463
#6  0x7fe09512688f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7fe09715d800 (LWP 1747)):
[KCrash Handler]
#6  0x7fe096d60da0 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5GlobalAccelPrivate.so.5
#7  0x7fe096d5daf0 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5GlobalAccelPrivate.so.5
#8  0x7fe096d6699b in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5GlobalAccelPrivate.so.5
#9  0x7fe096d66d85 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5GlobalAccelPrivate.so.5
#10 0x7fe094711128 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#11 0x7fe094715f80 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#12 0x7fe094716467 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#13 0x7fe094718f1e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#14 0x7fe095a2f992 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7fe0959ff328 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7fe095a01e87 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7fe095a5cb23 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x7fe091c69387 in g_main_context_dispatch () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x7fe091c695c0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x7fe091c6964c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7fe095a5c13f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x7fe0959fd64a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x7fe095a06800 in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x55c80206e7f7 in ?? ()
#25 0x7fe095026b97 in __libc_start_main (main=0x55c80206e4c0, argc=1,
argv=0x7fff56c7b058, init=, fini=,
rtld_fini=, stack_end=0x7fff56c7b048) at ../csu/libc-start.c:310
#26 0x55

[kwin] [Bug 406526] Request: Removal of destructive window shortcuts

2019-04-14 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=406526

--- Comment #2 from Christoph Feck  ---
That's probably not a serious wish, but a prank related to bug 321190 comment
#2.

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

[frameworks-kglobalaccel] [Bug 406528] kglobalaccel5, signal: Segmentation fault

2019-04-14 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=406528

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---


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

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

[frameworks-kglobalaccel] [Bug 406426] kglobalaccel5 crashes often

2019-04-14 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=406426

Christoph Feck  changed:

   What|Removed |Added

 CC||krzak.pa...@gmail.com

--- Comment #6 from Christoph Feck  ---
*** Bug 406528 has been marked as a duplicate of this bug. ***

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

[elisa] [Bug 406529] New: Elisa doesn't show cover icons

2019-04-14 Thread Rainer Finke
https://bugs.kde.org/show_bug.cgi?id=406529

Bug ID: 406529
   Summary: Elisa doesn't show cover icons
   Product: elisa
   Version: 0.3.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: m...@rainer-finke.de
  Target Milestone: ---

Elisa doesn't show cover icons. Tested with Elisa 3.0 and git (2019-04-14).

STEPS TO REPRODUCE
1. Open Elisa
2. Add music

OBSERVED RESULT
No cover icons are shown

EXPECTED RESULT
Show cover icons

SOFTWARE/OS VERSIONS
OS: Arch Linux 
KDE-Plasma-Version: 5.15.4
KDE-Frameworks-Version: 5.57.0
Qt-Version: 5.13.0
Kernel-Version: 5.0.7-arch1-1-ARCH

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

[frameworks-kglobalaccel] [Bug 406156] Executable: kglobalaccel5 PID: 3301 Signal: Floating point exception (8) Time: 4/2/19 18:47:47

2019-04-14 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=406156

Christoph Feck  changed:

   What|Removed |Added

   Severity|normal  |crash

--- Comment #1 from Christoph Feck  ---
Pasting backtrace inline:

Application: KDE Global Shortcuts Service (kglobalaccel5), signal: Floating
point exception
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd1d9d03800 (LWP 3301))]

Thread 1 (Thread 0x7fd1d9d03800 (LWP 3301)):
[KCrash Handler]
#6  0x7fd1d8427f19 in QHashData::nextNode (node=node@entry=0x560d47581a70)
at tools/qhash.cpp:594
#7  0x7fd1d9901bab in QHash::const_iterator::operator++ (this=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:395
#8  KdeDGlobalAccel::Component::cleanUp (this=0x560d4756db00) at
./src/runtime/component.cpp:163
#9  0x7fd1d990a99b in KdeDGlobalAccel::Component::qt_static_metacall
(_o=_o@entry=0x560d4756db00, _c=_c@entry=QMetaObject::InvokeMetaMethod,
_id=_id@entry=1, _a=_a@entry=0x7ffd30cbf020) at
./obj-x86_64-linux-gnu/src/runtime/KF5GlobalAccelPrivate_autogen/EWIEGA46WW/moc_component.cpp:130
#10 0x7fd1d990ad85 in KdeDGlobalAccel::Component::qt_metacall
(this=0x560d4756db00, _c=QMetaObject::InvokeMetaMethod, _id=1,
_a=0x7ffd30cbf020) at
./obj-x86_64-linux-gnu/src/runtime/KF5GlobalAccelPrivate_autogen/EWIEGA46WW/moc_component.cpp:205
#11 0x7fd1d72b5128 in QDBusConnectionPrivate::deliverCall
(this=this@entry=0x7fd1bc003f10, object=object@entry=0x560d4756db00, msg=...,
metaTypes=..., slotIdx=) at qdbusintegrator.cpp:991
#12 0x7fd1d72b9f80 in QDBusConnectionPrivate::activateCall
(this=this@entry=0x7fd1bc003f10, object=0x560d4756db00, flags=240, msg=...) at
qdbusintegrator.cpp:894
#13 0x7fd1d72ba467 in QDBusConnectionPrivate::activateCall (msg=...,
flags=, object=, this=0x7fd1bc003f10) at
qdbusintegrator.cpp:843
#14 QDBusConnectionPrivate::activateObject (this=0x7fd1bc003f10, node=...,
msg=..., pathStartPos=) at qdbusintegrator.cpp:1501
#15 0x7fd1d72bcf1e in QDBusActivateObjectEvent::placeMetaCall
(this=0x7fd1bc0153c0) at qdbusintegrator.cpp:1597
#16 0x7fd1d85d3992 in QObject::event (this=0x560d4756db00, e=) at kernel/qobject.cpp:1249
#17 0x7fd1d85a3328 in QCoreApplication::notifyInternal2
(receiver=0x560d4756db00, event=0x7fd1bc0153c0) at
kernel/qcoreapplication.cpp:1061
#18 0x7fd1d85a34fe in QCoreApplication::sendEvent (receiver=, event=event@entry=0x7fd1bc0153c0) at kernel/qcoreapplication.cpp:1451
#19 0x7fd1d85a5e87 in QCoreApplicationPrivate::sendPostedEvents
(receiver=receiver@entry=0x0, event_type=event_type@entry=0,
data=0x560d474cc440) at kernel/qcoreapplication.cpp:1800
#20 0x7fd1d85a6428 in QCoreApplication::sendPostedEvents
(receiver=receiver@entry=0x0, event_type=event_type@entry=0) at
kernel/qcoreapplication.cpp:1654
#21 0x7fd1d8600b23 in postEventSourceDispatch (s=0x560d474d0340) at
kernel/qeventdispatcher_glib.cpp:276
#22 0x7fd1d480c387 in g_main_context_dispatch () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7fd1d480c5c0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x7fd1d480c64c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x7fd1d860013f in QEventDispatcherGlib::processEvents
(this=0x560d474d8d80, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#26 0x7fd1d85a164a in QEventLoop::exec (this=this@entry=0x7ffd30cbf5e0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#27 0x7fd1d85aa800 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1364
#28 0x560d45fe87f7 in main (argc=, argv=) at
./src/runtime/main.cpp:88

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

[ksysguard] [Bug 403090] info:tooltip shown not neat

2019-04-14 Thread Richard Llom
https://bugs.kde.org/show_bug.cgi?id=403090

Richard Llom  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |---
 Status|RESOLVED|REPORTED

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

[elisa] [Bug 406530] New: Elisa-git music playback stutters

2019-04-14 Thread Rainer Finke
https://bugs.kde.org/show_bug.cgi?id=406530

Bug ID: 406530
   Summary: Elisa-git music playback stutters
   Product: elisa
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: m...@rainer-finke.de
  Target Milestone: ---

Elisa-git (2019-04-14) music playback stutters

STEPS TO REPRODUCE
1. Compile Elisa from git
2. Import library

OBSERVED RESULT
Music playback stutters

EXPECTED RESULT
Music is played fine

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.57.0
Qt Version: 5.13.0
Kernel Version: 5.0.7-arch1-1-ARCH
OS Type: 64-bit
Processors: 16 × AMD Ryzen 7 1700 Eight-Core Processor
Memory: 31,4 GiB of RAM

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

[krita] [Bug 406531] New: Crash after trying to merge down and saving with large file

2019-04-14 Thread Scott Petrovic
https://bugs.kde.org/show_bug.cgi?id=406531

Bug ID: 406531
   Summary: Crash after trying to merge down and saving with large
file
   Product: krita
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Layer Stack
  Assignee: krita-bugs-n...@kde.org
  Reporter: scottpetro...@gmail.com
  Target Milestone: ---

I tried doing a few different things to pinpoint this crash...but this is the
best I can do for now. Painting on a layer and just hitting save seems to save
ok. Only after I merged down a layer...then hit save do I get a SIGKILL crash.


STEPS TO REPRODUCE
1.Download this file and open... 
https://drive.google.com/file/d/1koSRXPn5mDF-M8m5p2gKJw2P2_AHJrhn/view?usp=sharing

2. select the "freckles" layer and merge down with the right click option
3. Save the file

OBSERVED RESULT
the file hangs for a while then crashes Krita with SIGKILL


EXPECTED RESULT
the file saves and doesn't crash

SOFTWARE/OS VERSIONS
Ubuntu 18.10 on git master

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

[krita] [Bug 406531] Crash after trying to merge down and saving with large file

2019-04-14 Thread Boudewijn Rempt
https://bugs.kde.org/show_bug.cgi?id=406531

Boudewijn Rempt  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||b...@valdyas.org
 Status|REPORTED|CONFIRMED

--- Comment #1 from Boudewijn Rempt  ---
I guess this is caused by the enormous size of the image. But it should be
investigated.

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

[krita] [Bug 406531] Crash after trying to merge down and saving with large file

2019-04-14 Thread Scott Petrovic
https://bugs.kde.org/show_bug.cgi?id=406531

--- Comment #2 from Scott Petrovic  ---
I am believing more it is specific to how merge down works.  Simply deleting
the layer and hitting save has no issues.

It is large. This is for a banner graphic that I have at the conventions. I am
just trying to update it with a new graphic

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

[krita] [Bug 406531] Crash after trying to merge down and saving with large file

2019-04-14 Thread Boudewijn Rempt
https://bugs.kde.org/show_bug.cgi?id=406531

--- Comment #3 from Boudewijn Rempt  ---
merge down starts a different and longer calculation though. I couldn't
reproduce the hang locally, but, like I said, this needs investigation :-)

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

[elisa] [Bug 406532] New: Add possibility to resize cover icons in Elisa

2019-04-14 Thread Rainer Finke
https://bugs.kde.org/show_bug.cgi?id=406532

Bug ID: 406532
   Summary: Add possibility to resize cover icons in Elisa
   Product: elisa
   Version: 0.3.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: m...@rainer-finke.de
  Target Milestone: ---

Add a possibility to resize cover icons in Elisa e.g. by using CTRL + mouse
scrolling and/or a slider.


STEPS TO REPRODUCE
1. Open Elisa
2. Import music library

OBSERVED RESULT
Cannot resize cover icons in library/file view

EXPECTED RESULT
Allow resizing of cover icons so that they look nice on all screen sized (e.g.
on a HiDPI screen).

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.15.4 Wayland
KDE Frameworks Version: 5.57.0
Qt Version: 5.13.0
Kernel Version: 5.0.7-arch1-1-ARCH
OS Type: 64-bit
Processors: 16 × AMD Ryzen 7 1700 Eight-Core Processor
Memory: 31,4 GiB of RAM

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

[dolphin] [Bug 286689] Dolphin should be able to show a column for file creation date, when available

2019-04-14 Thread Méven Car
https://bugs.kde.org/show_bug.cgi?id=286689

--- Comment #25 from Méven Car  ---
Git commit 5f2ab5c62dd56e5a1dae468355c9e72d84d94398 by Méven Car.
Committed on 14/04/2019 at 13:36.
Pushed by meven into branch 'master'.

Allow the baloo widgets to display creation date and access date.

Summary:
New fields accessed and created in dolphin/baloo-widgets information panel:
{F6761789}

GUI: New fields accessed and created in dolphin/baloo-widgets information panel

Test Plan: Tested locally

Reviewers: ngraham, elvisangelaccio, bruns

Reviewed By: ngraham, elvisangelaccio, bruns

Subscribers: bruns, #baloo

Tags: #baloo

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

M  +9-0src/filemetadataprovider.cpp

https://commits.kde.org/baloo-widgets/5f2ab5c62dd56e5a1dae468355c9e72d84d94398

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

[elisa] [Bug 406524] Playlist display issue when removing first track of the playlist

2019-04-14 Thread Matthieu Gallien
https://bugs.kde.org/show_bug.cgi?id=406524

Matthieu Gallien  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #1 from Matthieu Gallien  ---
I can reproduce the issue. I had not understood that the issue happened only
with the first entry.

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

[krita] [Bug 406531] Crash after trying to merge down and saving with large file

2019-04-14 Thread Scott Petrovic
https://bugs.kde.org/show_bug.cgi?id=406531

--- Comment #4 from Scott Petrovic  ---
this computer has 8GB of RAM too. Not sure how much that might play into it if
it is starting to use swap space

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

[krita] [Bug 406531] Crash after trying to merge down and saving with large file

2019-04-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=406531

tus...@vista.aero changed:

   What|Removed |Added

 CC||tus...@vista.aero

--- Comment #5 from tus...@vista.aero ---
Cannot confirm the crash, but after saving, it still prompts that the file is
not yet saved.

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

[plasmashell] [Bug 404208] libappindicator-gtk3 breaks system tray icons and single click rise functionality

2019-04-14 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=404208

Patrick Silva  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

--- Comment #7 from Patrick Silva  ---
Here the icons of skype and ms teams look the same no matter if
libappindicator-gtk3
is installed or not.
However, I can confirm that some apps (slack and ms teams, for example) are not
focused with single left click on their systray icon when libappindicator-gtk3
is installed.

Operating System: Arch Linux 
KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.57.0
Qt Version: 5.12.2

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

[kwin] [Bug 406526] Request: Removal of destructive window shortcuts

2019-04-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=406526

--- Comment #3 from plane.wan...@gmail.com ---
(In reply to Christoph Feck from comment #2)
> That's probably not a serious wish, but a prank related to bug 321190
> comment #2.

Prank or not doesn't matter, it's the arguments that matter. Those same
arguments were already used as a justification to remove similar functionality
from KWin before and I'm just trying to be consistent.

Either the arguments make sense, then they should be taken seriously, or they
don't then this whish can be ignored, but then other desicions might need to be
re-evaluated.

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

[plasmashell] [Bug 406048] Kicker menu and notifications do not align with primary monitor dimensions.

2019-04-14 Thread Darin Miller
https://bugs.kde.org/show_bug.cgi?id=406048

Darin Miller  changed:

   What|Removed |Added

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

--- Comment #5 from Darin Miller  ---
Requested info added (but I forgot to change the status).  I assume "REPORTED"
is correct?

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

[frameworks-kglobalaccel] [Bug 406426] kglobalaccel5 crashes often

2019-04-14 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=406426

Christoph Feck  changed:

   What|Removed |Added

   Severity|normal  |crash

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

[okular] [Bug 406489] Can not save image in pdf file use okular

2019-04-14 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=406489

--- Comment #5 from Nate Graham  ---
Oh OK, cool!

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

[elisa] [Bug 406499] elisa git fails to build on High Sierra

2019-04-14 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=406499

--- Comment #4 from Nate Graham  ---
Depends on what the missing library is. Can you pinpoint what it is? If you
can, and it's not in CMake, then yeah, that would be good to add.

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

[krita] [Bug 406533] New: when the transformation tool is selected you can't see the image/draw until you switch to another tool.

2019-04-14 Thread anderson
https://bugs.kde.org/show_bug.cgi?id=406533

Bug ID: 406533
   Summary: when the transformation tool is selected you can't see
the image/draw until you switch to another tool.
   Product: krita
   Version: 4.1.7
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Tools/Transform
  Assignee: krita-bugs-n...@kde.org
  Reporter: andersonicoderso...@gmail.com
  Target Milestone: ---

SUMMARY
when the transformation tool is selected you can't see the image/draw until you
switch to another tool.

STEPS TO REPRODUCE
1. select the transformation tool.
2. once selected you aren't able to see what you're doing to your work.
3. now select another tool, and you will see the changes.

OBSERVED RESULT

i can't see what i'm doing with my drawing till i switch to other tool, so the
result is a great horror and a lost of time.

EXPECTED RESULT

it's obvious, please. Sorry

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

ADDITIONAL INFORMATION

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

[kwin] [Bug 406526] Request: Removal of destructive window shortcuts

2019-04-14 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=406526

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #4 from David Edmundson  ---
alt+f4 is not an easy to press shortcut.

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

[elisa] [Bug 406499] elisa git fails to build on High Sierra

2019-04-14 Thread Yurii Kolesnykov
https://bugs.kde.org/show_bug.cgi?id=406499

--- Comment #5 from Yurii Kolesnykov  ---
According to 
https://github.com/KDE/elisa/blob/master/src/audiowrapper.h
https://github.com/KDE/elisa/blob/master/src/audiowrapper_qtmultimedia.cpp
https://github.com/KDE/elisa/blob/master/src/audiowrapper_libvlc.cpp

My suggestion is this lack of some libvlc/qtmultimedia and/or phonon?

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

[kwin] [Bug 406526] Request: Removal of destructive window shortcuts

2019-04-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=406526

--- Comment #5 from plane.wan...@gmail.com ---
(In reply to David Edmundson from comment #4)
> alt+f4 is not an easy to press shortcut.

That doesn't matter. An admin can change that shortcut to whatever they felt
like, e.g. , , ... which all do non-destructive
actions on other platforms, therefore users might accidentally trigger
destructive actions on KWin because they expected something else to happen for
those shortcuts. Therefore this feature needs to be removed - it's not
explicit/clear and might lead to data loss.

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

[okular] [Bug 406489] Can not save image in pdf file use okular

2019-04-14 Thread Oliver Sander
https://bugs.kde.org/show_bug.cgi?id=406489

Oliver Sander  changed:

   What|Removed |Added

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

--- Comment #6 from Oliver Sander  ---
Do you remember where that code is?

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

[kwin] [Bug 406526] Request: Removal of destructive window shortcuts

2019-04-14 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=406526

--- Comment #6 from David Edmundson  ---
Has this been an observed problem?

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

[krita] [Bug 406531] Crash after trying to merge down and saving with large file

2019-04-14 Thread Boudewijn Rempt
https://bugs.kde.org/show_bug.cgi?id=406531

--- Comment #6 from Boudewijn Rempt  ---
I tested on a 32gb system.

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

[krita] [Bug 406533] when the transformation tool is selected you can't see the image/draw until you switch to another tool.

2019-04-14 Thread Boudewijn Rempt
https://bugs.kde.org/show_bug.cgi?id=406533

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org
 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO

--- Comment #1 from Boudewijn Rempt  ---
No, sorry, it's not obvious. Please provide:

* a screenshot of what you're talking about.
* the output of help->system information for bug reports

And please test with the latest nightly build, too:
https://binary-factory.kde.org/job/Krita_Nightly_Windows_Build/

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

[kate] [Bug 406305] Add "Close file" button to inview notice about deleted file

2019-04-14 Thread Wyatt Childers
https://bugs.kde.org/show_bug.cgi?id=406305

Wyatt Childers  changed:

   What|Removed |Added

 CC||dark...@nearce.com

--- Comment #6 from Wyatt Childers  ---
I just saw this on the usability blog. I really think this should be changed to
"close file" or something more explicit. When I saw the screenshot in the blog,
my first thought was that the close button was for the notification -- which I
thought was odd, which brought me here.

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

[kwin] [Bug 406526] Request: Removal of destructive window shortcuts

2019-04-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=406526

--- Comment #7 from plane.wan...@gmail.com ---
(In reply to David Edmundson from comment #6)
> Has this been an observed problem?

Yes, like I said it can be easily reproduced.

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

[kwin] [Bug 395066] KWin crashes if while taking a screenshot I click on a panel

2019-04-14 Thread Cory F Cohen
https://bugs.kde.org/show_bug.cgi?id=395066

Cory F Cohen  changed:

   What|Removed |Added

 CC||cfco...@verizon.net

--- Comment #6 from Cory F Cohen  ---
Created attachment 119410
  --> https://bugs.kde.org/attachment.cgi?id=119410&action=edit
A shell log with GDB output, versions, config info, etc.

I'm also experiencing this bug in Kubuntu 18.10, with kwin 5.13.5 and Spectacle
version 18.04.3.  Set up is essentially identical to the previous report.   I
can add that I have two 4K monitors, and that I'm taking a screenshot of a
window that fills perhaps 75% of one of the two monitors.

GDB does not produce a useful backtrace (no stack), but does report:

The X11 connection broke: Maximum allowed requested length exceeded (code 4)
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
  after 17472 requests (17472 known processed) with 0 events remaining.

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

[kate] [Bug 406305] Add "Close file" button to inview notice about deleted file

2019-04-14 Thread Méven Car
https://bugs.kde.org/show_bug.cgi?id=406305

--- Comment #7 from Méven Car  ---
(In reply to Wyatt Childers from comment #6)
> I just saw this on the usability blog. I really think this should be changed
> to "close file" or something more explicit. When I saw the screenshot in the
> blog, my first thought was that the close button was for the notification --
> which I thought was odd, which brought me here.

I see your point and I agree, in fact I hesitate when I did the feature.
"Close file" would be better than "Close".

Review : https://phabricator.kde.org/D20542

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

[kwin] [Bug 406526] Request: Removal of destructive window shortcuts

2019-04-14 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=406526

--- Comment #8 from David Edmundson  ---
That's not what I meant, I meant if you've observed users accidentally closing
windows this way

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

[plasmashell] [Bug 358240] Legacy system tray icons are shown as white squares.

2019-04-14 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=358240

Patrick Silva  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

--- Comment #2 from Patrick Silva  ---
I can't reproduce on my system at least with pidgin 2.13.0.

Operating System: Arch Linux 
KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.57.0
Qt Version: 5.12.2

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

[kwin] [Bug 406526] Request: Removal of destructive window shortcuts

2019-04-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=406526

--- Comment #9 from plane.wan...@gmail.com ---
(In reply to David Edmundson from comment #8)
> That's not what I meant, I meant if you've observed users accidentally
> closing windows this way

I don't think my answer to that question should matter given that I could
easily lie and there would be no way to prove me wrong. But for the sake of the
argument I'll say: Yes, I observed it many times that users lost some data this
way.

Imho the important question is if the arguments make sense and given that those
same arguments were used to remove similar features in KWin before I thought
that they indeed do make sense to the project's goals.

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

[kwin] [Bug 340871] Applications open in background when opened from system tray

2019-04-14 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=340871

Patrick Silva  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

--- Comment #12 from Patrick Silva  ---
I can confirm with keepassx 0.4.4 Qt4 on Arch Linux.
Set focus stealing prevention to "None" solves the problem.

Operating System: Arch Linux 
KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.57.0
Qt Version: 5.12.2

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

[kwin] [Bug 385743] Kwin: Freeze/segfault when waking up an idle system on Wayland

2019-04-14 Thread miku84
https://bugs.kde.org/show_bug.cgi?id=385743

miku84  changed:

   What|Removed |Added

 CC||mik...@gmail.com

--- Comment #14 from miku84  ---
Hi,

I have the same with ATI r600 free driver. Is there any bug or workaround in
mesa for it? This is a blocker for me in wayland.
Thanks.

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

[frameworks-kunitconversion] [Bug 378967] Fuel consumption conversion incorrect

2019-04-14 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=378967

Albert Astals Cid  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kun
   ||itconversion/bc7495095baa7a
   ||70e756c4d2044de2197d1a4e3b
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #6 from Albert Astals Cid  ---
Git commit bc7495095baa7a70e756c4d2044de2197d1a4e3b by Albert Astals Cid, on
behalf of Michal Malý.
Committed on 14/04/2019 at 15:59.
Pushed by aacid into branch 'master'.

Fix l/100 km to MPG conversion

Summary:
Previous code (probably) worked only for l/100 km -> MPG but not the other way
around. Fix this by using reciprocal conversion when necessary.

Output:
38.7 MPG -> 6.077 l/100 km; 16.455 km/l; 46.482 MPGI
16.455 km/l -> 6.077 l/100 km; 38.7 MPG
46.48 MPGI -> 6.077 l/100 km

Seems good to me.

Reviewers: broulik, #frameworks, aacid

Subscribers: apol, aacid, meven, kde-frameworks-devel

Tags: #frameworks

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

M  +20   -0autotests/convertertest.cpp
M  +23   -9src/fuel_efficiency.cpp

https://commits.kde.org/kunitconversion/bc7495095baa7a70e756c4d2044de2197d1a4e3b

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

[okular] [Bug 406489] Can not save image in pdf file use okular

2019-04-14 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=406489

--- Comment #7 from Albert Astals Cid  ---
(In reply to Oliver Sander from comment #6)
> Do you remember where that code is?

ui/pageview.cpp
menu.addAction( new OKMenuTitle( &menu, i18n( "Image (%1 by %2
pixels)", selectionRect.width(), selectionRect.height() ) ) );

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

[kwin] [Bug 406534] New: KWin freezes when running this simple script

2019-04-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=406534

Bug ID: 406534
   Summary: KWin freezes when running this simple script
   Product: kwin
   Version: 5.15.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: scripting
  Assignee: kwin-bugs-n...@kde.org
  Reporter: tr...@yandex.com
  Target Milestone: ---

KWin freezes when running this simple script then close any window.
I don't know if there is something wrong with my script.

STEPS TO REPRODUCE
1. Install this simple script: https://github.com/trmdi/test
2. Open a new window, the sound is played as expected.
3. Close a window.

OBSERVED RESULT
KWin freezes.

EXPECTED RESULT
The window is closed and the sound is played without making KWin freeze.

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

[plasmashell] [Bug 406535] New: plasmashell crashing with freebsd, with kill Xorg and sddm again....

2019-04-14 Thread Miranda van den Breukelingen
https://bugs.kde.org/show_bug.cgi?id=406535

Bug ID: 406535
   Summary: plasmashell crashing with freebsd, with kill Xorg and
sddm again
   Product: plasmashell
   Version: master
  Platform: Other
OS: FreeBSD
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Desktop Containment
  Assignee: se...@kde.org
  Reporter: vanbreukelingen1...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 119411
  --> https://bugs.kde.org/attachment.cgi?id=119411&action=edit
Log file with backtrace being to long for the assistent...

Dr. Konqi crashes often when reporting bugs...

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

[kwin] [Bug 406526] Request: Removal of destructive window shortcuts

2019-04-14 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=406526

David Edmundson  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

--- Comment #10 from David Edmundson  ---
>I could easily lie

It would take a very odd sort of person to be disingenuous on a bug tracker.

However, it seems cfecks initial comments were right.
Thanks for wasting my time.

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

[plasmashell] [Bug 406535] plasmashell crashing with freebsd, with kill Xorg and sddm again....

2019-04-14 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=406535

David Edmundson  changed:

   What|Removed |Added

  Component|Desktop Containment |generic-crash
 CC||k...@davidedmundson.co.uk
   Assignee|se...@kde.org   |plasma-b...@kde.org
 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from David Edmundson  ---
Pasting inline

Crash is in Qt code, can you state what Qt and Plasma versions please

* thread #1, name = 'plasmashell'
  * frame #0: 0x000802e6984a libc.so.7`_nanosleep at _nanosleep.S:3
frame #1: 0x0008027d517c
libthr.so.3`__thr_nanosleep(time_to_sleep=,
time_remaining=) at thr_syscalls.c:289
frame #2: 0x000802dcfe0b libc.so.7`__sleep(seconds=1) at sleep.c:62
frame #3: 0x0008013b83ca
libKF5Crash.so.5`___lldb_unnamed_symbol6$$libKF5Crash.so.5 + 1450
frame #4: 0x0008013b7b3e
libKF5Crash.so.5`KCrash::defaultCrashHandler(int) + 1454
frame #5: 0x0008027d84b6
libthr.so.3`handle_signal(actp=0x7fffc0c0, sig=11,
info=0x7fffc4b0, ucp=0x7fffc140) at thr_sig.c:248
frame #6: 0x0008027d7a22 libthr.so.3`thr_sighandler(sig=11,
info=0x7fffc4b0, _ucp=0x7fffc140) at thr_sig.c:191
frame #7: 0x7fffe003
frame #8: 0x000800b1d0c2
libQt5Quick.so.5`QQuickItemViewTransitionableItem::startTransition(QQuickItemViewTransitioner*,
int) + 82
frame #9: 0x000806ce5cae
libQt5QuickTemplates2.so.5`___lldb_unnamed_symbol895$$libQt5QuickTemplates2.so.5
+ 158
frame #10: 0x000806ce3473
libQt5QuickTemplates2.so.5`QQuickStackView::replace(QQmlV4Function*) + 1251
frame #11: 0x000806d06e3a
libQt5QuickTemplates2.so.5`QQuickStackView::qt_metacall(QMetaObject::Call, int,
void**) + 122
frame #12: 0x000800e7d646
libQt5Qml.so.5`QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value
const, int) const + 1430
frame #13: 0x000800f12330
libQt5Qml.so.5`QV4::Runtime::method_callProperty(QV4::ExecutionEngine*,
QV4::Value*, int, QV4::Value, int) + 384
frame #14: 0x00081c2ba391
frame #15: 0x000800e94716
libQt5Qml.so.5`___lldb_unnamed_symbol2428$$libQt5Qml.so.5 + 198
frame #16: 0x000800e411df
libQt5Qml.so.5`___lldb_unnamed_symbol1662$$libQt5Qml.so.5 + 703
frame #17: 0x000800e81f44
libQt5Qml.so.5`___lldb_unnamed_symbol2174$$libQt5Qml.so.5 + 756
frame #18: 0x000802c58b0e
libQt5Core.so.5`QMetaObject::activate(QObject*, int, int, void**) + 1454
frame #19: 0x000800ac090a
libQt5Quick.so.5`QQuickImageBase::requestFinished(void) + 554
frame #20: 0x000800ac123e
libQt5Quick.so.5`QQuickImageBase::qt_metacall(QMetaObject::Call, int, void**) +
126
frame #21: 0x000800ac1bb8
libQt5Quick.so.5`QQuickImage::qt_metacall(QMetaObject::Call, int, void**) + 24
frame #22: 0x000802c5895c
libQt5Core.so.5`QMetaObject::activate(QObject*, int, int, void**) + 1020
frame #23: 0x000800972ffa
libQt5Quick.so.5`___lldb_unnamed_symbol1062$$libQt5Quick.so.5 + 842
frame #24: 0x000801c7e001
libQt5Widgets.so.5`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 273
frame #25: 0x000801c7f39d
libQt5Widgets.so.5`QApplication::notify(QObject*, QEvent*) + 589
frame #26: 0x000802c27881
libQt5Core.so.5`QCoreApplication::notifyInternal2(QObject*, QEvent*) + 161
frame #27: 0x000802c28749
libQt5Core.so.5`QCoreApplicationPrivate::sendPostedEvents(QObject*, int,
QThreadData*) + 857
frame #28: 0x000802c7cdc8
libQt5Core.so.5`___lldb_unnamed_symbol2553$$libQt5Core.so.5 + 24
frame #29: 0x000803eafb77 libglib-2.0.so.0`g_main_context_dispatch +
311

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

[kwin] [Bug 405971] [Wayland] "Fall apart" effect only should be triggered when a window is closed

2019-04-14 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=405971

--- Comment #4 from Patrick Silva  ---
On X11 the effect is also triggered when I minimize an app by clicking its icon
in systray.
For example, install SMPlayer and open it, click "Options" menu, check "Show
icon in system tray". Now minimize SMPlayer by clicking its systray icon: "Fall
apart" effect was triggered.

Operating System: Arch Linux 
KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.57.0
Qt Version: 5.12.2

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

[plasmashell] [Bug 406535] plasmashell crashing with freebsd, with kill Xorg and sddm again....

2019-04-14 Thread Miranda van den Breukelingen
https://bugs.kde.org/show_bug.cgi?id=406535

--- Comment #2 from Miranda van den Breukelingen 
 ---
It's plasma5 5.15.3_x and Qt 5.12.1

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

[lattedock] [Bug 406536] New: Regression: Lost ability to double click on a title/panel to maximize/unmaximize window

2019-04-14 Thread Michał Dybczak
https://bugs.kde.org/show_bug.cgi?id=406536

Bug ID: 406536
   Summary: Regression: Lost ability to double click on a
title/panel to maximize/unmaximize window
   Product: lattedock
   Version: git (master)
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: michal.dybc...@gmail.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Install latest latte-dock-git (based on PKGBUILD in AUR)
2. Restart latte
3. Open any window and double click on a panel where window title applet or the
empty space between global menu and systray is.

OBSERVED RESULT

Nothing happens.

EXPECTED RESULT

A focused window should maximize/unmaximize on panel's double click.


SOFTWARE/OS VERSIONS

Operating System: Manjaro Linux 
KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.56.0
Qt Version: 5.12.2
Kernel Version: 5.0.7-1-MANJARO
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz
Memory: 7,7 GiB


ADDITIONAL INFORMATION

Downgrading to the git build that I did on 30.03.2019 fixes the issue so the
bug happened somewhere between 31.03-13.04.

I learned to relay on this double click as it's super convienient because there
is a big surface area where I can double click vs. small unmaximize/maximize
buttons, So for me this a very important regression.

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

[lattedock] [Bug 406536] Regression: Lost ability to double click on a title/panel to maximize/unmaximize window

2019-04-14 Thread Michail Vourlakos
https://bugs.kde.org/show_bug.cgi?id=406536

--- Comment #2 from Michail Vourlakos  ---
Have you enabled the option for this in Bahavior page?

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

[lattedock] [Bug 406536] Regression: Lost ability to double click on a title/panel to maximize/unmaximize window

2019-04-14 Thread Michail Vourlakos
https://bugs.kde.org/show_bug.cgi?id=406536

--- Comment #1 from Michail Vourlakos  ---
Have you enabled the option for this in Bahavior page?

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

[kmymoney] [Bug 406537] New: Encrypted file cannot be saved as unencrypted

2019-04-14 Thread Thomas Baumgart
https://bugs.kde.org/show_bug.cgi?id=406537

Bug ID: 406537
   Summary: Encrypted file cannot be saved as unencrypted
   Product: kmymoney
   Version: 5.0.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: file
  Assignee: kmymoney-de...@kde.org
  Reporter: tbaumg...@kde.org
  Target Milestone: ---

SUMMARY
If a file is stored encrypted and later saved as unencrypted, the encryption
returns if the file is saved again.

STEPS TO REPRODUCE
1. Open encrypted file
2. "Save as" under different name w/o an encryption key
3. Restart application
4. Open unencrypted file (if it is not opened as last file used)
5. Make a modification
6. Save file

OBSERVED RESULT
File is encrypted again

EXPECTED RESULT
File is not encrypted

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

[kwin] [Bug 405971] [Wayland] "Fall apart" effect only should be triggered when a window is closed

2019-04-14 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=405971

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #5 from David Edmundson  ---
>On Wayland we don't have window types yet

It's not something anyone has requested on xdgshell. If we do want this, one of
us needs to actually request it on wayland-devel.

>I think isPopupWindow() could be used to filter out popups though not 
>dialogs... 

Seems sensible.

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

[kmymoney] [Bug 406537] Encrypted file cannot be saved as unencrypted

2019-04-14 Thread Thomas Baumgart
https://bugs.kde.org/show_bug.cgi?id=406537

Thomas Baumgart  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kmy
   ||money/a366b51e40a6f7a4d9d1b
   ||06b07e677892313c60e
 Status|REPORTED|RESOLVED
   Version Fixed In||5.0.4

--- Comment #1 from Thomas Baumgart  ---
Git commit a366b51e40a6f7a4d9d1b06b07e677892313c60e by Thomas Baumgart.
Committed on 14/04/2019 at 17:36.
Pushed by tbaumgart into branch '5.0'.

Do not re-encrypt file

This change allows to remove encryption permanently.
FIXED-IN: 5.0.4

M  +9-0kmymoney/plugins/xml/xmlstorage.cpp

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

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

[dolphin] [Bug 406538] New: Feature Requests for a more intuitive user experience

2019-04-14 Thread Julius R.
https://bugs.kde.org/show_bug.cgi?id=406538

Bug ID: 406538
   Summary: Feature Requests for a more intuitive user experience
   Product: dolphin
   Version: 18.12.3
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: kont...@juliusreich.de
CC: elvis.angelac...@kde.org
  Target Milestone: ---

Dear Mr Penz, Reininghaus, Pescocsta and Angelaccio,
first and foremost I would like to express my deepest gratitude for your
contribution to the world, which is in this case, one of the best filemanagers
for Linux. It is people like you who make it possible for someone like me, to
finally get rid of proprietary systems and corporations - in my case, switching
from Windows to Manjaro Linux and KDE. Thank you!

But, not all is evil in the Windows world and there are some cases, in which we
can learn from. I noticed a couple of possible improvements, which will
certainly lead to an even better, more intuitive user experience. My feature
requests are:

1) When using multible tabs, the text-align of the folders name is left. This
is sth the windows explorer does better. With large folder structes, the
left-aligned text shows the root of the tabs folder, it obscures the name of
the folder, the user is currently looking at. The text aligment should be
right.
Example: /home/user/documents/private/finances/2019 becomes
/home/user/documents/private/... instead if .../documents/private/finances/2019

2) It is not possible to detach or attach tabs via drag and drop. This is a
quite common feature for all tab enviroments, e.g. Firefox or other file
managers. This feature would highly increase the workflow.

3) This is the best feature I ever found in a filemanager: Incremental inline
search. I stumbled across this in an addon called qttabs for windows explorer.
What it does is primarily searching for a filename, while typing it. But not
restricted to the beginning of the file. Example: kwalletmanager.ending. If the
user types "wallet" or "walletmanager" it will not be found. Incremental inline
search would be a feature, that would skyrocket usability. Of course, it must
be restricted to folders with less than (n) number of files for performance
reasons, but still, this feature became a must have for me and I severely miss
it, now that I switched to KDE.

4) A simple, but undescribebly useful workflow function: Go one level up, when
double clicking on white space within a folder. This also comes from qttabs for
windows explorer and it increased my workflow tremendously.


That is all from side :)

Again, thank you very much for your hard efforts!

With regards
Julius R.

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

[frameworks-kglobalaccel] [Bug 406426] kglobalaccel5 crashes often

2019-04-14 Thread David Faure
https://bugs.kde.org/show_bug.cgi?id=406426

David Faure  changed:

   What|Removed |Added

 CC||fa...@kde.org

--- Comment #7 from David Faure  ---

-Q_FOREACH(GlobalShortcut *sc, shortcutContext(context)->_actions)
+for (GlobalShortcut *sc :
qAsConst(shortcutContext(context)->_actions))

This is probably the problem. qAsConst cannot be used for temporaries, because
the temporary goes out of scope before the result is used.

src/runtime/component.cpp around line 330

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

[frameworks-kglobalaccel] [Bug 406426] kglobalaccel5 crashes often

2019-04-14 Thread David Faure
https://bugs.kde.org/show_bug.cgi?id=406426

--- Comment #8 from David Faure  ---
Here's a generic way to detect such problems:

ag -sr qAsConst'\([^)]*\(' .

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

[kwin] [Bug 406526] Request: Removal of destructive window shortcuts

2019-04-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=406526

--- Comment #11 from plane.wan...@gmail.com ---
(In reply to David Edmundson from comment #10)
> >I could easily lie
> 
> It would take a very odd sort of person to be disingenuous on a bug tracker.

Then you can assume I'm telling the truth, but I don't know why an anecdote of
a single user should have any relevance whatsoever. Like does it make a
difference if I witnessed this issue 5 times, or 10 times? And how often is
enough for this to become important? Also the last time the same arguments were
used to justify the removal of similar features in KWin it didn't matter if it
actually happened to anyone.

> However, it seems cfecks initial comments were right.
> Thanks for wasting my time.

I didn't make this personal, I didn't make this OT, I didn't break any Code of
Conduct, all I did was putting forward arguments why destructive window
shortcuts are an issue in my oppinion. But instead of arguing about the issue,
which I'd much rather do, I have to deal with ad hominem attacks.

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

[okular] [Bug 402779] Okular, when printing 2 pages per sheet, prints the wrong pages.

2019-04-14 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=402779

Albert Astals Cid  changed:

   What|Removed |Added

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

--- Comment #2 from Albert Astals Cid  ---
yes, this is a bug in Qt. Please report it to https://bugreports.qt.io/ and
tell us the bug number so we can keep track.

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

[frameworks-kglobalaccel] [Bug 406426] kglobalaccel5 crashes often

2019-04-14 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=406426

--- Comment #9 from Laurent Montel  ---
I can't reproduce the crash...

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

[frameworks-kglobalaccel] [Bug 406426] kglobalaccel5 crashes often

2019-04-14 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=406426

--- Comment #10 from Laurent Montel  ---
(In reply to David Faure from comment #7)
> -Q_FOREACH(GlobalShortcut *sc, shortcutContext(context)->_actions)
> +for (GlobalShortcut *sc :
> qAsConst(shortcutContext(context)->_actions))
> 
> This is probably the problem. qAsConst cannot be used for temporaries,
> because the temporary goes out of scope before the result is used.
> 
> src/runtime/component.cpp around line 330

interesting.
"ag -sr qAsConst'\([^)]*\(' ." thanks for command

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

[kwin] [Bug 406539] New: Hot corners are hard to activate

2019-04-14 Thread Björn Feber
https://bugs.kde.org/show_bug.cgi?id=406539

Bug ID: 406539
   Summary: Hot corners are hard to activate
   Product: kwin
   Version: git master
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: febe...@gmail.com
  Target Milestone: ---

Created attachment 119412
  --> https://bugs.kde.org/attachment.cgi?id=119412&action=edit
Very Hard Hot Corner Activation

SUMMARY
(At least on my system, with default KDE neon/upstream settings) hot corners
are very hard to activate, as seen in the video. If you reduce the activation
delay to 100ms or 50ms it works much better.

STEPS TO REPRODUCE
1. Try to activate a hot corner

OBSERVED RESULT
Hot corners are very hard to activate (see video).

EXPECTED RESULT
Hot corners should be easy to activate.

SOFTWARE/OS VERSIONS
KDE Plasma Version: Git Master or lower
KDE Frameworks Version: 5.58 or lower
Qt Version: 5.12 or lower

ADDITIONAL INFORMATION
Proprietary Nvidia graphics drivers, running on Xorg.

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

[frameworks-kglobalaccel] [Bug 406426] kglobalaccel5 crashes often

2019-04-14 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=406426

--- Comment #11 from Laurent Montel  ---
ag is a command line from "the_silver_searcher" package

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

[Qt/KDE Flatpak Runtime] [Bug 405599] Falkon doesn't work on wayland

2019-04-14 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=405599

Aleix Pol  changed:

   What|Removed |Added

Summary|Cannot run natively on  |Falkon doesn't work on
   |Wayland KDE apps installled |wayland
   |on Gnome via|
   |flatpak/flathub |

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

[Qt/KDE Flatpak Runtime] [Bug 405599] Falkon doesn't work on wayland

2019-04-14 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=405599

Aleix Pol  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #4 from Aleix Pol  ---
I can confirm. On Plasma Wayland it happens as well, non-flatpak falkon works
fine.

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

[digikam] [Bug 406540] New: Add Metatags to Canon Raw

2019-04-14 Thread Lars Grabner
https://bugs.kde.org/show_bug.cgi?id=406540

Bug ID: 406540
   Summary: Add Metatags to Canon Raw
   Product: digikam
   Version: 6.0.0
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Metadata-Raw
  Assignee: digikam-bugs-n...@kde.org
  Reporter: larsgrab...@gmx.de
  Target Milestone: ---

SUMMARY
Write Metatags to RAW File (Canon) dosen´t work. (Like in version 4)

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

[frameworks-kglobalaccel] [Bug 406426] kglobalaccel5 crashes often

2019-04-14 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=406426

Laurent Montel  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
  Latest Commit||https://commits.kde.org/kgl
   ||obalaccel/abe32ec599397bda0
   ||ce73471519410bee2c16059
 Resolution|--- |FIXED

--- Comment #12 from Laurent Montel  ---
Git commit abe32ec599397bda0ce73471519410bee2c16059 by Laurent Montel.
Committed on 14/04/2019 at 18:25.
Pushed by mlaurent into branch 'master'.

Don't use qAsConst over a temporary variable

Summary: BUG: 406426

Reviewers: dfaure

Reviewed By: dfaure

Subscribers: kde-frameworks-devel

Tags: #frameworks

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

M  +2-1src/runtime/component.cpp

https://commits.kde.org/kglobalaccel/abe32ec599397bda0ce73471519410bee2c16059

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

[korganizer] [Bug 406411] Korganizer daemon closes when plasma starts

2019-04-14 Thread Wolfgang Bauer
https://bugs.kde.org/show_bug.cgi?id=406411

--- Comment #7 from Wolfgang Bauer  ---
*** Bug 406430 has been marked as a duplicate of this bug. ***

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

[korganizer] [Bug 406430] korganizer chrashes

2019-04-14 Thread Wolfgang Bauer
https://bugs.kde.org/show_bug.cgi?id=406430

Wolfgang Bauer  changed:

   What|Removed |Added

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

--- Comment #3 from Wolfgang Bauer  ---
Let's mark it as duplicate then, I looked again and the backtraces are indeed
exactly the same.

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

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

[kwin] [Bug 406534] KWin freezes when running this simple script

2019-04-14 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=406534

--- Comment #1 from Martin Flöser  ---
Please attach gdb and get a backtrace of the freeze.

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

[korgac] [Bug 406521] korgac crash on start up

2019-04-14 Thread Wolfgang Bauer
https://bugs.kde.org/show_bug.cgi?id=406521

Wolfgang Bauer  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE
 CC||wba...@tmo.at

--- Comment #2 from Wolfgang Bauer  ---


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

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

  1   2   >