[kate] [Bug 388239] New: kate long line wrapping only works after restart

[bugzilla_noreply]

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

Bug ID: 388239
   Summary: kate long line wrapping only works after restart
   Product: kate
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: krichter...@aol.de
  Target Milestone: ---

Created attachment 109524
  --> https://bugs.kde.org/attachment.cgi?id=109524=edit
allows to reproduce (open in another editor and paste into kate)

When creating extremely long lines in `kate` (most likely through pasting), the
view jumps to the end of the line when scrolling down and to the beginning when
scrolling up which makes it impossible to read the middle. This issues is
avoided after a restart when `kate` provides a view with line breaks (and an
option to save it).

The scrolling shouldn't be different for long lines because not only the
skipping of the middle part is an issue, but the jumping of the scroll interval
as well.

A possible use case is pasting web server integration test logs containing
base64-encoded screenshot which are ready to run on a headless CI server. A few
100 KB in one base64-encoded line can easily have a few million characters.
Even it the use case is rare, `kate` should be capable of handling it.

experienced with 17.08.3 on Kubuntu 18.04-daily

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

[kwin] [Bug 388230] KWin crashes all the time.

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Martin Flöser  ---
Crash happens in the Radeon driver. Please report to Radeon developers.

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

[kwin] [Bug 388224] KWin Crash Tabbing from Discord to Chromium

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Martin Flöser  ---
Crash happens in the Radeon driver. Please report to Radeon developers.

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

[kmail2] [Bug 374395] Its not possible to hide menu bar in email editor (Ctrl + M).

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||5.8.0
 CC||mon...@kde.org
 Status|UNCONFIRMED |RESOLVED

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

[kmail2] [Bug 374926] Printout of Mails with umlauts from kmail 5.3 isn´t possible

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||mon...@kde.org
 Resolution|--- |FIXED

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

[kmail2] [Bug 374992] provide a way to reorder the list of favorite folders

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||mon...@kde.org
 Resolution|--- |FIXED
   Version Fixed In||5.8.0

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

[ksmserver] [Bug 388208] Login screen doesn't allow to type normally and show virtual keyboard

[Pawel]

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

Pawel  changed:

   What|Removed |Added

 CC||pavbara...@gmail.com

--- Comment #1 from Pawel  ---
It looks like qt5/sddm problem, not related to ksmserver.

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

[kbreakout] [Bug 337439] Slugish performance, bad bounce angles, levels clear prematurely, and mouse problems.

[cl . emence]

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

cl.eme...@giroll.org  changed:

   What|Removed |Added

 CC||cl.eme...@giroll.org

--- Comment #2 from cl.eme...@giroll.org  ---
My father have same problems, in debian Jessie, 32 bit
Since his upgrade from Wheezy to Jessie, for this game, he use the wheezy
package and force the pakage version to not upgrade ( paquet 4:4.8.4-3).
The issue still exist today. We have done verification this week.

Issues are erratic, starting from level 7.

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

[kmail2] [Bug 381714] Cancelling sieve management operation has no effect

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

   Version Fixed In||5.7.1
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/lib
   ||ksieve/bb78894acfa86d09b827
   ||4c193bfe23a5a02e5749
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Laurent Montel  ---
Git commit bb78894acfa86d09b8274c193bfe23a5a02e5749 by Laurent Montel.
Committed on 26/12/2017 at 06:59.
Pushed by mlaurent into branch 'Applications/17.12'.

Fix Bug 381714 - Cancelling sieve management operation has no effect

FIXED-IN: 5.7.1

M  +1-1src/ksieveui/widgets/managesievewidget.cpp

https://commits.kde.org/libksieve/bb78894acfa86d09b8274c193bfe23a5a02e5749

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

[krita] [Bug 388238] New: Extension to the Particle Brush Engine - Add Color Source

[bugzilla_noreply]

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

Bug ID: 388238
   Summary: Extension to the Particle Brush Engine - Add Color
Source
   Product: krita
   Version: 4.0 pre-alpha
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Brush engines
  Assignee: krita-bugs-n...@kde.org
  Reporter: reptilli...@live.com
  Target Milestone: ---

Inspired by Flame Painter, I noticed that Particle Brush seem to be lacking in
comparison with Flame Painter, and you have to go through all the trouble
adding gradient map filter mask/layer, and clone your painting layer, and apply
destination in just to get similar effect. So, my suggestion is to support
adding randomization of colors via alpha information, and gradient map color
utilizing alpha information, and allowing rainbow stroke using stroke line as
reference. 

To clarify:

For randomization of colors via alpha information, it shall use shifting color
with random values,using alpha information, and if you zoom in closely, the
colors are smooth during the transition.

And then, gradient map via alpha information. That would be hard to emulate,
but I think it use alpha information as the base for generating colors on the
particle brush.

And finally, there should be an option to allow rainbow stroke using your
stroke line as information as to values of color going by rainbow path.

These are extension of particle engine I believe artists would find useful.

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

[krita] [Bug 388237] Add "Ignore Alpha" to Smudge Brush or "preserve existing alpha"

[bugzilla_noreply]

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

--- Comment #1 from reptilli...@live.com ---
Also, I forgot to add, I noticed that smudging does not build up alpha value as
much as what would be seen on traditional media. A option to increase alpha
build-up would be greatly appreciated by those who wants more traditional media
approach.

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

[krita] [Bug 388237] New: Add "Ignore Alpha" to Smudge Brush or "preserve existing alpha"

[bugzilla_noreply]

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

Bug ID: 388237
   Summary: Add "Ignore Alpha" to Smudge Brush or "preserve
existing alpha"
   Product: krita
   Version: 4.0 pre-alpha
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Brush engines
  Assignee: krita-bugs-n...@kde.org
  Reporter: reptilli...@live.com
  Target Milestone: ---

Something I noticed when it comes to testing Krita painting capability is that
alpha do get smudged over color. For artists that would like to avoid this, I
would suggest a way to somehow limit the effect of smudging alpha as sort of a
option or somehow to preserve alpha of already painted information. 

In real life, think of two painted areas with noticeable mass, and you blend in
the two, it behaves differently than in Krita. I don't know how to explain
this, but I believe this will significantly make Krita more viable for painting
as the main goal. There should be someway to limit alpha smudging.

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

[plasmashell] [Bug 388236] New: Crash when starting x2goclient

[Gene]

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

Bug ID: 388236
   Summary: Crash when starting x2goclient
   Product: plasmashell
   Version: 5.8.7
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: gene...@yahoo.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.7)

Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.4.92-31-default x86_64
Distribution: "openSUSE Leap 42.3"

-- Information about the crash:
1. started x2go client from menu
2. plasmashell crashed and restarted

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6f7d854900 (LWP 3558))]

Thread 25 (Thread 0x7f6eaa38b700 (LWP 17222)):
#0  0x7f6f76d6428d in read () at /lib64/libc.so.6
#1  0x7f6f6c336931 in pa_read () at
/usr/lib64/pulseaudio/libpulsecommon-9.0.so
#2  0x7f6f6c9bf3be in pa_mainloop_prepare () at /usr/lib64/libpulse.so.0
#3  0x7f6f6c9bfdd2 in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0
#4  0x7f6f6c9bfe90 in pa_mainloop_run () at /usr/lib64/libpulse.so.0
#5  0x7f6f6c9ce006 in  () at /usr/lib64/libpulse.so.0
#6  0x7f6f6c365408 in  () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so
#7  0x7f6f76571744 in start_thread () at /lib64/libpthread.so.0
#8  0x7f6f76d70aad in clone () at /lib64/libc.so.6

Thread 24 (Thread 0x7f6eaf964700 (LWP 17220)):
#0  0x7f6f76d6820d in poll () at /lib64/libc.so.6
#1  0x7f6f73419314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f6f7341942c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f6f776751ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f6f77622bfb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f6f7745df5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f6f7a76b3d8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f6f77462a29 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f6f76571744 in start_thread () at /lib64/libpthread.so.0
#9  0x7f6f76d70aad in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7f6eb1d07700 (LWP 4919)):
#0  0x7f6f765760bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f6f7746369b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f6ecff5b42f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f6ecff5edea in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f6ecff5945b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f6ecff5ee32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f6ecff5945b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f6ecff5ca46 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f6f77462a29 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f6f76571744 in start_thread () at /lib64/libpthread.so.0
#10 0x7f6f76d70aad in clone () at /lib64/libc.so.6

Thread 22 (Thread 0x7f6eb2508700 (LWP 4918)):
#0  0x7f6f765760bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f6f7746369b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f6ecff5b42f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f6ecff5edea in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f6ecff5945b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f6ecff5ee32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f6ecff5945b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f6ecff5ee32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f6ecff5945b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7f6ecff5ee32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7f6ecff5945b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#11 0x7f6ecff5ca46 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#12 0x7f6f77462a29 in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f6f76571744 in start_thread () at /lib64/libpthread.so.0
#14 0x7f6f76d70aad in clone () at /lib64/libc.so.6

