[kdevelop] [Bug 391470] Building UnrealEngine 4.18 with KDevelop

[Sven Brauch]

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

--- Comment #4 from Sven Brauch  ---
Ah, it's also possible that it exits because of an assert. Can you post the
console log?

But also, can you please try KDevelop 5.2.1? The version you use is again quite
a while old ... try the AppImage from kdevelop.org/download.

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

[kde] [Bug 391503] New: konsole crash

[Mina]

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

Bug ID: 391503
   Summary: konsole crash
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: 842m...@gmail.com
  Target Milestone: ---

Application: kdeinit5 (17.12.2)

Qt Version: 5.10.0
Frameworks Version: 5.43.0
Operating System: Linux 4.13.0-36-generic x86_64
Distribution: KDE neon User Edition 5.12

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

getting crash messages right after login (after restart). Although there are
konsole windows still open and working.

-- Backtrace:
Application: Konsole (kdeinit5), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1f5ca3c780 (LWP 2818))]

Thread 2 (Thread 0x7f1f3eb1f700 (LWP 2866)):
#0  0x7f1f5ab0a74d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f1f570ff38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f1f570ff49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f1f5b0bb5cb in QEventDispatcherGlib::processEvents
(this=0x7f1f380008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f1f5b06264a in QEventLoop::exec (this=this@entry=0x7f1f3eb1ee10,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f1f5ae82554 in QThread::exec (this=) at
thread/qthread.cpp:522
#6  0x7f1f514d92c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f1f5ae876eb in QThreadPrivate::start (arg=0x7f1f5174dd60) at
thread/qthread_unix.cpp:376
#8  0x7f1f58f716ba in start_thread (arg=0x7f1f3eb1f700) at
pthread_create.c:333
#9  0x7f1f5ab1641d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f1f5ca3c780 (LWP 2818)):
[KCrash Handler]
#6  0x7f1f5aa44428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7f1f5aa4602a in __GI_abort () at abort.c:89
#8  0x7f1f5aa867ea in __libc_message (do_abort=do_abort@entry=2,
fmt=fmt@entry=0x7f1f5ab9fed8 "*** Error in `%s': %s: 0x%s ***\n") at
../sysdeps/posix/libc_fatal.c:175
#9  0x7f1f5aa8f37a in malloc_printerr (ar_ptr=,
ptr=, str=0x7f1f5ab9ffe8 "double free or corruption (out)",
action=3) at malloc.c:5006
#10 _int_free (av=, p=, have_lock=0) at
malloc.c:3867
#11 0x7f1f5aa9353c in __GI___libc_free (mem=) at
malloc.c:2968
#12 0x7f1f5b08db8c in QMetaCallEvent::~QMetaCallEvent (this=0x7f1f40023cd0,
__in_chrg=) at kernel/qobject.cpp:485
#13 0x7f1f5b08dbe9 in QMetaCallEvent::~QMetaCallEvent (this=0x7f1f40023cd0,
__in_chrg=) at kernel/qobject.cpp:493
#14 0x7f1f5b0676ef in QCoreApplication::removePostedEvents
(receiver=0x1475db0, eventType=eventType@entry=0) at
kernel/qcoreapplication.cpp:1796
#15 0x7f1f5b090c4a in QObjectPrivate::~QObjectPrivate (this=0x1476150,
__in_chrg=) at kernel/qobject.cpp:252
#16 0x7f1f5b090df9 in QObjectPrivate::~QObjectPrivate (this=0x1476150,
__in_chrg=) at kernel/qobject.cpp:263
#17 0x7f1f5b098edc in QScopedPointerDeleter::cleanup
(pointer=) at
../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:60
#18 QScopedPointer::~QScopedPointer (this=0x1475db8, __in_chrg=) at
../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:107
#19 QObject::~QObject (this=, __in_chrg=) at
kernel/qobject.cpp:881
#20 0x7f1f49139489 in QXcbConnection::~QXcbConnection (this=0x1475db0,
__in_chrg=) at qxcbconnection.cpp:678
#21 0x7f1f4913afa6 in qDeleteAll::const_iterator>
(end=..., begin=...) at
../../../../include/QtCore/../../src/corelib/tools/qalgorithms.h:320
#22 qDeleteAll > (c=...) at
../../../../include/QtCore/../../src/corelib/tools/qalgorithms.h:328
#23 QXcbIntegration::~QXcbIntegration (this=0x1446da0, __in_chrg=) at qxcbintegration.cpp:224
#24 0x7f1f4913b0a9 in QXcbIntegration::~QXcbIntegration (this=0x1446da0,
__in_chrg=) at qxcbintegration.cpp:226
#25 0x7f1f5b5f in QGuiApplicationPrivate::~QGuiApplicationPrivate
(this=0x14241d0, __in_chrg=) at kernel/qguiapplication.cpp:1548
#26 0x7f1f594e23e9 in QApplicationPrivate::~QApplicationPrivate
(this=0x14241d0, __in_chrg=) at kernel/qapplication.cpp:189
#27 0x7f1f5b098edc in QScopedPointerDeleter::cleanup
(pointer=) at
../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:60
#28 QScopedPointer::~QScopedPointer (this=0x1432a18, __in_chrg=) at
../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:107
#29 QObject::~QObject (this=, __in_chrg=) at
kernel/qobject.cpp:881
#30 0x7f1f5b066802 in QCoreApplication::~QCoreApplication (this=0x1432a10,
__in_chrg=) at 

[Ruqola] [Bug 391426] Incoming chat request appears in wrong category, text doesn't show

[Laurent Montel]

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

--- Comment #2 from Laurent Montel  ---
Git commit 5c2e77b0b7f968a72533c23732a4a8d8a90b200c by Laurent Montel.
Committed on 07/03/2018 at 07:15.
Pushed by mlaurent into branch 'master'.

Start to fix load room when we never open a specific room

M  +3-4src/model/roommodel.cpp
M  +4-0src/rocketchatbackend.cpp

https://commits.kde.org/ruqola/5c2e77b0b7f968a72533c23732a4a8d8a90b200c

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

[kde] [Bug 391502] New: Dolphin Crashed when emptying the trash

[bugzilla_noreply]

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

Bug ID: 391502
   Summary: Dolphin Crashed when emptying the trash
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: barnabas.jovanov...@gmail.com
  Target Milestone: ---

Application: kdeinit5 (17.12.2)

Qt Version: 5.10.0
Frameworks Version: 5.43.0
Operating System: Linux 4.4.0-116-generic x86_64
Distribution: KDE neon User Edition 5.12

-- Information about the crash:
- What I was doing when the application crashed:
I wanted to delete everything from my Downloads folder. It wasn't possible to
delete everything at once because it said that the trash can was full. so i
emtpied it and deleted the rest. When i tried to empty the trash again Dolphin
crashed.

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