[kmail2] [Bug 382562] Hidden menu in kmail composer: no (obvious?) way to get it back (or hide it)

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kma
   ||il/f1bafd1a4e30ea1ab1bf1bf2
   ||d57adf3322a8b27e
   Version Fixed In||5.8.0

--- Comment #3 from Laurent Montel  ---
Git commit f1bafd1a4e30ea1ab1bf1bf2d57adf3322a8b27e by Laurent Montel.
Committed on 26/12/2017 at 06:03.
Pushed by mlaurent into branch 'master'.

Fix Bug 382562 - Hidden menu in kmail composer: no (obvious?) way to get it
back (or hide it)

FIXED-IN: 5.8.0

(adding action for show or not menubar)

M  +26   -0src/editor/kmcomposerwin.cpp
M  +3-0src/editor/kmcomposerwin.h
M  +2-1src/kmcomposerui.rc
M  +7-0src/settings/kmail.kcfg.cmake

https://commits.kde.org/kmail/f1bafd1a4e30ea1ab1bf1bf2d57adf3322a8b27e

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

[plasmashell] [Bug 388235] New: Plasma crash upon using Application launcher

[Vishnu]

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

Bug ID: 388235
   Summary: Plasma crash upon using Application launcher
   Product: plasmashell
   Version: 5.11.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: vishn...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.11.4)

Qt Version: 5.10.0
Frameworks Version: 5.41.0
Operating System: Linux 4.14.6-1-ARTIX x86_64
Distribution (Platform): Archlinux Packages

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

I had a Konsole terminal in fullscreen opened, and then I pressed the Super key
(which is my shortcut to Application launcher). The launcher comes up, and with
in a few seconds, crashes along with plasma.

- Unusual behavior I noticed:

The screen flickers as though gamma changes and is reset to normal.

The crash can be reproduced every time.

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

Thread 17 (Thread 0x7f96ac6bc700 (LWP 7385)):
[KCrash Handler]
#5  0x7f97161a1a23 in  () at /usr/lib/libsqlite3.so.0
#6  0x7f97161a202f in  () at /usr/lib/libsqlite3.so.0
#7  0x7f971619cfe1 in  () at /usr/lib/libsqlite3.so.0
#8  0x7f971612fd28 in  () at /usr/lib/libsqlite3.so.0
#9  0x7f9716136b4b in sqlite3BtreeMovetoUnpacked () at
/usr/lib/libsqlite3.so.0
#10 0x7f97161c198d in sqlite3VdbeExec () at /usr/lib/libsqlite3.so.0
#11 0x7f97161c83a0 in sqlite3_step () at /usr/lib/libsqlite3.so.0
#12 0x7f96fcdf2a2e in  () at /usr/lib/qt/plugins/sqldrivers/libqsqlite.so
#13 0x7f97caddf4d3 in QSqlCachedResult::cacheNext() () at
/usr/lib/libQt5Sql.so.5
#14 0x7f97cadca27e in QSqlQuery::next() () at /usr/lib/libQt5Sql.so.5
#15 0x7f96fd132ac6 in  () at /usr/lib/qt/plugins/krunner_bookmarksrunner.so
#16 0x7f96fd13a8ba in  () at /usr/lib/qt/plugins/krunner_bookmarksrunner.so
#17 0x7f96fd137f86 in  () at /usr/lib/qt/plugins/krunner_bookmarksrunner.so
#18 0x7f970437e8c0 in
Plasma::AbstractRunner::performMatch(Plasma::RunnerContext&) () at
/usr/lib/libKF5Runner.so.5
#19 0x7f96fedea618 in
ThreadWeaver::Executor::run(QSharedPointer const&,
ThreadWeaver::Thread*) () at /usr/lib/libKF5ThreadWeaver.so.5
#20 0x7f96fede9610 in
ThreadWeaver::Job::execute(QSharedPointer const&,
ThreadWeaver::Thread*) () at /usr/lib/libKF5ThreadWeaver.so.5
#21 0x7f96fede8d45 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#22 0x7f97cce1f86d in  () at /usr/lib/libQt5Core.so.5
#23 0x7f97cbfd408a in start_thread () at /usr/lib/libpthread.so.0
#24 0x7f97cc72742f in clone () at /usr/lib/libc.so.6

Thread 16 (Thread 0x7f96acebd700 (LWP 7384)):
#0  0x7f97cbfda38d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f97cce20d4c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f96fede642f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f96fedeb479 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f96fede5924 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f96fedeb4d2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f96fede5924 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f96fede8c83 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f97cce1f86d in  () at /usr/lib/libQt5Core.so.5
#9  0x7f97cbfd408a in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f97cc72742f in clone () at /usr/lib/libc.so.6

Thread 15 (Thread 0x7f96ad6be700 (LWP 7383)):
#0  0x7f97cbfda38d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f97cce20d4c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f96fede642f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f96fedeb479 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f96fede5924 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f96fedeb4d2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f96fede5924 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f96fede8c83 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f97cce1f86d 

[kmail2] [Bug 388080] kMail 5.7.0: Where is mail structure view gone?

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #1 from Laurent Montel  ---
You can readd it when you use "configure toolbar"

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

[flatpak-platform-plugin] [Bug 388234] New: flatpak-kde-runtime: Can't open file

[Peter Eszlari]

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

Bug ID: 388234
   Summary: flatpak-kde-runtime: Can't open file
   Product: flatpak-platform-plugin
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jgrul...@redhat.com
  Reporter: peter.eszl...@gmail.com
  Target Milestone: ---

https://github.com/flatpak/flatpak/issues/1276

I can't open a file in the following kde runtime based apps:

* io.mgba.mGBA (File -> Load ROM)
* org.fedoraproject.MediaWriter (Custom image)
* org.subsurface_divelog.Subsurface (File -> Open logbook)

It works in the following apps:

* net.mediaarea.MediaInfo (wxwidgets, gnome runtime)
* org.gnome.gedit (gnome runtime)
* org.videolan.VLC (freedesktop runtime)
* org.musescore.MuseScore (also kde runtime based, but working!)

Tested on Ubuntu 17.10 and Fedora 27.

I pretty sure, this must be kde runtime specfic, because when I compiled VLC
against it instead of the freedesktop runtime, the same problem occurs.