Thread 4 (Thread 0x7f0cab921700 (LWP 11812)):
#0  0x7f0cd20a327d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f0cce7a96f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f0cce765e74 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f0cce766330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f0cce76649c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f0cd26585cb in QEventDispatcherGlib::processEvents
(this=0x7f0ca40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7f0cd25ff64a in QEventLoop::exec (this=this@entry=0x7f0cab920e80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#7  0x7f0cd241f554 in QThread::exec (this=) at
thread/qthread.cpp:522
#8  0x7f0cd24246eb in QThreadPrivate::start (arg=0x2b3b620) at
thread/qthread_unix.cpp:376
#9  0x7f0cd050e6ba in start_thread (arg=0x7f0cab921700) at
pthread_create.c:333
#10 0x7f0cd20b341d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f0cb9c31700 (LWP 11806)):
#0  0x7f0cce73a200 in g_ptr_array_set_size () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f0cce765871 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f0cce7662bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f0cce76649c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f0cd26585cb in QEventDispatcherGlib::processEvents
(this=0x7f0cac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f0cd25ff64a in QEventLoop::exec (this=this@entry=0x7f0cb9c30e50,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f0cd241f554 in QThread::exec (this=) at
thread/qthread.cpp:522
#7  0x7f0cc93c92c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#8  0x7f0cd24246eb in QThreadPrivate::start (arg=0x7f0cc963dd60) at
thread/qthread_unix.cpp:376
#9  0x7f0cd050e6ba in start_thread (arg=0x7f0cb9c31700) at
pthread_create.c:333
#10 0x7f0cd20b341d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f0cbbd74700 (LWP 11805)):
#0  0x7f0cd20a774d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f0cd343bc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f0cd343d8d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f0cbe4dcce9 in QXcbEventReader::run (this=0x255cd80) at
qxcbconnection.cpp:1370
#4  0x7f0cd24246eb in QThreadPrivate::start (arg=0x255cd80) at
thread/qthread_unix.cpp:376
#5  0x7f0cd050e6ba in start_thread (arg=0x7f0cbbd74700) at
pthread_create.c:333
#6  0x7f0cd20b341d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f0cd3fcf740 (LWP 11804)):
[KCrash Handler]
#6  QStringBuilder,
QString>::convertTo (this=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qstringbuilder.h:112
#7  QStringBuilder, QString>::operator
QString (this=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qstringbuilder.h:131
#8  KDirWatchPrivate::inotifyEventReceived (this=0x2aa0450) at
/workspace/build/src/lib/io/kdirwatch.cpp:322
#9  0x7f0cd262e489 in QMetaObject::activate (sender=sender@entry=0x2acec80,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7ffc35a14a60) at kernel/qobject.cpp:3766
#10 0x7f0cd262ed97 in QMetaObject::activate (sender=sender@entry=0x2acec80,
m=m@entry=0x7f0cd2a5dd80 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc35a14a60)
at kernel/qobject.cpp:3628
#11 0x7f0cd263a768 in QSocketNotifier::activated
(this=this@entry=0x2acec80, 

[digikam] [Bug 391497] Digikam crashes when manually stopping database sync

[Maik Qualmann]

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

--- Comment #2 from Maik Qualmann  ---
Not with the AppImage, the Windows bundles are there too.

Maik

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

[digikam] [Bug 391497] Digikam crashes when manually stopping database sync

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
This problem is already fixed. Please try with the digiKam-5.9.0 pre-release
AppImage:

https://files.kde.org/digikam/

Maik

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

[kwin] [Bug 385100] Moving window to another activity

[Dmitry Vakhnin]

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

--- Comment #3 from Dmitry Vakhnin  ---
(In reply to zeta from comment #2)
> (In reply to Dmitry Vakhnin from comment #0)
> > I have 2 activities. When I need to move window from 1 to another, I'm
> > pressing right button and choose "Move To Activity". Now behavior is that
> > window will move to another activity but it just get status "All
> > Activities". Expected behavior is that window will move straightly to
> > another activity.
> 
> I would not consider this a bug, as a window can belong to more than one
> activity, which becomes clearer if you use 3 or more actibvities. Maybe you
> want to vote for this: https://bugs.kde.org/show_bug.cgi?id=271686

No, I don't need shortcuts. You can see normal behaviour for moving windows
between desktops, but between activities I think that's a bug.

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

[valgrind] [Bug 390524] use of 0b prefix for binary constants

[Ivo Raisr]

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

Ivo Raisr  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||iv...@ivosh.net
 Resolution|--- |WONTFIX

--- Comment #3 from Ivo Raisr  ---
Support for binary constants has been around since gcc 4.3.0 (since 2008, 10
years ago). Also clang supports this notation. I don't see any reason why we
need to prefer compatibility with ancient compilers over readability and
maintainability.

I think your case is a singular one; majority of LTS distros have moved off of
such ancient gcc versions long time ago. You can't expect recent version of
Valgrind work with an ancient version of the compiler; neither is the case of
other toolchain components.

There are going to be more and more cases of Valgrind using compiler features
available only to reasonably recent compilers. You could get away for now with
a simple patch, changing the binary constants into hexadecimal ones, for
example. But with the evolution bringing new changes, you could end up with a
huge patchset eventually.

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

[valgrind] [Bug 390524] use of 0b prefix for binary constants

[Ivo Raisr]

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

Ivo Raisr  changed:

   What|Removed |Added

   Assignee|jsew...@acm.org |iv...@ivosh.net

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

[kate] [Bug 391501] New: Integrate Kate Sessions with Activities

[zeta]

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

Bug ID: 391501
   Summary: Integrate Kate Sessions with Activities
   Product: kate
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: sessions
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: franciscodezuvi...@gmail.com
  Target Milestone: ---

Let's say I have an activity called 'Research'
Let's say I have a Kate session called 'Research'

Wouldn't it be nice that if I open a .txt on my 'Research' activity, kate's
Research session get's fired?

I don't know where it should be configured, some guru will probably know better
than me.

I hope something like this happens someday :)

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

[plasmashell] [Bug 391010] Kmail closes by clicking the "Security" tab

[bugzilla_noreply]

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

weidner-...@gmx.de changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[plasmashell] [Bug 391010] Kmail closes by clicking the "Security" tab

[bugzilla_noreply]

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

weidner-...@gmx.de changed:

   What|Removed |Added

 CC||weidner-...@gmx.de

--- Comment #2 from weidner-...@gmx.de ---
I also can confirm this bug.

System:

Open SuSe Leap 42.3 / German localization
akonadi (17.04.2-1.1/17.04.2-1.6 according to Yast)
KDE Frameworks 5.32.0
Qt 5.6.2 (compiled against 5.6.2) (libqt4 4.8.6-16.6, libqt5-* 5.6.2-1.3
according to Yast)
kMail 5.5.2 (17.04.2-3.1 according to Yast)

Installed the Linux Distro from Scratch a few week ago, for some time
everything was fine, and suddenly this bug emerged. Can't remember whether this
was connected to an semi-automated update or not.

Even after several following updates, the bug still exists. No way to get into
security options (in German Menu: Einstellungen/KMail
einrichten.../Sicherheit).

I'm new to bugs.kde.org, so I don't dare to change the "product" info, But I
wonder whether it is correct?

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

[kwin] [Bug 385100] Moving window to another activity

[zeta]

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

zeta  changed:

   What|Removed |Added

 CC||franciscodezuvi...@gmail.co
   ||m

--- Comment #2 from zeta  ---
(In reply to Dmitry Vakhnin from comment #0)
> I have 2 activities. When I need to move window from 1 to another, I'm
> pressing right button and choose "Move To Activity". Now behavior is that
> window will move to another activity but it just get status "All
> Activities". Expected behavior is that window will move straightly to
> another activity.

I would not consider this a bug, as a window can belong to more than one
activity, which becomes clearer if you use 3 or more actibvities. Maybe you
want to vote for this: https://bugs.kde.org/show_bug.cgi?id=271686

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

[kwin] [Bug 348231] Bring window to current activity when selected

[zeta]

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

zeta  changed:

   What|Removed |Added

 CC||franciscodezuvi...@gmail.co
   ||m
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #10 from zeta  ---
I can confirm this as well. Have my votes.

1) Clicking on a systemtray icon to show the main window (e.g. konversation,
skype) switches the activity if the window is currently open on a different
activity

This should be configurable because it may be a correct use case for some users
(eg, if they have an activity for chatting and they want to be switched).
Options should be a: switch activity (current behavior) b: add window to
current activity.


2) Opening a file that is already open in a different activity switches the
activity

Should be configurable as well for the same reason. (I just tried it with
libreoffice and it didnt even switch the activity, so go figure...)

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

[plasmashell] [Bug 391500] New: Permit users to label devices in Hard Disk I/O Monitor Widget

[Zakhar]

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

Bug ID: 391500
   Summary: Permit users to label devices in Hard Disk I/O Monitor
Widget
   Product: plasmashell
   Version: master
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: zakhar.nasi...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Currently there is no way to label active or inactive devices, users with many
devices likely find this appaling, its the nature of KDE to make this
customizable.

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

[kwin] [Bug 391486] Epoxy 1.5 breaks OpenGL compositing

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

  Component|compositing |scene-opengl
Summary|Nvidia 340x drivers - KWin  |Epoxy 1.5  breaks OpenGL
   |Compositor won't use OpenGL |compositing
   |backend |

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

[plasmashell] [Bug 346181] K menu, context menus, system tray popups not displayed (or displayed off-screen) after an external monitor is plugged in

[David Guerrero]

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

David Guerrero  changed:

   What|Removed |Added

 CC||dguerr...@dguerrero.co

--- Comment #15 from David Guerrero  ---
Created attachment 111239
  --> https://bugs.kde.org/attachment.cgi?id=111239=edit
schreenshot showing items in wrong side

I can confirm this bug is still present in plasma 5.12.2

OS: KDE Neon 5.12 user
KDE Plasma version 5.12.2
KDE framework 5.43.0
QT 5.10.0
Kernel 4.13.0-36

I use a TV as a secondary HDMI display (located to the left), and laptop is the
primary screen. all the pop-ups of the plasma panel are shown in the wrong
screen. I started with this problem with the 5.11 update. (wasn't presented by
the time I started used KDE neon in December of 2017, or before, when I was on
latest Kubuntu 16.04).

In the KDE Neon telegram chat, someone pointed that restoring the layout from
the theme will fix the issue, but you will lose any personalization made to the
plasma bar. After further testing, it seems that activating the auto-hide
option will bring back this problem if you log out and log back in (which
sooner or latter you will have to)

I've tried adding new widgets or changing the configuration of the current
ones, and this doesn't seem to activate the bug, so far, I only tried the
auto-hide to activate it.

Also, this seems related to this bug:
https://bugs.kde.org/show_bug.cgi?id=344706

Please let me know which logs can I attach to help and kill this bug.

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

[kgpg] [Bug 391499] New: KGPG crashes on setting trust level for self keypair

[mva]

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

Bug ID: 391499
   Summary: KGPG crashes on setting trust level for self keypair
   Product: kgpg
   Version: 17.12.2
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@opensource.sf-tec.de
  Reporter: k...@mva.name
  Target Milestone: ---

Application: kgpg (17.12.2)
 (Compiled from sources)
Qt Version: 5.9.4
Frameworks Version: 5.43.0
Operating System: Linux 4.15.4 x86_64
Distribution: "Gentoo GNU/Linux"

-- Information about the crash:
- What I was doing when the application crashed:
Set trust level fo own keys to "Absolute". Then it freezed, and then I pressed
"Cancel", that, in turn, caused crash.

The crash can be reproduced every time.

-- Backtrace:
Application: KGpg (kgpg), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0b1acf8880 (LWP 44436))]

Thread 3 (Thread 0x7f0af1727700 (LWP 44525)):
#0  0x7f0b0d77d003 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#1  0x7f0b0d77da3b in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f0b0d77dc1c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f0b15448a7b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f0b153f6baa in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f0b152517fa in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f0b15255c75 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#7  0x7f0b106d292b in start_thread () from /lib64/libpthread.so.0
#8  0x7f0b1495165f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f0afbfff700 (LWP 44488)):
#0  0x7f0b14945c95 in poll () from /lib64/libc.so.6
#1  0x7f0b0d77db09 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f0b0d77dc1c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f0b15448a7b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f0b153f6baa in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f0b152517fa in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f0b15ab8ce5 in QDBusConnectionManager::run() () from
/usr/lib64/libQt5DBus.so.5
#7  0x7f0b15255c75 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#8  0x7f0b106d292b in start_thread () from /lib64/libpthread.so.0
#9  0x7f0b1495165f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f0b1acf8880 (LWP 44436)):
[KCrash Handler]
#6  0x7f0b14884fa0 in raise () from /lib64/libc.so.6
#7  0x7f0b14886af7 in abort () from /lib64/libc.so.6
#8  0x7f0b14ebc035 in __gnu_cxx::__verbose_terminate_handler () at
/var/tmp/portage/sys-devel/gcc-7.3.0/work/gcc-7.3.0/libstdc++-v3/libsupc++/vterminate.cc:95
#9  0x7f0b14eb9c26 in __cxxabiv1::__terminate (handler=) at
/var/tmp/portage/sys-devel/gcc-7.3.0/work/gcc-7.3.0/libstdc++-v3/libsupc++/eh_terminate.cc:47
#10 0x7f0b14eb9c71 in std::terminate () at
/var/tmp/portage/sys-devel/gcc-7.3.0/work/gcc-7.3.0/libstdc++-v3/libsupc++/eh_terminate.cc:57
#11 0x7f0b14ebaa5f in __cxxabiv1::__cxa_pure_virtual () at
/var/tmp/portage/sys-devel/gcc-7.3.0/work/gcc-7.3.0/libstdc++-v3/libsupc++/pure.cc:50
#12 0x559be77eeeb7 in KGpgTransactionPrivate::slotReadReady() ()
#13 0x7f0b15420507 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#14 0x7f0b15420507 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#15 0x559be7843c79 in KLineBufferedProcessPrivate::_k_receivedStdout() ()
#16 0x7f0b15420507 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#17 0x7f0b153845fa in
QProcess::readyReadStandardOutput(QProcess::QPrivateSignal) () from
/usr/lib64/libQt5Core.so.5
#18 0x7f0b153890b1 in
QProcessPrivate::tryReadFromChannel(QProcessPrivate::Channel*) () from
/usr/lib64/libQt5Core.so.5
#19 0x7f0b1538e9f8 in QProcessPrivate::waitForFinished(int) () from
/usr/lib64/libQt5Core.so.5
#20 0x7f0b15384eeb in QProcess::waitForFinished(int) () from
/usr/lib64/libQt5Core.so.5
#21 0x7f0b153855ea in QProcess::~QProcess() () from
/usr/lib64/libQt5Core.so.5
#22 0x559be7840adf in GPGProc::~GPGProc() ()
#23 0x559be77eda45 in KGpgTransactionPrivate::~KGpgTransactionPrivate() ()
#24 0x559be77edad9 in KGpgTransactionPrivate::~KGpgTransactionPrivate() ()
#25 0x559be77e9f71 in KGpgTransaction::~KGpgTransaction() ()
#26 0x559be77f1237 in KGpgChangeTrust::~KGpgChangeTrust() ()
#27 0x7f0b15426ba8 in QObjectPrivate::deleteChildren() () from
/usr/lib64/libQt5Core.so.5
#28 0x7f0b16579b4c in 

[plasmashell] [Bug 391498] Tablet mode for convertibles (laptops with hinge screens)

[Mina]

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

--- Comment #1 from Mina <842m...@gmail.com> ---
My laptop's product model:

15-w107ne

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

[konsole] [Bug 327541] konsole loses keyboard focus, need to use mouse to regain it

[bugzilla_noreply]

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

--- Comment #9 from yves.can...@ens-lyon.fr ---
(In reply to Ahmad Samir from comment #8)
> This might be caused by the "Sticky Keys" accessibility feature
> (systemsettings -> Accessibility -> Modifier Keys.
> 
> Closing as KDE4/konsole is no longer maintained. Feel free to reopen if you
> can still reproduce it with a currently supported konsole version.

It wasn't for this reason.
But the problem is resolved for konsole 17.08.03 and the consequent KDE
packages.

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

[plasmashell] [Bug 391498] New: Tablet mode for convertibles (laptops with hinge screens)

[Mina]

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

Bug ID: 391498
   Summary: Tablet mode for convertibles (laptops with hinge
screens)
   Product: plasmashell
   Version: master
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: 842m...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

My laptop is an HP envy x360 convertible. It's screen can be rotated 360
degrees (so that the back of the screen touches the back of the keyboard and
the laptop becomes very much like a tablet).

The laptop has windows preinstalled. On windows when I rotate the screen 360
degrees, windows detects this and asks to "switch to tablet mode".

In tablet mode:
 - screen is rotated according to orientation*
 - keyboard and touchpad are disabled**
 - an on-screen keyboard pops up for anything that needs a keyboard (the
android way)
 - (not sure of this) a 2-finger click triggers a right-click. This currently
works in google chrome. Try it on chrome with a touch screen.





*(it seems the laptop has a built-in gsensor) (this can be done using `xrandr
-o right` `xrandr -o inverted` `xrandr -o normal`...
**There volume up & down buttons and a "meta" button on the side. Those are
meant to be used in tablet mode. When I disable the entire keyboard those are
disabled too.

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

[krita] [Bug 391023] Can't draw using the touch screen

[Mina]

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

--- Comment #4 from Mina <842m...@gmail.com> ---
wow it's fixed. Now I can draw with the touch screen. I didn't do anything.
Thanks X)

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

[Falkon] [Bug 391370] bundled qtsingleapplication

[Kevin Kofler]

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

--- Comment #16 from Kevin Kofler  ---
So I think I see where the issue is. First, we construct the
QtSingleApplication with the default appId, which calls sysInit() once. Then,
setAppId is called, which calls sysInit(appId) and creates a new socket,
without deleting the old one first.

I would blame the modifications from QupZilla/Falkon adding that setAppId
method. But the bundled version in QupZilla/Falkon has that too, so I don't see
why you are not seeing this bug with that version.

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

[digikam] [Bug 391497] New: Digikam crashes when manually stopping database sync

[IWBR]

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

Bug ID: 391497
   Summary: Digikam crashes when manually stopping database sync
   Product: digikam
   Version: 5.8.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Database-Maintenance
  Assignee: digikam-bugs-n...@kde.org
  Reporter: iwannaber...@gmail.com
  Target Milestone: ---

Digikam (5.8.0 for windows) crashes when manually stopping a database sync (by
clicking the "cancel this operation" button on the bottom right corner). I
update the database from "Tools -> Maintenance -> Sync Metadata and Database ->
>From image metadata to database". I have been able to replicate this error
several times, and it crashes consistently.

An error window with the following message appears:

"digikam.exe has stopped working

A problem caused the program to stop working correctly.  Windows will close the
program and notify you if solution is available."

I tried looking at DebugView, but no messages related to the crash appear.

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

[digikam] [Bug 391497] Digikam crashes when manually stopping database sync

[IWBR]

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

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[elisa] [Bug 391496] New: Crash when spamming the "Configure Elisa" action through hotkeys

[Guillaume Racicot]

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

Bug ID: 391496
   Summary: Crash when spamming the "Configure Elisa" action
through hotkeys
   Product: elisa
   Version: 0.0.81
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: gufi...@gmail.com
  Target Milestone: ---

Application: elisa (0.0.81)

Qt Version: 5.10.1
Frameworks Version: 5.43.0
Operating System: Linux 4.15.6-1-ARCH x86_64
Distribution: "Arch Linux"

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

I pressed a large number of times Ctrl+Shift+, rapidly

- Unusual behavior I noticed:

The configure window don't open for me, so spamming the hotkey was easy

The crash can be reproduced every time.

-- Backtrace:
Application: Elisa (elisa), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9bcc8d1200 (LWP 14977))]

Thread 13 (Thread 0x7f9b6bc2e700 (LWP 15128)):
#0  0x7f9bc17aeee8 in  () at /usr/lib/libglib-2.0.so.0
#1  0x7f9bc17af10e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#2  0x7f9bc8915314 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f9bc88b73db in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f9bc86c67ae in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f9bc9c34379 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7f9bc86cbb4d in  () at /usr/lib/libQt5Core.so.5
#7  0x7f9bc3f5608c in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f9bc7fd3e7f in clone () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7f9b79769700 (LWP 14990)):
#0  0x7f9bc3f5c3bd in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f9bc86cd02c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f9bc6a1041a in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f9bc6a108a4 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f9bc86cbb4d in  () at /usr/lib/libQt5Core.so.5
#5  0x7f9bc3f5608c in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f9bc7fd3e7f in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7f9b7a17c700 (LWP 14989)):
#0  0x7f9bc3f5c6fd in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f9bc86ccee1 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f9bc86c8db1 in  () at /usr/lib/libQt5Core.so.5
#3  0x7f9bc86cbb4d in  () at /usr/lib/libQt5Core.so.5
#4  0x7f9bc3f5608c in start_thread () at /usr/lib/libpthread.so.0
#5  0x7f9bc7fd3e7f in clone () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7f9b7a97d700 (LWP 14988)):
#0  0x7f9bc7fc997b in poll () at /usr/lib/libc.so.6
#1  0x7f9bc17aeff3 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f9bc17af10e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f9bc8915314 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f9bc88b73db in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f9bc86c67ae in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f9bc86cbb4d in  () at /usr/lib/libQt5Core.so.5
#7  0x7f9bc3f5608c in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f9bc7fd3e7f in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7f9b7b17e700 (LWP 14987)):
#0  0x7f9bc17f5b94 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7f9bc17aeb8b in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#2  0x7f9bc17af081 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f9bc17af10e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f9bc8915314 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f9bc88b73db in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f9bc86c67ae in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f9bc86cbb4d in  () at /usr/lib/libQt5Core.so.5
#8  0x7f9bc3f5608c in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f9bc7fd3e7f in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7f9b98f28700 (LWP 14986)):
#0  0x7f9bc17f5b94 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7f9bc17ade7c in g_main_context_acquire () at
/usr/lib/libglib-2.0.so.0
#2  0x7f9bc17aeea7 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f9bc17af10e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f9bc8915314 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f9bc88b73db in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f9bc86c67ae in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f9bc86cbb4d in  () at 

[plasmashell] [Bug 391494] Plasma shell repeatedly crashes

[Jim Lienhart]

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

--- Comment #2 from Jim Lienhart  ---
Thank you

On Tue, Mar 6, 2018 at 8:52 PM, David Edmundson 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=391494
>
> David Edmundson  changed:
>
>What|Removed |Added
> 
> 
>  Resolution|--- |DOWNSTREAM
>  Status|UNCONFIRMED |RESOLVED
>
> --- Comment #1 from David Edmundson  ---
> [KCrash Handler]
> #6  0x7f33bc4f050e in  () at /usr/lib/x86_64-linux-gnu/dri/
> radeonsi_dri.so
>
> Crash is in radeon, we can't do much about that. Please upgrade/downgrade
> your
> driver.
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[elisa] [Bug 391495] Configure menu entry does not open any window

[Guillaume Racicot]

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

Guillaume Racicot  changed:

   What|Removed |Added

   Platform|Other   |Compiled Sources

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

[elisa] [Bug 391495] New: Configure menu entry does not open any window

[Guillaume Racicot]

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

Bug ID: 391495
   Summary: Configure menu entry does not open any window
   Product: elisa
   Version: 0.0.81
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: gufi...@gmail.com
  Target Milestone: ---

Step to reproduce:

 1. Press the hamburger menu
 2. Click on "Configure Elisa"
 3. ...

Actual behavior:

 - No configuration window is open

Expected behavior:

 - A configuration window is opened

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

[plasmashell] [Bug 391494] Plasma shell repeatedly crashes

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from David Edmundson  ---
[KCrash Handler]
#6  0x7f33bc4f050e in  () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so

Crash is in radeon, we can't do much about that. Please upgrade/downgrade your
driver.

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

[plasmashell] [Bug 391494] New: Plasma shell repeatedly crashes

[Jim Lienhart]

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

Bug ID: 391494
   Summary: Plasma shell repeatedly crashes
   Product: plasmashell
   Version: 5.10.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: jimlienh...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.5)

Qt Version: 5.9.1
Frameworks Version: 5.38.0
Operating System: Linux 4.13.0-36-generic x86_64
Distribution: Ubuntu 17.10

-- Information about the crash:
- What I was doing when the application crashed:
Browsing the web,  firefox and konsole running
Happens regularly, maybe once every hour. Desjtop wallpaper is a slideshow.

The crash can be reproduced sometimes.

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

Thread 15 (Thread 0x7f3300aa5700 (LWP 2652)):
#0  0x7f33de4a5951 in __GI___poll (fds=0x7f32f4000b10, nfds=1,
timeout=1593030) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f33d90d8169 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f33d90d827c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f33dede549b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f33ded8ae3a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f33debaa3ca in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f32edfe9717 in KCupsConnection::run() () at
/usr/lib/x86_64-linux-gnu/libkcupslib.so
#7  0x7f33debaf29d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f33ddd457fc in start_thread (arg=0x7f3300aa5700) at
pthread_create.c:465
#9  0x7f33de4b1b5f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 14 (Thread 0x7f331700 (LWP 2614)):
#0  0x7f33d911d5b9 in g_mutex_lock () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f33d90d7b7c in g_main_context_check () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f33d90d8110 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f33d90d827c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f33dede549b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f33ded8ae3a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f33debaa3ca in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f33e28a0846 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x7f33debaf29d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f33ddd457fc in start_thread (arg=0x7f331700) at
pthread_create.c:465
#10 0x7f33de4b1b5f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 13 (Thread 0x7f3301f47700 (LWP 2612)):
#0  0x7f33ddd4c072 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55d0686d95b8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f33ddd4c072 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55d0686d9568, cond=0x55d0686d9590) at pthread_cond_wait.c:502
#2  0x7f33ddd4c072 in __pthread_cond_wait (cond=0x55d0686d9590,
mutex=0x55d0686d9568) at pthread_cond_wait.c:655
#3  0x7f33bc60224b in  () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#4  0x7f33bc602167 in  () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#5  0x7f33ddd457fc in start_thread (arg=0x7f3301f47700) at
pthread_create.c:465
#6  0x7f33de4b1b5f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 12 (Thread 0x7f332cd28700 (LWP 2604)):
#0  0x7f33ddd4c072 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55d068419360) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f33ddd4c072 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55d068419310, cond=0x55d068419338) at pthread_cond_wait.c:502
#2  0x7f33ddd4c072 in __pthread_cond_wait (cond=0x55d068419338,
mutex=0x55d068419310) at pthread_cond_wait.c:655
#3  0x7f33bc60224b in  () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#4  0x7f33bc602167 in  () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#5  0x7f33ddd457fc in start_thread (arg=0x7f332cd28700) at
pthread_create.c:465
#6  0x7f33de4b1b5f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 11 (Thread 0x7f332d529700 (LWP 2603)):
#0  0x7f33ddd4c072 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55d068419364) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f33ddd4c072 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55d068419310, 