(I filed it under "flatpak-platform-plugin", because there is no product
"flatpak-kde-runtime".

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

[krita] [Bug 388233] New: DI-DPI displays canvas at 2x size in respect to zoom level

[Isaac]

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

Bug ID: 388233
   Summary: DI-DPI displays canvas at 2x size in respect to zoom
level
   Product: krita
   Version: 3.3.2
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: isaacnor...@live.com
  Target Milestone: ---

An example of this is a simple 1920x1080 sized canvas. If I set my canvas zoom
level to 100%, the canvas is portrayed twice it's actual set size. To view the
canvas at it's actual size, I must set the zoom level to 50%, only then will I
see the canvas at it's true size, 1920x1080.

If I uncheck "HI-DPI" in the options, Krita will load but the UI will be tiny
to where I cannot see things too well.

I have a 4k monitor with Windows 10 set to 200% scaling. If you need to know my
system specs for diagnostics, here's an image (from my Google Drive) showing
them:
https://drive.google.com/file/d/108i0YsxHwFrIDrRec3Gx47ydPmRVS4BA/view?usp=sharing

Is this something that can be fixed in a future release? It's not major, but it
will help with large images when having to view them at the proper zoom level.

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

[kaffeine] [Bug 388232] New: Provide Flatpak or AppImage for kaffeine

[Peter Eszlari]

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

Bug ID: 388232
   Summary: Provide Flatpak or AppImage for kaffeine
   Product: kaffeine
   Version: 2.0.13
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mchehab+...@kernel.org
  Reporter: peter.eszl...@gmail.com
  Target Milestone: ---

https://flatpak.org / https://flathub.org

I wanted to build a flatpak of kaffeine and publish it on flathub. Then I
noticed that libdvbv5 depends on libudev, which is not available in flatpak:

https://github.com/flatpak/flatpak/issues/961

On the other hand, mesa/libdrm removed their libudev support and one can access
/dev/dri from flatpak without problems. Maybe the same can be done for libdvbv5
(or make it optional).

An alternative for cross distro packaging would be AppImage. Not as convenient
as Flatpak, but it's able to link against host libraries:

https://appimage.org

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

[marble] [Bug 388089] luvbru

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

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

[umbrello] [Bug 388171] umbrello5 does not display any files using default file pattern

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

   Version Fixed In|2.24.2 (KDE Applications|2.24.1 (KDE Applications
   |17.12.2)|17.12.1)

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

[krita] [Bug 388215] I can't make a new layer

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

   Assignee|k.h...@gmx.de   |krita-bugs-n...@kde.org
  Component|general |Layer Stack
Product|abakus  |krita
   Severity|critical|normal

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

[ksmserver] [Bug 366156] ksmserver crashes when switching from nvidia to intel profile/GPU on laptop with hybrid graphics

[Robert]

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

Robert  changed:

   What|Removed |Added

 CC||robert.biel...@outlook.com

--- Comment #14 from Robert  ---
Same problem here on fully updated KDE neon 5.11.4. Have to restart using the
command line each time I want to switch the GPU. Only then can I use the other
video card.

This has been around for quite a while, it should be given higher priority.

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

[plasmashell] [Bug 387321] High CPU/GPU load after switching Display Port connected screen off and on in multi screen setup

[Jim Jones]

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

Jim Jones  changed:

   What|Removed |Added

   Severity|normal  |major

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

[krita] [Bug 388231] New: Can't use at all.

[bugzilla_noreply]

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

Bug ID: 388231
   Summary: Can't use at all.
   Product: krita
   Version: 3.3.2
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: brandonrobinson...@gmail.com
  Target Milestone: ---

Whenever I first get into Krita it allows me to do anything like normal, but if
I have a canvas and try to do anything it just won't do anything. I think it
might be lag from something but I can't really tell as I can't get it to do
anything besides closing the canvas, exiting out, or hitting a couple tool and
what not.

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

[krita] [Bug 349459] Improvements for the reference image docker.

[Isaac]

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

Isaac  changed:

   What|Removed |Added

 CC||isaacnor...@live.com

--- Comment #17 from Isaac  ---
Sorry for the late comment posting, but what Magnamara69 said, that would be
nice. I'm glad that I searched for this before submitting my wishlist report,
because I was having a similar experience.

It would be nice to have basic canvas controls over the reference image docker
when using it.

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

[yakuake] [Bug 361725] Yakuake task appears in the task manager some times, when opening Yakuake with hotkey

[Bart]

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

Bart  changed:

   What|Removed |Added

 CC||bart.po...@gmail.com

--- Comment #5 from Bart  ---
Same here, up to date Arch Linux 

QT 5.10
KDE 5.41
Yakuake 3.0.4

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

[digikam] [Bug 385280] digikam does not use the native Plasma file dialog under Plasma

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|general |Usability-Ergonomy

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

[digikam] [Bug 388222] high RAM memory consumption of digiKam

[bugzilla_noreply]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com
  Component|general |Bundle-Windows

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

[digikam] [Bug 387168] No Plugins loaded marble

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|general |Geolocation
 CC||caulier.gil...@gmail.com

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

[digikam] [Bug 387372] With Digikam Version 5.7 is no preview possible

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|general |Albums-MainView

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

[digikam] [Bug 385507] Digikam crash at startup

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|general |Database-Similarity

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

[digikam] [Bug 386891] Crashed while adding pictures

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|general |Metadata-Video

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

[kipiplugins] [Bug 384826] Flickr export broken

[bugzilla_noreply]

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

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

   What|Removed |Added

   Assignee|digikam-bugs-n...@kde.org   |imaging-bugs-n...@kde.org
 CC||caulier.gil...@gmail.com
  Component|general |Flickr
Product|digikam |kipiplugins

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

[kwin] [Bug 388230] New: KWin crashes all the time.

[Daniel Ziltener]

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

Bug ID: 388230
   Summary: KWin crashes all the time.
   Product: kwin
   Version: 5.11.4
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: dzilte...@lyrion.ch
  Target Milestone: ---

Application: kwin_x11 (5.11.4)

Qt Version: 5.9.3
Frameworks Version: 5.40.0
Operating System: Linux 4.14.6-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed: I was normally using KDE with
a few open windows. Nothing special, really. Radeon RX580, and have selected
OpenGL 3.1. It crashes about a dozen times every day, during Alt+Tab. Seems
more likely when one of the windows has content like a playing video or a VM.
Most of the time I have to manually start kwin_x11 again.

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6407139dc0 (LWP 23319))]

Thread 13 (Thread 0x7f63d2fa4700 (LWP 23337)):
#0  0x7f63ffadf82d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f63d09dd06b in  () at /usr/lib64/dri/radeonsi_dri.so
#2  0x7f63d09dcf87 in  () at /usr/lib64/dri/radeonsi_dri.so
#3  0x7f63ffad9558 in start_thread () at /lib64/libpthread.so.0
#4  0x7f6406ab76df in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7f63b77fe700 (LWP 23334)):
#0  0x7f63ffadf82d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f640304d554 in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f640304d599 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f63ffad9558 in start_thread () at /lib64/libpthread.so.0
#4  0x7f6406ab76df in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7f63c4bd0700 (LWP 23332)):
#0  0x7f63ffadf82d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f63d09dd06b in  () at /usr/lib64/dri/radeonsi_dri.so
#2  0x7f63d09dcf87 in  () at /usr/lib64/dri/radeonsi_dri.so
#3  0x7f63ffad9558 in start_thread () at /lib64/libpthread.so.0
#4  0x7f6406ab76df in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7f63c53d1700 (LWP 23331)):
#0  0x7f63ffadf82d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f63d09dd06b in  () at /usr/lib64/dri/radeonsi_dri.so
#2  0x7f63d09dcf87 in  () at /usr/lib64/dri/radeonsi_dri.so
#3  0x7f63ffad9558 in start_thread () at /lib64/libpthread.so.0
#4  0x7f6406ab76df in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7f63c5bd2700 (LWP 23330)):
#0  0x7f63ffadf82d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f63d09dd06b in  () at /usr/lib64/dri/radeonsi_dri.so
#2  0x7f63d09dcf87 in  () at /usr/lib64/dri/radeonsi_dri.so
#3  0x7f63ffad9558 in start_thread () at /lib64/libpthread.so.0
#4  0x7f6406ab76df in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f63c63d3700 (LWP 23329)):
#0  0x7f63ffadf82d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f63d09dd06b in  () at /usr/lib64/dri/radeonsi_dri.so
#2  0x7f63d09dcf87 in  () at /usr/lib64/dri/radeonsi_dri.so
#3  0x7f63ffad9558 in start_thread () at /lib64/libpthread.so.0
#4  0x7f6406ab76df in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f63c6bd4700 (LWP 23328)):
#0  0x7f63ffadf82d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f63d09dd06b in  () at /usr/lib64/dri/radeonsi_dri.so
#2  0x7f63d09dcf87 in  () at /usr/lib64/dri/radeonsi_dri.so
#3  0x7f63ffad9558 in start_thread () at /lib64/libpthread.so.0
#4  0x7f6406ab76df in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f63c73d5700 (LWP 23327)):
#0  0x7f63ffadf82d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f63d09dd06b in  () at /usr/lib64/dri/radeonsi_dri.so
#2  0x7f63d09dcf87 in  () at /usr/lib64/dri/radeonsi_dri.so
#3  0x7f63ffad9558 in start_thread () at /lib64/libpthread.so.0
#4  0x7f6406ab76df in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f63c7ddb700 (LWP 23326)):
#0  0x7f63ffadf82d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f63d09dd06b in  () at /usr/lib64/dri/radeonsi_dri.so
#2  0x7f63d09dcf87 in  () at /usr/lib64/dri/radeonsi_dri.so
#3  0x7f63ffad9558 in start_thread () at /lib64/libpthread.so.0
#4  0x7f6406ab76df in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f63c85dc700 (LWP 23325)):
#0  0x7f63ffadf82d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f63d09dd06b in  () at /usr/lib64/dri/radeonsi_dri.so
#2  0x7f63d09dcf87 in  () at /usr/lib64/dri/radeonsi_dri.so
#3  

[homerun] [Bug 388229] New: This refers to Plasma/Kickoff which I could not locate in the menu; please redirect appropriately if necessary

[bugzilla_noreply]

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

Bug ID: 388229
   Summary: This refers to Plasma/Kickoff which I could not locate
in the menu; please redirect appropriately if
necessary
   Product: homerun
   Version: 1.2.5
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: homerun-bugs-n...@kde.org
  Reporter: colleagu...@protonmail.com
CC: h...@kde.org
  Target Milestone: ---

KDE plasmas vers 5.8.6
KDE vers FW 5.28.0
Qt vers 5.7.1

open k launcher, left and icon, and the menu appears but you cannot search in
the search menu. This also affects dialog boxes asking for credentials but
seemingly nothing else in the system. I believe it has something to do keyboard
layout; when installing the OS I selected UK English, and this is what it
displayed upon login. But it was in practice a us layout. I went into the
layout settings and there were no layout there, I added English uk and shortly
after that I noticed this bug. Changing it back does not solve the issue. 
This is a security issue as I have to write passwords in clear when the system
requires authentication i.e. synaptic and  system operation related dialogs for
which the system needs authorisation.

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

[KScreen] [Bug 355396] dual monitor become single after reboot

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Keywords||usability

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

[KScreen] [Bug 355396] dual monitor become single after reboot

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[plasmashell] [Bug 375053] enabling global menu breaks copy/paste shortcuts in qupzilla

[Antonio Rojas]

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

Antonio Rojas  changed:

   What|Removed |Added

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

--- Comment #16 from Antonio Rojas  ---
Still valid

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

[qca] [Bug 379810] qca compilation fails with openssl 1.1

[Christian Fowelin]

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

Christian Fowelin  changed:

   What|Removed |Added

 CC|c...@fowelin.de  |

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

[qca] [Bug 379810] qca compilation fails with openssl 1.1

[Christian Fowelin]

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

Christian Fowelin  changed:

   What|Removed |Added

 CC||c...@fowelin.de

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

[digikam] [Bug 328855] Manual geotagging is unintuitive or misleading

[Maik Qualmann]

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

--- Comment #4 from Maik Qualmann  ---
*** Bug 388221 has been marked as a duplicate of this bug. ***

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

[digikam] [Bug 388221] almost impossible to change location of an image

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #7 from Maik Qualmann  ---


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

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

[digikam] [Bug 328855] Manual geotagging is unintuitive or misleading

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||uwesto...@web.de

--- Comment #3 from Maik Qualmann  ---
*** Bug 388219 has been marked as a duplicate of this bug. ***

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

[digikam] [Bug 388219] setting location for images has inconvenient workflow

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #3 from Maik Qualmann  ---


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

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

[okular] [Bug 388228] New: Okular crashes when annotating a piece of text

[Jonathan Schmidt-Dominé]

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

Bug ID: 388228
   Summary: Okular crashes when annotating a piece of text
   Product: okular
   Version: 1.1.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: de...@the-user.org
  Target Milestone: ---

Hi, I’m using Kubuntu 17.10 with Okular 1.1.3. When highlighting a piece of
text (markup annotation) okular crashes from time to time. It is not easily
reproducible (when I try to highlight the same word again after the crash, it
usually works), but it occurs quite often (after some dozens of annotations
okular crashes again). I have the problem since upgrading from Kubuntu 17.04 to
17.10. The crash occurs when releasing the mouse button after having marked a
segment of the text.

This is the backtrace which I get from gdb:
Thread 1 "okular" received signal SIGSEGV, Segmentation fault.
0x7fffe00169c0 in ?? ()

#0  0x7fffe00169c0 in ?? ()
#1  0x7fffdab5a286 in MouseAnnotation::cursor (this=0x574cb090) at
./ui/pageviewmouseannotation.cpp:379
#2  0x7fffdab5f88c in PageView::updateCursor
(this=this@entry=0x574dcd50, p=...) at ./ui/pageview.cpp:4032
#3  0x7fffdab5f93a in PageView::updateCursor (this=0x574dcd50) at
./ui/pageview.cpp:3997
#4  0x7fffdab51d1b in PageViewAnnotator::slotToolSelected
(this=0x57a6f020, toolID=-1) at ./ui/pageviewannotator.cpp:981
#5  0x747fc9ff in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fffdab7b6ba in PageViewToolBar::toolSelected (_t1=,
this=0x57aa3b10) at
./obj-x86_64-linux-gnu/okularpart_autogen/include/moc_pageviewutils.cpp:340
#7  ToolBarPrivate::selectButton (this=0x57ad22c0,
button=button@entry=0x57a93180) at ./ui/pageviewutils.cpp:927
#8  0x7fffdab7b9d6 in ToolBarPrivate::selectButton (button=0x57a93180,
this=) at ./ui/pageviewutils.cpp:610
#9  PageViewToolBar::selectButton (this=0x57aa3b10, id=id@entry=-1) at
./ui/pageviewutils.cpp:610
#10 0x7fffdab533af in PageViewAnnotator::detachAnnotation
(this=0x57a6f020) at ./ui/pageviewannotator.cpp:1077
#11 PageViewAnnotator::performRouteMouseOrTabletEvent
(this=this@entry=0x57a6f020, eventType=@0x7fffca80:
AnnotatorEngine::Release, button=@0x7fffca84: AnnotatorEngine::Left,
pos=..., 
item=item@entry=0x57b335b0) at ./ui/pageviewannotator.cpp:867
#12 0x7fffdab53430 in PageViewAnnotator::routeMouseEvent
(this=0x57a6f020, e=e@entry=0x7fffd1f0, item=0x57b335b0) at
./ui/pageviewannotator.cpp:881
#13 0x7fffdab72449 in PageView::mouseReleaseEvent (this=0x574dcd50,
e=0x7fffd1f0) at ./ui/pageview.cpp:2443
#14 0x75812dc8 in QWidget::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x758f22de in QFrame::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x7fffdab74f24 in PageView::viewportEvent (this=0x574dcd50,
e=0x7fffd1f0) at ./ui/pageview.cpp:3323
#17 0x747cdacc in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x757d2445 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x757da28f in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x747cdde8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x757d9262 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#22 0x7582d94b in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#23 0x7582ffba in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#24 0x757d246c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#25 0x757d9d34 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#26 0x747cdde8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x75016f43 in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#28 0x75018a25 in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#29 0x74ff0cab in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#30 0x7fffe7fb65a0 in ?? () from

[frameworks-kdelibs4support] [Bug 380973] KDE Calculates Hijri Calendar Incorrectly

[Branimir Amidzic]

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

Branimir Amidzic  changed:

   What|Removed |Added

 CC||m...@ambraspace.com

--- Comment #1 from Branimir Amidzic  ---
I confirm that this is present in recent Plasma version (5.10.5).
Looking at
https://cgit.kde.org/kholidays.git/tree/holidays/plan2/holiday_ba-srp_sr@ijekavianlatin
the "Kurban-bajram" is correctly set, but the system calculates the date to be
23-24.12.2017. while it should be 1.9.2017.

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

[digikam] [Bug 277502] All versions of version set always displayed in Album view

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||clif-li...@jones-clan.com

--- Comment #19 from Maik Qualmann  ---
*** Bug 388227 has been marked as a duplicate of this bug. ***

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

[digikam] [Bug 388227] Image version always shown

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||metzping...@gmail.com
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Maik Qualmann  ---


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

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

[digikam] [Bug 388227] New: Image version always shown

[Clif]

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

Bug ID: 388227
   Summary: Image version always shown
   Product: digikam
   Version: 5.7.0
  Platform: Other
OS: OS X
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Versioning
  Assignee: digikam-bugs-n...@kde.org
  Reporter: clif-li...@jones-clan.com
  Target Milestone: ---

Created 2 edit versions of a JPEG file.  Marked _v1 to 'Show item permanently'.
Later, marked _v1 to 'Hide item permanently' but now _v1 always shows no matter
what the Show/Hide status.  I am able to mark _v2 as show/hide and it works
properly by displaying/not-displaying on the album view.

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

[digikam] [Bug 388221] almost impossible to change location of an image

[Uwe Stöhr]

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

--- Comment #6 from Uwe Stöhr  ---
Hello Maik,

I forgot to thank you for your support. Thanks to your help I think I will be
ready for tomorrows Christmas presentation with located images.

Nevertheless as I reported my bugs as newbie I guess other user will have the
same beginner problems as I had so therefore you and the digiKam team should
discuss if my proposals/bug reports could lead to a more intuitive workflow.

many thanks and best regards
Uwe

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

[dolphin] [Bug 388226] New: desktop filenames canvas bug after login from suspend

[tester]

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

Bug ID: 388226
   Summary: desktop filenames canvas bug after login from suspend
   Product: dolphin
   Version: 17.04.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: view-engine: icons mode
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: yomima...@crymail2.com
  Target Milestone: ---

Created attachment 109523
  --> https://bugs.kde.org/attachment.cgi?id=109523=edit
desktop filenames canvas bug after login from suspend

Only when waking up from suspend file names get noisy.

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

[krita] [Bug 388225] Mouse wheel input setting should show a dropdown menu

[Florrie]

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

--- Comment #2 from Florrie  ---
Quick clarification on this:

> From here, I would click on "Mouse Wheel" and then scroll my wheel in a 
> direction, e.g. up. This would set the value to Mouse Wheel Up (etc). 
> However, on my Linux system, *the scroll wheel is not detected.* Thus, I 
> can't set the setting. [..] It's just that the settings UI doesn't detect my 
> mouse wheel.