[Discover] [Bug 391126] Regression: Discover does not list apps from Flatpak repos

[Aleix Pol]

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

--- Comment #7 from Aleix Pol  ---
So it's listing by display (as it was before my patch) instead of sourceId...

Really weird :/

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

[kde] [Bug 391493] New: falta botones de reproducción en panel clip de texto en kdenlive 17.12 español

[Susana Gómez]

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

Bug ID: 391493
   Summary: falta botones de reproducción en panel clip de texto
en kdenlive 17.12 español
   Product: kde
   Version: unspecified
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: siusa...@gmail.com
  Target Milestone: ---

Created attachment 111237
  --> https://bugs.kde.org/attachment.cgi?id=111237=edit
botones de reproducción en panel clip de texto

S:O: windows 7 x64 español --> kdenlive 17.12 español
¿será posible considerar los siguientes detalles?

1-si quiero animar el texto desde el panel Clip de texto no aparecen los
botones de 
   reproducción, sólo  aparece alineación y, en la sección animación, sólo
aparece Editar 
   Inicio y Final 

2- Eso por un lado, por otro, la aguja de la línea de tiempo se pega, no
avanza, hay que 
moverla con el  puntero del mouse

ÉSte programa lo encuentro genial, ojala funcione con windows 7 x64 como lo
hace con linux... ¡me encanta!

Gracias 

Atte.

Susana

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

[kde] [Bug 391492] New: falta cursor de mouse al escribir texto Clip de título en kdenlive 17.12 y más otros detalles...

[Susana Gómez]

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

Bug ID: 391492
   Summary: falta cursor de mouse al escribir texto Clip de título
en kdenlive 17.12 y más otros detalles...
   Product: kde
   Version: unspecified
  Platform: Other
OS: other
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: siusa...@gmail.com
  Target Milestone: ---

Created attachment 111236
  --> https://bugs.kde.org/attachment.cgi?id=111236=edit
muestra panel Clip de texto con texto sin cursor ni puntero tal como se ve

S.O.: windows 7 x64 --> ¿será posible considerar hacer algún arreglo a los
siguientes detalles?
1-  Kdenlive se realentiza y al agregar texto a través del clip de título, no
aparece el cursor  que muestra donde 
 se va escribiendo y cuando se quiere ir a alguna palabra anterior, es muy
complicado identificar selección...

Veo todas las posibilidades que tiene este programa y sería maravilloso que
funcionara en windows tan bien como lo hace en linux... ¡¡¡Me encanta!!!

Gracias

Atte.

Susana

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

[plasmashell] [Bug 391491] New: Folder view syncronous betwewn screens

[bugzilla_noreply]

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