On Windows, it does detect the mouse wheel. See the attached screenshot (which
rad_ from freenode #krita captured).

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

[krita] [Bug 388225] Mouse wheel input setting should show a dropdown menu

[Florrie]

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

--- Comment #1 from Florrie  ---
Created attachment 109522
  --> https://bugs.kde.org/attachment.cgi?id=109522=edit
Screenshot posted by rad_ captured - note "Mouse Wheel Up", which rad_ set by
scrolling after clicking the "Mouse Wheel (None)" button I mentioned.

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

[kdeconnect] [Bug 377058] KDE Connect : SD card empty

[Rog131]

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

Rog131  changed:

   What|Removed |Added

 CC||samrog...@hotmail.com

--- Comment #2 from Rog131  ---
A workaround, working at here -
https://forum.kde.org/viewtopic.php?f=22=141037#p384929 :

'The files are not listed because of some bug, but you can go to the SD card in
Dolphin, append to the path smth like '/DCIM' and see what's inside.'

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

[krita] [Bug 388225] New: Mouse wheel input setting should show a dropdown menu

[Florrie]

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

Bug ID: 388225
   Summary: Mouse wheel input setting should show a dropdown menu
   Product: krita
   Version: 3.2.1
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: towerof...@gmail.com
  Target Milestone: ---

Steps to reproduce shows the problem clearly:

1. Open Canvas Input Settings (settings -> configure krita... -> canvas input
settings).
2. Open one of the sections, e.g. Pan Canvas.
3. Click on "Add shortcut..." at the bottom of the table
4. Set the Type to Mouse Wheel.
5. Double click on the Input cell ("None" by default) to show the
input/modifier settings.

>From here, I would click on "Mouse Wheel" and then scroll my wheel in a
direction, e.g. up. This would set the value to Mouse Wheel Up (etc). However,
on my Linux system, *the scroll wheel is not detected.* Thus, I can't set the
setting.

I should note that the scroll wheel *does* work correctly within the actual
paint UI - I can zoom in/out with the scroll wheel just fine (there's a setting
"Zoom Canvas" -> "Mouse Wheel Down: Zoom Out"). It's just that the settings UI
doesn't detect my mouse wheel.

I propose that, rather than that setting require the user to scroll their mouse
wheel (which, of course, needs it to be detectable through the UI - which
evidently isn't always the case), there should be a dropdown menu with the
possible options in it ("Mouse Wheel Down", "Mouse Wheel Up").

Another case of this being a particularly bad problem would be if I
accidentally removed the binding for zooming in/out - then I'd never be able to
use the mouse to zoom, because the setting would be gone and I'd not be able to
restore it! (I could restore all defaults, but then any other settings I'd made
would be gone.)

(This obviously should also be extended to the other options, like "Mouse
Button", but just implementing it for "Mouse Wheel" would fix this particular
case.)

[This is my first bug/feature report here, so, sorry if I've forgotten to
provide any other useful information. For what it's relevant, I'm running Krita
on Debian testing, using Gnome Xorg (not wayland).)

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

[krita] [Bug 387997] Zooming results in "Edit guides" history entry

[Storm Engineer]

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

--- Comment #2 from Storm Engineer  ---
Some other actions also cause the Edit Guides event, such as transforming.

Since these events create a new history entry it makes Undo-ing very dangerous
because this can destroy the steps preventing Redo.

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

[digikam] [Bug 388221] almost impossible to change location of an image

[Uwe Stöhr]

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

--- Comment #5 from Uwe Stöhr  ---
> > - As moving in the map doesn't work, how else can I change an existing
> > location without entering new coordinates manually?
> 
> Drag the image from the list to the new position in the map.

Ehm, so I have to drag in the image again to the map to another location?
Heureka, this works. But this is very unintuitive. I spent now an hour and
never came to to the idea to drag the image in there again because the image is
already in the map, just at the wrong location.

The most intuitive way would be to move the image within the map to the correct
location.

> you do not want to see the context menu if we put everything in there.

It is not about everything, it is that there is NO context menu at all. I mean
what do I want to do when I right-click on an image within a map? Ask persons
around you, I bet they all say "to change the image location or to get info
about the current location".

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

[kwin] [Bug 388224] New: KWin Crash Tabbing from Discord to Chromium

[Kyle Brown]

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

Bug ID: 388224
   Summary: KWin Crash Tabbing from Discord to Chromium
   Product: kwin
   Version: 5.11.4
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: crashbox...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.11.4)
 (Compiled from sources)
Qt Version: 5.9.3
Frameworks Version: 5.41.0
Operating System: Linux 4.14.3 x86_64
Distribution (Platform): Gentoo Packages

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

Simply tabbing from Discord over to Chromium causes KWin to crash and relaunch
then with desktop effects disabled.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f2388414180 (LWP 10745))]

Thread 17 (Thread 0x7f2335690700 (LWP 14174)):
#0  0x7f238fec0956 in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7f236cf9a2eb in util_queue_thread_func () from
/usr/lib64/dri/radeonsi_dri.so
#2  0x7f236cf9a1f7 in impl_thrd_routine () from
/usr/lib64/dri/radeonsi_dri.so
#3  0x7f238feb992a in start_thread () from /lib64/libpthread.so.0
#4  0x7f23945346ff in clone () from /lib64/libc.so.6

Thread 16 (Thread 0x7f237d9c1700 (LWP 12841)):
#0  0x7f238fec0956 in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7f236cf9a2eb in util_queue_thread_func () from
/usr/lib64/dri/radeonsi_dri.so
#2  0x7f236cf9a1f7 in impl_thrd_routine () from
/usr/lib64/dri/radeonsi_dri.so
#3  0x7f238feb992a in start_thread () from /lib64/libpthread.so.0
#4  0x7f23945346ff in clone () from /lib64/libc.so.6

Thread 15 (Thread 0x7f233d7ec700 (LWP 10768)):
#0  0x7f238fec0956 in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7f236cf9a2eb in util_queue_thread_func () from
/usr/lib64/dri/radeonsi_dri.so
#2  0x7f236cf9a1f7 in impl_thrd_routine () from
/usr/lib64/dri/radeonsi_dri.so
#3  0x7f238feb992a in start_thread () from /lib64/libpthread.so.0
#4  0x7f23945346ff in clone () from /lib64/libc.so.6

Thread 14 (Thread 0x7f233e3fd700 (LWP 10766)):
#0  0x7f238fec0956 in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7f23917a2a74 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from
/usr/lib64/libQt5Script.so.5
#2  0x7f23917a2ab9 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*)
() from /usr/lib64/libQt5Script.so.5
#3  0x7f238feb992a in start_thread () from /lib64/libpthread.so.0
#4  0x7f23945346ff in clone () from /lib64/libc.so.6

Thread 13 (Thread 0x7f233f7fe700 (LWP 10765)):
#0  0x7f2394528ecb in ppoll () from /lib64/libc.so.6
#1  0x7f2392683d61 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() from /usr/lib64/libQt5Core.so.5
#2  0x7f2392685016 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#3  0x7f239263621a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#4  0x7f2392492eb3 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#5  0x7f238f0938d5 in QQmlThreadPrivate::run() () from
/usr/lib64/libQt5Qml.so.5
#6  0x7f23924973d1 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#7  0x7f238feb992a in start_thread () from /lib64/libpthread.so.0
#8  0x7f23945346ff in clone () from /lib64/libc.so.6

Thread 12 (Thread 0x7f233700 (LWP 10764)):
#0  0x7f238fec0956 in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7f236cf9a2eb in util_queue_thread_func () from
/usr/lib64/dri/radeonsi_dri.so
#2  0x7f236cf9a1f7 in impl_thrd_routine () from
/usr/lib64/dri/radeonsi_dri.so
#3  0x7f238feb992a in start_thread () from /lib64/libpthread.so.0
#4  0x7f23945346ff in clone () from /lib64/libc.so.6

Thread 11 (Thread 0x7f23613c1700 (LWP 10762)):
#0  0x7f238fec0956 in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7f236cf9a2eb in util_queue_thread_func () from
/usr/lib64/dri/radeonsi_dri.so
#2  0x7f236cf9a1f7 in impl_thrd_routine () from
/usr/lib64/dri/radeonsi_dri.so
#3  0x7f238feb992a in start_thread () from /lib64/libpthread.so.0
#4  0x7f23945346ff in clone () from /lib64/libc.so.6

Thread 10 (Thread 0x7f2361bc2700 (LWP 10761)):
#0  0x7f238fec0956 in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7f236cf9a2eb in util_queue_thread_func () from
/usr/lib64/dri/radeonsi_dri.so
#2  0x7f236cf9a1f7 in impl_thrd_routine () from
/usr/lib64/dri/radeonsi_dri.so
#3  0x7f238feb992a in start_thread () from /lib64/libpthread.so.0
#4  0x7f23945346ff in clone () from /lib64/libc.so.6

Thread 9 (Thread 0x7f23623c3700 (LWP 10760)):
#0  0x7f238fec0956 in pthread_cond_wait () from 

[plasmashell] [Bug 388223] New: Plasma crash while hovering cursor

[Jaak Ristioja]

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

Bug ID: 388223
   Summary: Plasma crash while hovering cursor
   Product: plasmashell
   Version: 5.11.4
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: j...@ristioja.ee
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.11.4)
 (Compiled from sources)
Qt Version: 5.9.3
Frameworks Version: 5.41.0
Operating System: Linux 4.14.7-gentoo x86_64
Distribution: "NAME=Gentoo"

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

Afaict nothing special. I didn't interact directly with any Plasma components,
perhaps if only hovered over something with my cursor.

- Unusual behavior I noticed:

A Plasma panel at the bottom of my screen disappeared, then re-appeared with
some sliding effect.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fbf54588c40 (LWP 3066))]

Thread 7 (Thread 0x7fbf1f4aa700 (LWP 3187)):
#0  0x7fbf4a075691 in g_main_context_query
(context=context@entry=0x7fbf10003400, max_priority=2147483647,
timeout=timeout@entry=0x7fbf1f4a9c44, fds=fds@entry=0x7fbf10003f00,
n_fds=n_fds@entry=1) at
/var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3659
#1  0x7fbf4a075e1f in g_main_context_iterate
(context=context@entry=0x7fbf10003400, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3911
#2  0x7fbf4a07600b in g_main_context_iteration (context=0x7fbf10003400,
may_block=may_block@entry=1) at
/var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3990
#3  0x7fbf4f2d617b in QEventDispatcherGlib::processEvents
(this=0x7fbf10018b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fbf4f26c102 in QEventLoop::exec (this=this@entry=0x7fbf1f4a9da0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fbf4f06ef4e in QThread::exec (this=this@entry=0x55899127a6c0) at
thread/qthread.cpp:515
#6  0x7fbf0ab0e2c6 in KCupsConnection::run (this=0x55899127a6c0) at
/var/tmp/portage/kde-apps/print-manager-17.12.0/work/print-manager-17.12.0/libkcups/KCupsConnection.cpp:305
#7  0x7fbf4f076071 in QThreadPrivate::start (arg=0x55899127a6c0) at
thread/qthread_unix.cpp:368
#8  0x7fbf4de00ac6 in start_thread (arg=0x7fbf1f4aa700) at
pthread_create.c:465
#9  0x7fbf4e8be55f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7fbf204ab700 (LWP 3181)):
#0  0x7fbf4e8ad549 in __GI___libc_read (fd=16,
buf=buf@entry=0x7fbf204aab30, nbytes=nbytes@entry=16) at
../sysdeps/unix/sysv/linux/read.c:26
#1  0x7fbf4a0c9e50 in read (__nbytes=16, __buf=0x7fbf204aab30,
__fd=) at /usr/include/bits/unistd.h:44
#2  g_wakeup_acknowledge (wakeup=0x7fbf24003dc0) at
/var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gwakeup.c:210
#3  0x7fbf4a07595e in g_main_context_check
(context=context@entry=0x7fbf18022240, max_priority=2147483647,
fds=fds@entry=0x7fbf180221c0, n_fds=n_fds@entry=1) at
/var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3707
#4  0x7fbf4a075e48 in g_main_context_iterate
(context=context@entry=0x7fbf18022240, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3926
#5  0x7fbf4a07600b in g_main_context_iteration (context=0x7fbf18022240,
may_block=may_block@entry=1) at
/var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3990
#6  0x7fbf4f2d617b in QEventDispatcherGlib::processEvents
(this=0x7fbf1800d150, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#7  0x7fbf4f26c102 in QEventLoop::exec (this=this@entry=0x7fbf204aad70,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#8  0x7fbf4f06ef4e in QThread::exec (this=this@entry=0x55898ed87b90) at
thread/qthread.cpp:515
#9  0x7fbf522b1045 in QQuickPixmapReader::run (this=0x55898ed87b90) at
util/qquickpixmapcache.cpp:868
#10 0x7fbf4f076071 in QThreadPrivate::start (arg=0x55898ed87b90) at
thread/qthread_unix.cpp:368
#11 0x7fbf4de00ac6 in start_thread (arg=0x7fbf204ab700) at
pthread_create.c:465
#12 0x7fbf4e8be55f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7fbf363a1700 (LWP 3159)):
#0  0x7fbf4e8b1f84 in __GI___poll (fds=0x7fbf24002de0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fbf4a075ea4 in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7fbf24002de0, timeout=, context=0x7fbf24000be0) at
/var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:4228
#2  

[digikam] [Bug 388221] almost impossible to change location of an image

[Maik Qualmann]

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

--- Comment #4 from Maik Qualmann  ---
> - all programs I know offer a context menu. So why can't I just select an
> image in the mag and right-click on it to open the geolocation editor?

DigiKam has so many features, you do not want to see the context menu if we put
everything in there.

> - As moving in the map doesn't work, how else can I change an existing
> location without entering new coordinates manually?

Drag the image from the list to the new position in the map.

Screencast is in progress...

Maik

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

[digikam] [Bug 388222] high RAM memory consumption of digiKam

[Uwe Stöhr]

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

--- Comment #4 from Uwe Stöhr  ---
> it has much more features

I understand this. I was only wondering that digiKam uses so much more RAM
despite I did nothing else than opening it. I did not start any map, I even
didn't select an image or edited one. Therefore I assumed that there is room
for improvements.

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

[digikam] [Bug 388219] setting location for images has inconvenient workflow

[Uwe Stöhr]

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

--- Comment #2 from Uwe Stöhr  ---
> Now you open the geolocation editor. Here you have an image list below the 
> map. Here you can now select individual or all images and drag into the map. 
> So you
> can also assign the coordinates to 100 images at once.

I understood but this issue is about workflow. In all programs I use
(LibreOffice, Inkscape etc.) one can right-click on an element to change its
properties. in digikam I cannot right-click on an image to set or to change its
location. Therefore my proposal in the initial comment of this bug would in my
opinion improve the workflow a lot.

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

[digikam] [Bug 388221] almost impossible to change location of an image

[Uwe Stöhr]

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

--- Comment #3 from Uwe Stöhr  ---
> For editing is the geolocation editor.

I understood that. I am an Open-Source developer too and think I am not too
untalented. But I don't get it:

- all programs I know offer a context menu. So why can't I just select an image
in the mag and right-click on it to open the geolocation editor?

> Here you can now select individual or all images and drag into the map.

That is my second point:

- I once dragged an image into the map
- now I realize that its location is not correct
- therefore I want to move the image inside the map of the geolocation editor
- why is this impossible?
- As moving in the map doesn't work, how else can I change an existing location
without entering new coordinates manually?

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

[digikam] [Bug 388222] high RAM memory consumption of digiKam

[Simon]

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

Simon  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||freisi...@gmail.com
 Resolution|--- |INVALID

--- Comment #3 from Simon  ---
Digikam is not a file browser but a photo management suite, meaning it has much
more features and tracks much more information about items (photos, ...) than
the native file manager. You are comparing apples with oranges here...

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

[digikam] [Bug 388221] almost impossible to change location of an image

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #2 from Maik Qualmann  ---
This map only shows an overview of the images with geolocation positions. I
think I have to create a screencast for you. For editing is the geolocation
editor. Either by Ctrl+Shift+G or in the "Items" menu. Auf Deutsch unter
"Eintrag". You can also select multiple images in the Album View. Now you open
the geolocation editor. Here you have an image list below the map. Here you can
now select individual or all images and drag into the map. So you can also
assign the coordinates to 100 images at once.

Maik

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

[digikam] [Bug 388219] setting location for images has inconvenient workflow

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
This map only shows an overview of the images with geolocation positions. I
think I have to create a screencast for you. For editing is the geolocation
editor. Either by Ctrl+Shift+G or in the "Items" menu. Auf Deutsch unter
"Eintrag". You can also select multiple images in the Album View. Now you open
the geolocation editor. Here you have an image list below the map. Here you can
now select individual or all images and drag into the map. So you can also
assign the coordinates to 100 images at once.

Maik

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

[digikam] [Bug 388222] high RAM memory consumption of digiKam

[Uwe Stöhr]

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

--- Comment #2 from Uwe Stöhr  ---
Created attachment 109521
  --> https://bugs.kde.org/attachment.cgi?id=109521=edit
digiKam preview of the same folder as album

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

[digikam] [Bug 388222] high RAM memory consumption of digiKam

[Uwe Stöhr]

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

--- Comment #1 from Uwe Stöhr  ---
Created attachment 109520
  --> https://bugs.kde.org/attachment.cgi?id=109520=edit
explorer view of the same folder as small thumbnails

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

[digikam] [Bug 388222] New: high RAM memory consumption of digiKam

[Uwe Stöhr]

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

Bug ID: 388222
   Summary: high RAM memory consumption of digiKam
   Product: digikam
   Version: 5.8.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: uwesto...@web.de
  Target Milestone: ---

Created attachment 109519
  --> https://bugs.kde.org/attachment.cgi?id=109519=edit
RAM comparison

- open a folder in the Windows explorer and show it with small thumbnails
- now start digiKam and open the same folder as image preview
- now compare the RAM usage

result: while the Win explorer needs only 33 MB RAM for the image preview,
digiKam needs more than 100 MB more, see the attached screenshots.

This is quite a lot for the same action.

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

[kdeconnect] [Bug 377058] KDE Connect : SD card empty

[Andreas Kilgus]

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

Andreas Kilgus  changed:

   What|Removed |Added

 CC||k...@fuenfsieben.de

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

[digikam] [Bug 388221] almost impossible to change location of an image

[Uwe Stöhr]

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

--- Comment #1 from Uwe Stöhr  ---
Created attachment 109518
  --> https://bugs.kde.org/attachment.cgi?id=109518=edit
screenshot of image in map

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

[digikam] [Bug 388221] almost impossible to change location of an image

[Uwe Stöhr]

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

Uwe Stöhr  changed:

   What|Removed |Added

  Component|general |Geolocation

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

[digikam] [Bug 388221] New: almost impossible to change location of an image

[Uwe Stöhr]

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

Bug ID: 388221
   Summary: almost impossible to change location of an image
   Product: digikam
   Version: 5.8.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: uwesto...@web.de
  Target Milestone: ---

- open a map in the middle
- select an image that is shown in the map, see the attached screenshot
- now I want to change its location

result: one cannot move the image in the map

- OK, then let's use the geolocation editor, thus right-click on the image to
open the context menu to choose from actions

result: there is no context menu at all to open e.g. the editor

- OK, then use the right sidebar and open the geolocation editor from there

result: it is not opened so that I can directly change the location of the
image I want. I see there some previous edited images but not the one I
selected as preselection.

- OK, I can select the image I want in the geolocation editor.
- as i want to correct the location I try to drag the image within in the map

result: this is not possible

Am I too untalented to change the location of an image?

The only way I find is to enter new coordinates manually that I copied from the
OSM URL of the desired location.

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

[konsole] [Bug 387375] konsole -p Command= with spaces uses only the first word

[Kurt Hindenburg]

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

Kurt Hindenburg  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[digikam] [Bug 388199] no context menu to copy coordinates from map

[Uwe Stöhr]

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

--- Comment #9 from Uwe Stöhr  ---
> But we talk about Drag & Drop via the Geolocation Editor
> (Ctrl+Shift+G).

But how can I do this in a convenient way? I created now a separate bug report
because I am still stuck:
bug 388219

So the main question is how I can drag an image from the album view into a map
to set its location. If I open the geolocation editor I cannot do this because
I cannot see anymore the album to drag images from the album to the map of the
editor.

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

[konqueror] [Bug 388220] Konqueror crashes after setting a web shortcut locally that has a system (shared) equivilant

[Linux User #330250]

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

--- Comment #1 from Linux User #330250  ---
(In reply to Linux User #330250 from comment #0)
> Now when I additionally create a new entry for English to German, say like
> this:
> 4. Name="",
> URL="https://www.linguee.de/englisch-deutsch/
> search?source=englisch=\{@}.html", Shortcut="en2de, le2d"

  
Name="Linguee Wörterbuch: Englisch-Deutsch"


Sorry, copy error, I had forgotten to fill in the missing text here...

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

[konqueror] [Bug 388220] New: Konqueror crashes after setting a web shortcut locally that has a system (shared) equivilant

[Linux User #330250]

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

Bug ID: 388220
   Summary: Konqueror crashes after setting a web shortcut locally
that has a system (shared) equivilant
   Product: konqueror
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konq-b...@kde.org
  Reporter: andreas.thalham...@linux.com
  Target Milestone: ---

In short: Konqueror crashes when creating a new Web Shortcut of the same
filename (wich is automatically chosen) as a previous one, but with different
Name, different URL and different Shortcut.

STEPS:
I choose "Settings - Configure Konqueror" and then "Web Browsing - Web
Shortcuts" and I rename a shortcut, say:

1. Name="dict.cc Translation: English to German", Shortcut="en2de" -->
Shortcut="dictccen2de,dcen2de"
2. Name="dict.cc Translation: German to English", Shortcut="de2en" -->
Shortcut="dictccde2en,dcde2en"

and then I create a new entry, say Linguee as follows:
1. Name="Linguee Wörterbuch: Deutsch-Englisch",
URL="https://www.linguee.de/deutsch-englisch/uebersetzung/\{@}.html;,
Shortcut="linguee,de2en,ld2e"


This will create the following files in
~/.kde/share/kde4/services/searchproviders:
1. en2de.desktop (DictCC, local modification)
2. de2en.desktop (DictCC, local modification)
and the new one:
3. linguee.desktop (newly created Linguee translation de2en)


Now when I additionally create a new entry for English to German, say like
this:
4. Name="",
URL="https://www.linguee.de/englisch-deutsch/search?source=englisch=\{@}.html;,
Shortcut="en2de, le2d"

then Konqueror will crash with the subwindows "Configure - Konqueror" and "New
Web Shortcut" remaining open but not responsive.

All Konqueror windows of the same process are unresponsive with it. Separate
processes continue to work.


POSSIBLE REASON:
The reason seems to be that it tries to create another file with the name
linguee.desktop in ~/.kde/share/kde4/services/searchproviders.

I got around this crash by renaming some files there, i.e. I now have only one
dictcc.desktop file (as en2de.desktop and de2en.desktop share the same
URL="http://www.dict.cc/?s=\{@}; anyway) as well as manually renaming
linguee.desktop to de2en.desktop and creating the other one en2de.desktop
manually using the former one as a template. This got around the crash.

(I first used the filenames "linguee_en2de.desktop" and
"linguee_de2en.desktop", but then I also got the system en2de.desktop and
en2de.desktop entries from dictcc again, which I again had to rename the
shortcut for, otherwise there would have been doubles for "en2de" and "de2en".
Using the same filenames fixes this from the start.)


Reproducible: always, following the STEPS mentioned above (top of posting).

This should be fixed so that Konqueror doesn't crash anymore.

Version of Konqueror: 4.14.25, KDE Development Platform 4.14.36, Debian testing
(konqueror/testing,now 4:16.08.3-1 amd64).

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

[plasmashell] [Bug 388143] Favorites and History disappear in launcher when I restart plasmashell

[bugzilla_noreply]

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

mfairu...@gmail.com changed:

   What|Removed |Added

 CC||mfairu...@gmail.com

--- Comment #2 from mfairu...@gmail.com ---
I got this bug too on my PC running manjaro with the latest updates.

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

[konsole] [Bug 388055] Last command gets carried over when in bottom line

[Kurt Hindenburg]

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

--- Comment #1 from Kurt Hindenburg  ---
The version you have is somewhat old - couldn't reproduce here - what shell do
you use? You have konsole maximized and not full screen?

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

[digikam] [Bug 388219] New: setting location for images has inconvenient workflow

[Uwe Stöhr]

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

Bug ID: 388219
   Summary: setting location for images has inconvenient workflow
   Product: digikam
   Version: 5.8.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Geolocation
  Assignee: digikam-bugs-n...@kde.org
  Reporter: uwesto...@web.de
  Target Milestone: ---

I want to set the location of images. Therefore I open a folder in the album
view.

Now I right-click on an image.

result: the context menu doesn't provide to set the location

OK, now I try to get the location by dragging it on a map. Therefore I open a
map on the left side but then the album view gets empty, see bug 388199.

>From the manual I know that the map on the right side cannot be used to change
parameters.

After fiddling around for about an hour I found out that I

1. have to select the image
2. need to open the Extras menu on the right side
3. choose on the right side the geolocation editor
4. now in this editor I can drag the image to the map
5. to tag the next image I have to close the geolocation editor because
otherwise I cannot select another image from the album view
6. select the other image
7. open the geolocation editor again and drag the image there to the map

I guess I do something wrong but as newbie with the manual as help I cannot
find abetter solution. If what I do is the normal workflow it should be
improved:

1. right-click on the image
2. choose there in the context menu an entry "set location"
3. this opens the geolocation editor where one can drag the image to the map
4. one clicks on the album view again and the geolocation editor is pushed
behind (minimized) to be able to see the full album to select another image
5. right-click on the new image and repeat step 2. and 3.

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

[digikam] [Bug 388199] no context menu to copy coordinates from map

[Maik Qualmann]

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

--- Comment #8 from Maik Qualmann  ---
The left sidebar is for finding images with geolocation positions. There you
can create a rectangle over the map and all images within the coordinates will
be displayed. But we talk about Drag & Drop via the Geolocation Editor
(Ctrl+Shift+G).

Maik

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

[kactivitymanagerd] [Bug 387979] Plasmashell and latte dock crashes due abnormal behavior of kactivitymanagerd

[Ivan Bordoni]

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

--- Comment #9 from Ivan Bordoni  ---
Created attachment 109517
  --> https://bugs.kde.org/attachment.cgi?id=109517=edit
files corrupted /home/Ivan/.local/share/kactivitymanagerd_corrupted/resources

Here are the corrupt files

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

[digikam] [Bug 388199] no context menu to copy coordinates from map

[Uwe Stöhr]

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

--- Comment #7 from Uwe Stöhr  ---
Created attachment 109516
  --> https://bugs.kde.org/attachment.cgi?id=109516=edit
map is shown but album view is now empty

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

[digikam] [Bug 388199] no context menu to copy coordinates from map

[Uwe Stöhr]

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

--- Comment #6 from Uwe Stöhr  ---
Created attachment 109515
  --> https://bugs.kde.org/attachment.cgi?id=109515=edit
initial album view

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

[digikam] [Bug 388199] no context menu to copy coordinates from map

[Uwe Stöhr]

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

--- Comment #5 from Uwe Stöhr  ---
> The normal way to work with the geolocation editor is to drag & drop the 
> image from the list to the appropriate location on the map. No complicated 
> copying of the coordinates.

Many thanks for your quick reply. I am a newbie and therefore follow the
manual. Maybe I am too untalented but I don't get it to work. What I do is:
1. open the album view
2. select there an image I want to tag, see the attached screenshot
3. now I want to drag it onto the map as you wrote, therefore I open a map on
the left side.

result: the album view is now empty and therefore I cannot drag the image to
the map, see the attached screenshot.

So how is it done correctly step by step? Can this instruction please also
appear in the manual?

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

[systemsettings] [Bug 388218] Desktop scaling is applied twice in Scale Display preview

[Lastique]

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

--- Comment #2 from Lastique  ---
Sorry, ignore my last comment and attached screenshot. It was supposed to be
posted to a different bug.

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

[konsole] [Bug 388217] Konsole height incorrect if desktop scaling is enabled

[Lastique]

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

--- Comment #1 from Lastique  ---
Created attachment 109514
  --> https://bugs.kde.org/attachment.cgi?id=109514=edit
Konsole window with two undrawn lines

Konsole window with two undrawn lines

Here's a screenshot of Konsole with two undrawn horizontal lines (the lines
show bits of desktop background behind Konsole window).

I've also noticed that similar undrawn lines appear under each line of the
console as its contents change. For example, one can start mc (Midnight
Commander) and try navigating filesystem; the corrupted lines will appear as mc
modifies the console contents.

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

[systemsettings] [Bug 388218] Desktop scaling is applied twice in Scale Display preview

[Lastique]

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

--- Comment #1 from Lastique  ---
Created attachment 109513
  --> https://bugs.kde.org/attachment.cgi?id=109513=edit
Konsole window with two undrawn lines

Here's a screenshot of Konsole with two undrawn horizontal lines (the lines
show bits of desktop background behind Konsole window).

I've also noticed that similar undrawn lines appear under each line of the
console as its contents change. For example, one can start mc (Midnight
Commander) and try navigating filesystem; the corrupted lines will appear as mc
modifies the console contents.

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

[systemsettings] [Bug 388218] New: Desktop scaling is applied twice in Scale Display preview

[Lastique]

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

Bug ID: 388218
   Summary: Desktop scaling is applied twice in Scale Display
preview
   Product: systemsettings
   Version: 5.10.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: andy...@mail.ru
  Target Milestone: ---

In System Settings -> Display and Monitor -> Scale Display dialog, the preview
is scaled twice. Apparently, it is first rendered using the current scaling
ratio that is in effect and then the rendered image is scaled using the
selected scaling ratio. For example, if after reboot the scaling ration is 1.7
and you open this dialog, the preview will not show the current sizes of
interface elements but instead scale them up 1.7x again (therefore the preview
would show 1.7 * 1.7 = 2.89x scaling ratio).

The preview should show the actual size of UI elements after setting the
specified scaling ratio.

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

[konsole] [Bug 388217] New: Konsole height incorrect if desktop scaling is enabled

[Lastique]

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

Bug ID: 388217
   Summary: Konsole height incorrect if desktop scaling is enabled
   Product: konsole
   Version: 17.04.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: andy...@mail.ru
  Target Milestone: ---

When desktop scaling ratio is greater than 1 (System Settings -> Display and
Monitor -> Scale Display), the height of the Konsole window becomes incorrect.
For example, if I set scaling ratio to 1.7, the Konsole window opens down for
less than a half of the screen, despite that in Konsole settings the height is
set to 80% of the screen.

I've also noticed that when scaling is enabled, Konsole window is sometimes
incorrectly drawn and misses a line or two in the middle.

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

[plasmashell] [Bug 375053] enabling global menu breaks copy/paste shortcuts in qupzilla

[acidrums4]

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

acidrums4  changed:

   What|Removed |Added

 CC||acidrums4+st...@gmail.com

--- Comment #15 from acidrums4  ---
Though it's been marked resolved, I can still reproduce this, despite using
plasma-workspace-5.11.4, Qupzilla 2.2.3 and Qt 5.9.3 (on a Gentoo amd64 box).

The `KDE_NO_GLOBAL_MENU=1 qupzilla` did worked for me, though.

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

[kdeplasma-addons] [Bug 353819] Notes white Icons for Plasma Breeze Dark

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

--- Comment #4 from Kai Uwe Broulik  ---
*** Bug 388216 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 388216] Buttons of Notes widget are invisible according breeze theme and widget color

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #2 from Kai Uwe Broulik  ---


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

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

[plasmashell] [Bug 388216] Buttons of Notes widget are invisible according breeze theme and widget color

[Dr . Chapatin]

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

--- Comment #1 from Dr. Chapatin  ---
Created attachment 109512
  --> https://bugs.kde.org/attachment.cgi?id=109512=edit
breeze dark + light widget color

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

[plasmashell] [Bug 388216] New: Buttons of Notes widget are invisible according breeze theme and widget color

[Dr . Chapatin]

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

Bug ID: 388216
   Summary: Buttons of Notes widget are invisible according breeze
theme and widget color
   Product: plasmashell
   Version: 5.11.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: bugsefor...@gmx.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 109511
  --> https://bugs.kde.org/attachment.cgi?id=109511=edit
breeze and dark widget color

Buttons of Notes widget are invisible when I use breeze theme + dark widget
color
or breeze dark theme + light widget color. See the demonstrations.

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

[abakus] [Bug 388215] New: I can't make a new layer

[RainDrop]

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

Bug ID: 388215
   Summary: I can't make a new layer
   Product: abakus
   Version: unspecified
  Platform: Other
OS: unspecified
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: k.h...@gmx.de
  Reporter: xxxraindropx...@gmail.com
  Target Milestone: ---

When I try to make a layer in Krita with the insert key or plus icon at the
bottom right, it won't make the new layer. I do have a digital tablet plugged
into my computer and installed but Krita won't cooperate.

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

[okular] [Bug 376692] Search function fails to find phrases split over two lines

[Michael Weghorn]

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

Michael Weghorn  changed:

   What|Removed |Added

 CC||m.wegh...@posteo.de

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

[plasmashell] [Bug 388214] Zombie notifications in plasmashell. There must be way to inspect/debug what is going on...

[David Tonhofer]

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

--- Comment #1 from David Tonhofer  ---
Created attachment 109510
  --> https://bugs.kde.org/attachment.cgi?id=109510=edit
There seems to be no processes corresponding to the notifications

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

[plasmashell] [Bug 388214] New: Zombie notifications in plasmashell. There must be way to inspect/debug what is going on...

[David Tonhofer]

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

Bug ID: 388214
   Summary: Zombie notifications in plasmashell. There must be way
to inspect/debug what is going on...
   Product: plasmashell
   Version: 5.11.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: bugh...@gluino.name
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 109509
  --> https://bugs.kde.org/attachment.cgi?id=109509=edit
Zombie notifications in action

In Fedora 27 KDE, which uses 

plasma-workspace-5.11.3-2.fc27.x86_64

I encounter the following:

I am doing some heavy rearrangement/copying operations in Dolphin, in parallel.

This seems to succeed (how do I into "I'm sure it succeeded?", ah, transactions
and Unix filesystems, a problem since 1969 ;-) 

However, the plasmashell notification widget seems to remain in the "not sure"
state (see attachment). 9 jobs are marked as "in progress" and display the
"Zylon Moving Eye". 

However these notifications never go away. No processes seem to correspond to
thos (see attachment) There is neither a title, nor a log, nor any explanation
about what these are (basically, "zombie notifications", innit?) 

There needs to be a way to debug these. PID number, thread number. What caused
the notification to appear, command line, anything. And indications about what
happens if I press "pause" or "stop".

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