Bug ID: 391491
   Summary: Folder view syncronous betwewn screens
   Product: plasmashell
   Version: 5.12.2
  Platform: Manjaro
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Desktop Containment
  Assignee: se...@kde.org
  Reporter: mato...@arcor.de
CC: plasma-b...@kde.org
  Target Milestone: 1.0

I have 3 screens and my main desktop area set to "folder-view", with plasma
5.11 when i created a desktop shortcut it was visible on all 3 screens, with
plasma 5.12 i have to create a shortcut for every screen individually.

My feature request is to optionally restore the old pre 5.12 behavior.

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

[konqueror] [Bug 61524] find from cursor -- cursor where? make a visible cursor.

[Susana Gómez]

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

Susana Gómez  changed:

   What|Removed |Added

 CC||siusa...@gmail.com

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

[kate] [Bug 391490] New: add option to right click on a highlighted URL and open it in the default browser

[k3bBug]

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

Bug ID: 391490
   Summary: add option to right click on a highlighted URL and
open it in the default browser
   Product: kate
   Version: 17.04.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: erben...@comcast.net
  Target Milestone: ---

When editing a text file, it would be nice if the user highlights a URL and
right click if there there was an option there to open the URL in the default
browser
e.g suppose the text file contained http://www.google.com
you would highlight the entire URL and then right click on it, on the popup
menu that comes up there should be an option to 'open the url in the default
browser'

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

[dolphin] [Bug 386460] Trashing is slow when trash size is limited

[Huon]

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

Huon  changed:

   What|Removed |Added

 Ever confirmed|0   |1
Version|17.08.2 |17.12.2
 Status|UNCONFIRMED |CONFIRMED

--- Comment #3 from Huon  ---
Confirmed in latest release (17.12.2) and also current master (18.03.70).

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

[dolphin] [Bug 386460] Trashing is slow when trash size is limited

[Huon]

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

Huon  changed:

   What|Removed |Added

 CC||h...@plonq.org

--- Comment #2 from Huon  ---
Oddly I've only just recently (last week or so) noticed trashing being slow -
1-2 seconds trashing small (<1MB) files. Removing the size limit in Dolphin's
settings fixes this making trashing instantaneous.

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

[Akonadi] [Bug 391489] akonadi_baloo_indexer never exits cleanly

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

Product|kde |Akonadi
 Status|UNCONFIRMED |RESOLVED
 CC||chrig...@fastmail.fm,
   ||dvra...@kde.org
Version|unspecified |4.13
 Resolution|--- |DUPLICATE
  Component|general |Indexer

--- Comment #1 from Christoph Feck  ---
Please read bug 385452 comment #7.

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

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

[Akonadi] [Bug 385452] akonadi_baloo_indexer crash

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||hh.kde.cr...@gmail.com

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

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

[systemsettings] [Bug 391389] System Settings / Desktop Effects has list poking out of the window's border

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #2 from Christoph Feck  ---
https://bugreports.qt.io/browse/QTBUG-54888

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

[konsole] [Bug 391445] Font changes doesn't saves in Konsole after rebooting

[Eugene]

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

Eugene  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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

[konsole] [Bug 391445] Font changes doesn't saves in Konsole after rebooting

[Eugene]

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

--- Comment #5 from Eugene  ---
(In reply to Sergio Torres Soldado from comment #4)
> This also happens to me using konsole 17.12.2 libqt* 5.10.1 Archlinux. A
> reboot is not necessary in my case, I just need to launch a new Konsole
> instance.

Yes, you're right. Reboot is not necessary in my case too.

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

[plasmashell] [Bug 391359] System Monitor Plasma Widgets break rendering in Plasma Shell

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from David Edmundson  ---
thanks for reporting back

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

[plasmashell] [Bug 391485] Wallpaper chooser UI not very discoverable; consider making it into a KCM so we can expose it via System Settings

[David Edmundson]

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

--- Comment #3 from David Edmundson  ---
Yeah, I'm of the thought that no-one uses the toolbox. 
But it's there because of designing round the idea that users never right
click. 

>I think some creative UI design could work:

That can at most remove one level:
but it still leaves adding an activity chooser inside the multi-screen thing,
or a monitor chooser inside the activity thing.

(and we're not making system settings contextually aware of only showing the
current activity, because that would be so unlike any other settings page)

Frankly it seems incredibly arbitrary to put some desktop settings in a
completely disjointed place to the desktop. 
I'm not against a discussion, but it needs some better justification than
"others do it".

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

[frameworks-kglobalaccel] [Bug 391488] Global Shortcuts displays shortcuts for apps I don't have installed

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Platform|Other   |Kubuntu Packages

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

[kmail2] [Bug 388790] SMTP does not support OAuth2

[Raúl]

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

Raúl  changed:

   What|Removed |Added

 CC||rasas...@gmail.com

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

[plasmashell] [Bug 391485] Wallpaper chooser UI not very discoverable; consider making it into a KCM so we can expose it via System Settings

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Keywords||usability

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

[kde] [Bug 391489] New: akonadi_baloo_indexer never exits cleanly

[happy]

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

Bug ID: 391489
   Summary: akonadi_baloo_indexer never exits cleanly
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: hh.kde.cr...@gmail.com
  Target Milestone: ---

Application: akonadi_baloo_indexer (4.14)
KDE Platform Version: 4.14.34
Qt Version: 4.8.7
Operating System: Linux 4.15.0-041500rc6-generic x86_64
Distribution: Ubuntu 17.10

-- Information about the crash:
Because of bugs in GMail IMAP handling, restarting Akonadi periodically is
required (...)

The akonadi_baloo_indexer is the only process belonging to akonadi stuff that
_never_ exits cleanly:

org.kde.pim.akonadicontrol: ProcessControl: Application
"/usr/bin/akonadi_baloo_indexer" stopped unexpectedly ( "Process crashed" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_baloo_indexer'
crashed! 1 restarts left.
QProcess: Destroyed while process ("/usr/bin/akonadi_baloo_indexer") is still
running.
org.kde.pim.akonadicontrol: ProcessControl: Application
"/usr/bin/akonadi_baloo_indexer" stopped unexpectedly ( "Process crashed" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_baloo_indexer'
crashed! 0 restarts left.
org.kde.pim.akonadicontrol: Agent instance with identifier
"akonadi_baloo_indexer" does not exist
akonadi_baloo_indexer(12481): "DatabaseLockError" "DatabaseLockError: Unable to
get write lock on /home/dean/.local/share/baloo/email/: already locked" 
akonadi_baloo_indexer(12481): "DatabaseLockError" "DatabaseLockError: Unable to
get write lock on /home/dean/.local/share/baloo/emailContacts/: already locked"

The crash can be reproduced every time.

-- Backtrace:
Application:  (akonadi_baloo_indexer), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x7feb46cd70bb in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:51
#7  0x7feb46cd8f5d in __GI_abort () at abort.c:90
#8  0x7feb4a8a8f15 in qt_message_output(QtMsgType, char const*) () at
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x7feb493ddcc7 in  () at /usr/lib/libakonadi-kde.so.4
#10 0x7feb493dd18a in  () at /usr/lib/libakonadi-kde.so.4
#11 0x7feb4a9ddd11 in QObject::event(QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#12 0x7feb47f3103c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#13 0x7feb47f37f76 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#14 0x7feb48c9004a in KApplication::notify(QObject*, QEvent*) () at
/usr/lib/libkdeui.so.5
#15 0x7feb4a9c38ad in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#16 0x7feb4a9c7366 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#17 0x7feb4a9f409e in  () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#18 0x7feb46396fb7 in g_main_context_dispatch () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x7feb463971f0 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x7feb4639727c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7feb4a9f420e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#22 0x7feb47fde666 in  () at /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#23 0x7feb4a9c212f in
QEventLoop::processEvents(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#24 0x7feb4a9c2495 in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#25 0x7feb4a9c8459 in QCoreApplication::exec() () at
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#26 0x7feb493da43d in Akonadi::AgentBase::init(Akonadi::AgentBase*) () at
/usr/lib/libakonadi-kde.so.4
#27 0x55d5cb5731f3 in  ()
#28 0x7feb46cc11c1 in __libc_start_main (main=0x55d5cb56c3a0, argc=3,
argv=0x7ffe6b46e778, init=, fini=,
rtld_fini=, stack_end=0x7ffe6b46e768) at ../csu/libc-start.c:308
#29 0x55d5cb56c45a in _start ()

Reported using DrKonqi

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

[kopete] [Bug 265440] turn off wireless -> kopete crashes

[Jiri Palecek]

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

Jiri Palecek  changed:

   What|Removed |Added

 CC||jpale...@web.de

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

[kopete] [Bug 216021] Kopete crashes when the network connection is lost [QList::*, DNSSD::ServiceBrowserPrivate::gotRemoveService, ..., OrgFreedesktopAvahiServiceBrowserInterface::ItemRemove]

[Jiri Palecek]

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

Jiri Palecek  changed:

   What|Removed |Added

 CC||jpale...@web.de

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

[kopete] [Bug 301743] kopete crashes on NetworkManager restart

[Jiri Palecek]

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

Jiri Palecek  changed:

   What|Removed |Added

 CC||jpale...@web.de

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

[frameworks-kglobalaccel] [Bug 391488] New: Global Shortcuts displays shortcuts for apps I don't have installed

[Nate Graham]

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

Bug ID: 391488
   Summary: Global Shortcuts displays shortcuts for apps I don't
have installed
   Product: frameworks-kglobalaccel
   Version: 5.43.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: n...@kde.org
  Target Milestone: ---

System Settings > Shortcuts > Global Shortcuts displays the shortcuts for a
variety of KDE programs, many of which the I don't have installed (Amarok, JuK,
KTorrent). These entries are unnecessary and clutter up the list, making it
harder for the user to find things.

We should consider hiding entries for apps that aren't currently installed.

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

[plasmashell] [Bug 391485] Wallpaper chooser UI not very discoverable; consider making it into a KCM so we can expose it via System Settings

[Nate Graham]

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

--- Comment #2 from Nate Graham  ---
Fair enough about the Desktop Toolbox. Of course, I remember seeing a Plasma
developer recently (can't remember who) comment that nobody uses it!


> the first thing people do if they want options is right click everywhere like 
> a nutter.

Computer experts with a mouse, yes. :) Regular people look for a thing with the
word "Settings" in its name.


> It's not a particularly giant leap that the most visibly massive prominent 
> thing on the desktop is part of the desktop.

For you and me, no. But it still doesn't have the word "wallpaper" in it, so a
large fraction of people are going to miss it. Besides, why should they have to
make a mental leap in the first place? If we make it a KCM, we can have a menu
item that says "Change wallpaper" and just open that KCM directly.


> The problem with the KCM is it then becomes super complex.
> You'd need a UI to choose which activity you're configuring
> Then you need a UI to choose which monitor you're changing

I think some creative UI design could work:
- For multi-screen setups, you could show a new window with the KCM on every
screen (this is what macOS does)
- For activities, you could move the wallpaper configuration UI into the
Activities KCM, making it explicit that 


One of our strengths is all this customizability and power, but we shouldn't
let it get in the way of providing a polished user experience for the average
user who has one screen and does not use activities.

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

[kleopatra] [Bug 386518] Decrypt and verify both crash

[rbdj]

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

rbdj  changed:

   What|Removed |Added

 CC||reinbe...@gmail.com

--- Comment #1 from rbdj  ---
Same problem over here. 
Is anybody looking into this?

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

[krita] [Bug 391487] Krita ignores PNG EXIF data

[Danas]

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

--- Comment #1 from Danas  ---
Sample image to test the bug
https://drive.google.com/open?id=1Z7P78WYmJWo9GfsU3MtqoFaM0LXZ2ej3

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

[krita] [Bug 391487] New: Krita ignores PNG EXIF data

[Danas]

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

Bug ID: 391487
   Summary: Krita ignores PNG EXIF data
   Product: krita
   Version: 3.3.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: File formats
  Assignee: krita-bugs-n...@kde.org
  Reporter: danas.a...@gmail.com
  Target Milestone: ---

Hello, 

I just faced with an issue that Krita seems to don;t see exif data in PNG
images, it is fine with TIFF and JPG files, but when it comes to PNG, it looks
like Krita doesn't see Exif data. Checked with Image viewer and GIMP 2.9 and
same file shows Exif as it should, but Krita seems to ignore that there is exif
data. Checked on Krita 3.3.3 and Krita 4 beta. same result. 

OS: Kubuntu 17.10 latest updates.

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

[plasmashell] [Bug 391359] System Monitor Plasma Widgets break rendering in Plasma Shell

[Dan]

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

--- Comment #2 from Dan  ---
OK, so I've located the source of this issue:

An upgraded library libepoxy 1.5.0-1 was the source of the rendering issues.

I downgraded to libepoxy-1.4.3-1 and the widgets now render properly.

I don't think this is a KDE bug.

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

[plasmashell] [Bug 391485] Wallpaper chooser UI not very discoverable; consider making it into a KCM so we can expose it via System Settings

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #1 from David Edmundson  ---
>- It relies on a context menu,

That's not true. 
Burger menu -> configure desktop

>- The user needs to make the mental leap that the wallpaper is part of the 
>desktop

It's not a particularly giant leap that the most visibly massive promintent
thing on the desktop is part of the desktop.

>The first place people go looking for the wallpaper chooser UI is in the 
>System Settings app.

That's a random guess.

>From my anecodatal experience (which admittiedly is my random guess) the first
thing people do if they want options is right click everywhere like a nutter.

>contrary to [..] every other platform.

I'll give you that. Though our goal was never to make a 1-1 clone of anything.



The problem with the KCM is it then becomes super complex.

You'd need a UI to choose which activity you're configuring
Then you need a UI to choose which monitor you're changing

That creates an n*m UI of settings that you don't need when you have implied
context.

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

[plasmashell] [Bug 391485] Wallpaper chooser UI not very discoverable; consider making it into a KCM so we can expose it via System Settings

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

  Component|Folder  |Desktop Containment
   Assignee|h...@kde.org|se...@kde.org

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

[dolphin] [Bug 391378] Dolphin crashed when moving directory via terminal

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

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

--- Comment #1 from Elvis Angelaccio  ---


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

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

[frameworks-kcoreaddons] [Bug 390214] Dolphin random crash

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||warrenh...@gmail.com

--- Comment #10 from Elvis Angelaccio  ---
*** Bug 391378 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 391486] Nvidia 340x drivers - KWin Compositor won't use OpenGL backend

[Dan]

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

--- Comment #4 from Dan  ---
OK, so I did find a thread in the ArchLinux forums:

https://bbs.archlinux.org/viewtopic.php?id=235021

it appears the offending package is libepoxy 1.50-1. Downgrading to a previous
version of libepoxy (1.4.3-1) allows me to use OpenGL as a rendering backend
for Compositing.

I'm not sure if this is a valid bug in this case.

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

[kwin] [Bug 391486] Nvidia 340x drivers - KWin Compositor won't use OpenGL backend

[Dan]

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

--- Comment #3 from Dan  ---
pacman -Q | grep nvidia

lib32-nvidia-340xx-utils 340.106-1
lib32-nvidia-cg-toolkit 3.1-5
nvidia-340xx 340.106-15
nvidia-340xx-utils 340.106-1
nvidia-cg-toolkit 3.1-4

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

[kwin] [Bug 391486] Nvidia 340x drivers - KWin Compositor won't use OpenGL backend

[Dan]

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

--- Comment #2 from Dan  ---
Created attachment 111235
  --> https://bugs.kde.org/attachment.cgi?id=111235=edit
glxinfo

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

[kwin] [Bug 391486] Nvidia 340x drivers - KWin Compositor won't use OpenGL backend

[Dan]

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

Dan  changed:

   What|Removed |Added

 CC||dan.f.k...@gmail.com

--- Comment #1 from Dan  ---
Created attachment 111234
  --> https://bugs.kde.org/attachment.cgi?id=111234=edit
qdbus org.kde.KWin /KWin supportInformation > Kwin-info.txt

Attached supportInformation

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

[kwin] [Bug 391486] New: Nvidia 340x drivers - KWin Compositor won't use OpenGL backend

[Dan]

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

Bug ID: 391486
   Summary: Nvidia 340x drivers - KWin Compositor won't use OpenGL
backend
   Product: kwin
   Version: 5.12.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: dan.f.k...@gmail.com
  Target Milestone: ---

OpenGL 2.0 and OpenGL 3.1 stopped working as the compositor backend after an
update. XRender does work.

When attempting to set the compositor backend in System Settings | Hardware |
Display and Monitor | Compositor, it appears to set correctly (i.e: no errors
are prompted), however



[user@host ~]$ qdbus org.kde.KWin /KWin supportInformation | grep -i compos 
Composite: yes; Version: 0x4
compositingMode: 1
useCompositing: true
compositingInitialized: true
windowsBlockCompositing: true
Compositing
Compositing is active
Compositing Type: XRender



I'm not able to enable certain desktop effects such as Magic Lamp, Wobbly
Windows, etc, so it's obvious XRender is actually in use.

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

[digikam] [Bug 386959] Properties view: wrong creation date [patch]

[bugzilla_noreply]

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

--- Comment #14 from caulier.gil...@gmail.com ---
yes it sound logic.
If the Exif to XMP conversion is suspect, i recommend to report this problem to
Exiv2 team. At least they lust said if we have really a problem here ...

Gilles

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

[plasmashell] [Bug 391485] New: Wallpaper chooser UI not very discoverable; consider making it into a KCM so we can expose it via System Settings

[Nate Graham]

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

Bug ID: 391485
   Summary: Wallpaper chooser UI not very discoverable; consider
making it into a KCM so we can expose it via System
Settings
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Folder
  Assignee: h...@kde.org
  Reporter: n...@kde.org
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Right now, the only way to change the wallpaper is by right-clicking on the
desktop and choosing "Configure Desktop".

This is a rather unintuitive method, because:
- It relies on a context menu, which is an expert UI; most users don't use
context menus, especially on laptops
- The user needs to make the mental leap that the wallpaper is part of the
desktop

The first place people go looking for the wallpaper chooser UI is in the System
Settings app. Sadly, ours doesn't have it there, contrary to user expectations
and consistency with every other platform.

Technically speaking, this is because it's a part of the Folder View widget,
and not a KCM. But perhaps we should break it out into being a KCM so we can
put it in System Settings.

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

[kwin] [Bug 391473] Disabling compositor breaks launch feedback

[bugzilla_noreply]

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

--- Comment #2 from jonb...@gmx.com ---
Disabled.

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

[digikam] [Bug 386959] Properties view: wrong creation date [patch]

[Maik Qualmann]

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

--- Comment #13 from Maik Qualmann  ---
Yes, both entries exist:

Xmp.exif.DateTimeOriginal
Xmp.exif.DateTimeDigitized

But I do not think that this entrys exists in a sidecar file:

Exif.Photo.DateTimeOriginal
Exif.Photo.DateTimeDigitized

The problem is, we begins by looking for the date with the query from the EXIF
name space. Through http://www.exiv2.org/conversion.html we get:

Exif.Photo.DateTimeOriginal ==> Xmp.photoshop.DateCreated
Exif.Photo.DateTimeDigitized ==> Xmp.xmp.CreateDate

I think it would be correct:

Exif.Photo.DateTimeOriginal ==> Xmp.exif.DateTimeOriginal
Exif.Photo.DateTimeDigitized ==> Xmp.exif.DateTimeDigitized

Or am I completely wrong?

Maik

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

[kdeconnect] [Bug 391484] kdeconnectd crashs in Notification::parseNetworkPackage at plugins/notifications/notification.cpp:177

[林博仁]

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

林博仁  changed:

   What|Removed |Added

Summary|kdeconnectd crashs in   |kdeconnectd crashs in
   |Notification::parseNetworkP |Notification::parseNetworkP
   |ackage at at|ackage at
   |plugins/notifications/notif |plugins/notifications/notif
   |ication.cpp:177 |ication.cpp:177

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

[kdeconnect] [Bug 391484] New: kdeconnectd crashs in Notification::parseNetworkPackage at at plugins/notifications/notification.cpp:177

[林博仁]

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

Bug ID: 391484
   Summary: kdeconnectd crashs in
Notification::parseNetworkPackage at at
plugins/notifications/notification.cpp:177
   Product: kdeconnect
   Version: 1.2.1
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: buo.ren@gmail.com
  Target Milestone: ---

Stacktrace
--
#0  Notification::parseNetworkPackage (this=this@entry=0x0, np=...)
at /workspace/build/plugins/notifications/notification.cpp:177
#1  0x7fffd37cc471 in Notification::update (this=this@entry=0x0, np=...)
at /workspace/build/plugins/notifications/notification.cpp:79
#2  0x7fffd37d2256 in NotificationsDbusInterface::processPackage (
this=0x7e8000, np=...)
at /workspace/build/plugins/notifications/notificationsdbusinterface.cpp:96
#3  0x7fffd37ccc7d in NotificationsPlugin::receivePackage (this=0x7e7dd0, 
np=...)
at /workspace/build/plugins/notifications/notificationsplugin.cpp:59
#4  0x77bbd538 in Device::privateReceivedPackage (
this=, np=...) at /workspace/build/core/device.cpp:345
#5  0x75d757b6 in QtPrivate::QSlotObjectBase::call (a=0x7fffbd10, 
r=0x767a30, this=)
at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:378
#6  QMetaObject::activate (sender=sender@entry=0x7afd70, 
signalOffset=, 
local_signal_index=local_signal_index@entry=4, 
argv=argv@entry=0x7fffbd10) at kernel/qobject.cpp:3749
#7  0x75d75d97 in QMetaObject::activate (
sender=sender@entry=0x7afd70, 
m=m@entry=0x77dd5ac0 , 
local_signal_index=local_signal_index@entry=4, 
argv=argv@entry=0x7fffbd10) at kernel/qobject.cpp:3628
#8  0x77bc3ec5 in DeviceLink::receivedPackage (
this=this@entry=0x7afd70, _t1=...)
at /workspace/build/obj-x86_64-linux-gnu/core/moc_devicelink.cpp:209
#9  0x77ba0b32 in LanDeviceLink::dataReceived (this=0x7afd70)
at /workspace/build/core/backends/lan/landevicelink.cpp:133
#10 0x75d757b6 in QtPrivate::QSlotObjectBase::call (a=0x7fffbed0, 
r=0x7afd70, this=)
at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:378
#11 QMetaObject::activate (sender=sender@entry=0x7dcb80, 
signalOffset=,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0)
at kernel/qobject.cpp:3749
#12 0x75d75d97 in QMetaObject::activate (
sender=sender@entry=0x7dcb80, 
m=m@entry=0x77dd5980 , 
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0)
at kernel/qobject.cpp:3628
#13 0x77bc4150 in SocketLineReader::readyRead (
this=this@entry=0x7dcb80)
at /workspace/build/obj-x86_64-linux-gnu/core/moc_socketlinereader.cpp:134
#14 0x77ba5ae6 in SocketLineReader::dataReceived (this=0x7dcb80)
at /workspace/build/core/backends/lan/socketlinereader.cpp:51
#15 0x75d757b6 in QtPrivate::QSlotObjectBase::call (a=0x7fffc020, 
r=0x7dcb80, this=)
at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:378
#16 QMetaObject::activate (sender=0xe99040, signalOffset=, 
local_signal_index=, argv=)
at kernel/qobject.cpp:3749
#17 0x7510fb07 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#18 0x750f39e1 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#19 0x75d75489 in QMetaObject::activate (sender=0x81a4e0, 
signalOffset=, local_signal_index=, 
argv=) at kernel/qobject.cpp:3766
#20 0x750c1773 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#21 0x750c182c in ?? ()
   from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#22 0x750d20e1 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#23 0x76a88acc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#24 0x76a90417 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#25 0x75d483c8 in QCoreApplication::notifyInternal2 (
receiver=0x79fa90, event=event@entry=0x7fffd4e0)
at kernel/qcoreapplication.cpp:1044
#26 0x75da022d in QCoreApplication::sendEvent (event=0x7fffd4e0, 
receiver=)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:234
#27 socketNotifierSourceDispatch (source=0x6cccd0)
at kernel/qeventdispatcher_glib.cpp:106
#28 0x7fffeffbb197 in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x7fffeffbb3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x7fffeffbb49c in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#31 0x75d9f5af in 

[plasmashell] [Bug 391359] System Monitor Plasma Widgets break rendering in Plasma Shell

[Dan]

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

--- Comment #1 from Dan  ---
Created attachment 111233
  --> https://bugs.kde.org/attachment.cgi?id=111233=edit
qdbus org.kde.KWin /KWin supportInformation > Kwin-info.txt

Should this be relevant

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

[konsole] [Bug 327541] konsole loses keyboard focus, need to use mouse to regain it

[Ahmad Samir]

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

Ahmad Samir  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||a.samir...@gmail.com
 Resolution|--- |UNMAINTAINED

--- Comment #8 from Ahmad Samir  ---
This might be caused by the "Sticky Keys" accessibility feature (systemsettings
-> Accessibility -> Modifier Keys.

Closing as KDE4/konsole is no longer maintained. Feel free to reopen if you can
still reproduce it with a currently supported konsole version.

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

[digikam] [Bug 386959] Properties view: wrong creation date [patch]

[bugzilla_noreply]

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

--- Comment #12 from caulier.gil...@gmail.com ---
>Gilles, are you really sure that the Exif tags Exif.Photo.DateTimeOriginal or 
>>Exif.Photo.DateTimeDigitized exist in an XMP sidcar file?

Both tags exists in XMP definition of Exif namespace :

https://github.com/Exiv2/exiv2/blob/master/src/properties.cpp#L813
https://github.com/Exiv2/exiv2/blob/master/src/properties.cpp#L816

There exists also for video namespace :

https://github.com/Exiv2/exiv2/blob/master/src/properties.cpp#L1388
https://github.com/Exiv2/exiv2/blob/master/src/properties.cpp#L1389

Gilles

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

[digikam] [Bug 388320] Selecting print layout does not stay selected.

[bugzilla_noreply]

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

r...@robdavies.net changed:

   What|Removed |Added

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

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

[krita] [Bug 391481] Gmic return empty pixels

[David REVOY]

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

--- Comment #2 from David REVOY  ---
Thank you @boud! 
Yes, I tested reverting this commit on a local branch and now it's working.
https://www.peppercarrot.com/extras/temp/2018-03-06_screenshot_220142_net.jpg

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

[Falkon] [Bug 391461] Enchancement for Speed Dial

[wizard160888]

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

--- Comment #1 from wizard160888  ---
Created attachment 111232
  --> https://bugs.kde.org/attachment.cgi?id=111232=edit
My problem)

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

[konsole] [Bug 391445] Font changes doesn't saves in Konsole after rebooting

[Sergio Torres Soldado]

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

Sergio Torres Soldado  changed:

   What|Removed |Added

 CC||torres.sold...@gmail.com

--- Comment #4 from Sergio Torres Soldado  ---
This also happens to me using konsole 17.12.2 libqt* 5.10.1 Archlinux. A reboot
is not necessary in my case, I just need to launch a new Konsole instance.

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

[kdevelop] [Bug 391470] Building UnrealEngine 4.18 with KDevelop

[Martin Linklater]

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

--- Comment #3 from Martin Linklater  ---
It's worth mentioning I got UE4 via 'git clone' and then ran 'setup.sh' and
'GenerateProjectFiles.sh'. After those steps there should be a KDevelop project
file inside the UnrealEngine folder.

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

[kdevelop] [Bug 391470] Building UnrealEngine 4.18 with KDevelop

[Martin Linklater]

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

--- Comment #2 from Martin Linklater  ---
Hi. I downloaded UE4 and opened the KDevelop UE4 project. I then right-clicked
on the project and selected 'build' from the drop down menu. That's when the
crash happened. I'm new to KDevelop so as far as I know it is a stock install.

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

[kdeconnect] [Bug 391483] New: Low battery notification shown twice

[Kai Uwe Broulik]

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

Bug ID: 391483
   Summary: Low battery notification shown twice
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: k...@privat.broulik.de
  Target Milestone: ---

When my phone battery runs low (reaches the 15% threshold where it auto-engages
battery saving mode) I get two identical battery low notifications from KDE
Connect for my phone.

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

[gwenview] [Bug 388353] In View mode, with the scroll behavior set to "Browse", scrolling with the touchpad is too fast

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

Summary|Scrolling with the touchpad |In View mode, with the
   |is too fast |scroll behavior set to
   ||"Browse", scrolling with
   ||the touchpad is too fast

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

[gwenview] [Bug 388353] Scrolling with the touchpad is too fast

[Nate Graham]

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

--- Comment #16 from Nate Graham  ---
You may be thinking of https://bugreports.qt.io/browse/QTBUG-59261, which is
not the cause for two reasons:
- It only affected the libinput driver, but RaitaroH is using the Synaptics
driver
- The bug caused touchpad scrolling with libinput to be too slow, not too fast

Or maybe you're thinking of another Qt bug that I'm not as familiar with?

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

[kmymoney] [Bug 391453] Displaying the ledger without an account having been selected displays a closed account

[David Nelson]

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

--- Comment #4 from David Nelson  ---
I just cherry-picked your commit 6a5731e0 and it now looks good!

Sorry for all the fuss about a minor issue.

This was the last of my bugs, but I'll keep looking.

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

[digikam] [Bug 391477] Cropping (or resizing) does not adjust face rectangle positions

[Maik Qualmann]

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

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

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

[digikam] [Bug 286529] Face tag rectangles not adjusted after to apply aspect ratio crop tool

[Maik Qualmann]

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

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

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

[Discover] [Bug 391482] New: Support permissions connecting/disconnecting snap interfaces

[Emanuele]

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

Bug ID: 391482
   Summary: Support permissions connecting/disconnecting snap
interfaces
   Product: Discover
   Version: 5.12.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Snap Backend
  Assignee: aleix...@kde.org
  Reporter: emanu@gmail.com
  Target Milestone: ---

Created attachment 111231
  --> https://bugs.kde.org/attachment.cgi?id=111231=edit
screenshot ubuntu-software

With the snap you have the ability to enable the permissions of the APP: home
or USB devices ...
Recently on Ubuntu software have implemented this feature, it would be very
convenient to be able to do it on discover.
An example screenshot is attached.

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

[Discover] [Bug 388261] App icons should respect active icon theme

[bugzilla_noreply]

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

f.alexander.wi...@gmail.com changed:

   What|Removed |Added

 CC||f.alexander.wi...@gmail.com

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

[Spectacle] [Bug 390652] Capturing the active window fails if compositing is off and the window touches a screen border

[Henrik Fehlauer]

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

Henrik Fehlauer  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/spe
   ||ctacle/5d2e20ce7e4c19fbd722
   ||7ab750ea6b31c9f8968a

--- Comment #14 from Henrik Fehlauer  ---
Git commit 5d2e20ce7e4c19fbd7227ab750ea6b31c9f8968a by Henrik Fehlauer, on
behalf of Alex Nemeth.
Committed on 06/03/2018 at 20:29.
Pushed by rkflx into branch 'master'.

Set screen bounds for active window grab when compositor is disabled

Summary:
It failed to capture the window area when the window was outside of the screen
and showed a null image to the user when compositor was not enabled.
Now it only captures the area that is on the screen.

Reviewers: #spectacle, rkflx, ngraham, broulik

Reviewed By: #spectacle, rkflx, ngraham

Subscribers: davidedmundson, broulik, ngraham

Tags: #spectacle

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

M  +9-0src/PlatformBackends/X11ImageGrabber.cpp

https://commits.kde.org/spectacle/5d2e20ce7e4c19fbd7227ab750ea6b31c9f8968a

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

[krita] [Bug 391481] Gmic return empty pixels

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org

--- Comment #1 from Boudewijn Rempt  ---
Hm, that must've been 71374b68c9d0a98c0fb87ba3703cdaf6f4d3bbb2 then...

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

[krita] [Bug 391481] New: Gmic return empty pixels

[David REVOY]

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

Bug ID: 391481
   Summary: Gmic return empty pixels
   Product: krita
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: G'Mic for Krita
  Assignee: krita-bugs-n...@kde.org
  Reporter: i...@davidrevoy.com
  Target Milestone: ---

Hi,
It's a behavior I noticed only today, every GMIC filter I try return nothing in
Krita; it deletes the pixels in case of a selection and the full content of the
layer in case of applying a filter on a layer. It was working fine for sure
last week (I used GMIC during my weekly wednesday streaming with git~master
compiled at morning).

To reproduce:
=
1. Open a new canvas, do a quick stroke on it.
2. Go into Filter > Start GMIC-Qt
3. Apply a simple filter of your choice (eg ; Artistic > Felt Pen )
4. Press ok.

Result :

Just after GMIC-Qt dialog close, Krita delete the content of the layer (or
selection).

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

[kate] [Bug 391475] Find: "Match case sensitive" icon is invisible

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #4 from Nate Graham  ---
This is an issue with your icon theme not providing those icons. If they're not
present, then the buttons will lack icons, and because these buttons only have
borders when you hover the mouse over them, they look invisible without icons.

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

[gwenview] [Bug 388353] Scrolling with the touchpad is too fast

[Henrik Fehlauer]

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

--- Comment #15 from Henrik Fehlauer  ---
Why is it not a Qt issue? Maybe I'm mixing up things, but wasn't there a
problem where a newer Qt would send a gazillion of wheel events? Did someone
actually test with a really old distro with an old Qt whether the problem is
also present there?

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

[gwenview] [Bug 388353] Scrolling with the touchpad is too fast

[Nate Graham]

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

--- Comment #14 from Nate Graham  ---
Yes, seriously:
- It's not a Plasma issue since Plasma doesn't affect apps' scrolling
implementations
- It's not an issue with the Qt scrollview since the problem described in this
bug pertains to a custom scrolling implementation
- It's not a driver issue (e.g. with synaptics or libinput) issue because it
doesn't affect everything, just certain custom scrolling implementations like
this one

That leaves individual apps as the culprits. It's not at all a surprise to me
that scrolling with a touchpad is still a second-class citizen in Linux
software. Linux (and Windows, to be fair) folks have been relatively slow to
adopt laptops with touchpads as full-time work machines without plugging in
external mice, probably due to historically abominable touchpad input drivers
and software support.

We've already fixed Gwenview to handle touchpad scrolling more reasonably in
other contexts; see for example Bug 378584.

That was a pretty small patch; would you like to have a go at producing a patch
based on that for this issue?

Here's the documentation: https://community.kde.org/Get_Involved/development

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

[lattedock] [Bug 391480] New: Missing Keywords entry in desktop file

[Scarlett Clark]

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

Bug ID: 391480
   Summary: Missing Keywords entry in desktop file
   Product: lattedock
   Version: git (master)
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: sgcl...@kde.org
  Target Milestone: ---

While packaging for debian I ran into.

I: latte-dock: desktop-entry-lacks-keywords-entry
usr/share/applications/org.kde.latte-dock.desktop
N: 
N:This .desktop file does either not contain a "Keywords" entry or it does
N:not contain any keywords not already present in the "Name" or
N:"GenericName" entries.
N:
N:.desktop files are organized in key/value pairs (similar to .ini files).
N:"Keywords" is the name of the entry/key in the .desktop file containing
N:keywords relevant for this .desktop file.
N:
N:The desktop-file-validate tool in the desktop-file-utils package is
N:useful for checking the syntax of desktop entries.
N:
N:Refer to
N:   
https://specifications.freedesktop.org/desktop-entry-spec/1.1/ar01s05.html,
N:https://bugs.debian.org/693918, and
N:https://wiki.gnome.org/Initiatives/GnomeGoals/DesktopFileKeywords for
N:details.
N:
N:Severity: wishlist, Certainty: certain
N:
N:Check: menu-format, Type: binary

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

[krita] [Bug 372823] image size settings for render export

[Scott Petrovic]

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

Scott Petrovic  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
 CC||scottpetro...@gmail.com

--- Comment #4 from Scott Petrovic  ---
Krita 4.0 has the ability to export out videos with different width, height,
and FPS than your original animation settings.

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

[lattedock] [Bug 391474] spelling errors

[Scarlett Clark]

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

Scarlett Clark  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

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