[digikam] [Bug 329091] MySQL : Maintenance leads to crash digiKam

[via KDE Bugzilla]

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

--- Comment #10 from uwe.hai...@gmx.net ---
ok, I got digikam-5.0.0 now. The problem still exists. I have the stderr from
zsh in a file with 622 MB. This are the last lines:
 ---
digikam.general: Check for finish:  51 packages, 0 infos to filter,
hasFinished() false
digikam.general: Check for finish:  51 packages, 0 infos to filter,
hasFinished() false
digikam.general: Check for finish:  51 packages, 0 infos to filter,
hasFinished() false
digikam.general: Check for finish:  51 packages, 0 infos to filter,
hasFinished() false
digikam.general: Check for finish:  51 packages, 0 infos to filter,
hasFinished() false
digikam.general: Check for finish:  51 packages, 0 infos to filter,
hasFinished() false
digikam.facesengine: detectMultiScale gave  (QRect(298,406 146x146))
digikam.facesengine: Verifying face  QRect(298,406 146x146)  using cascade  0
digikam.facesengine: detectMultiScale: image size  226   226  searchIncrement 
1.1  grouping  3  flags  0  min size  88   88 

digikam.database: No location could be retrieved for ""
digikam.general: Entry QRect(1301,444 534x535)456overlapsQRect(1301,444
534x535)456, skipping
digikam.facesengine: detectMultiScale gave  (QRect(41,42 145x145))
digikam.facesengine: Verifying face  QRect(298,406 146x146)  using cascade  1
digikam.facesengine: detectMultiScale: image size  226   226  searchIncrement 
1.1  grouping  3  flags  0  min size  88   88 

digikam.facesengine: detectMultiScale gave  (QRect(39,35 161x161))
digikam.facesengine: Verifying face  QRect(298,406 146x146)  using cascade  2
digikam.facesengine: Verifying face  QRect(298,406 146x146)  using cascade  3
digikam.facesengine: detectMultiScale: image size  226   226  searchIncrement 
1.1  grouping  3  flags  0  min size  88   88 

digikam.facesengine: detectMultiScale gave  ()
digikam.facesengine: Verifying face  QRect(298,406 146x146)  using cascade  4
digikam.facesengine: detectMultiScale: image size  226   226  searchIncrement 
1.1  grouping  3  flags  0  min size  88   88 

digikam.facesengine: detectMultiScale gave  (QRect(69,39 139x139))
digikam.facesengine: Verifying face  QRect(298,406 146x146)  using cascade  5
digikam.facesengine: feature  QRectF(0,0 0.6x0.6) QRect(298,406 146x146)
QRect(298,406 88x88)
digikam.facesengine: detectMultiScale: image size  88   88  searchIncrement 
1.1  grouping  2  flags  0  min size  15   15 

digikam.facesengine: detectMultiScale gave  (QRect(29,45 26x39))
digikam.facesengine: Verifying face  QRect(298,406 146x146)  using cascade  6
digikam.facesengine: feature  QRectF(0.4,0 0.6x0.6) QRect(298,406 146x146)
QRect(356,406 88x88)
digikam.facesengine: detectMultiScale: image size  88   88  searchIncrement 
1.1  grouping  2  flags  0  min size  15   15 

digikam.facesengine: detectMultiScale gave  (QRect(27,45 26x39))
digikam.facesengine: Verifying face  QRect(298,406 146x146)  using cascade  7
digikam.facesengine: feature  QRectF(0.2,0.25 0.6x0.6) QRect(298,406 146x146)
QRect(327,443 88x88)
digikam.facesengine: detectMultiScale: image size  88   88  searchIncrement 
1.1  grouping  2  flags  0  min size  15   15 

digikam.facesengine: detectMultiScale gave  ()
digikam.facesengine: Verifying face  QRect(298,406 146x146)  using cascade  8
digikam.facesengine: feature  QRectF(0.1,0.4 0.8x0.6) QRect(298,406 146x146)
QRect(313,464 117x88)
digikam.facesengine: detectMultiScale: image size  117   88  searchIncrement 
1.1  grouping  2  flags  0  min size  15   15 

digikam.facesengine: detectMultiScale gave  ()
digikam.general: Found 1 faces in "2012-04-02 19.17.13.JPG" QSize(1944, 2592)
QSize(1944, 2592)
digikam.general: Check for finish:  51 packages, 0 infos to filter,
hasFinished() false
digikam.general: Entry QRect(1369,290 346x347)456overlapsQRect(1369,290
346x347)456, skipping
digikam.general: Check for finish:  51 packages, 0 infos to filter,
hasFinished() false
digikam.general: Entry QRect(1557,949 211x211)456overlapsQRect(1557,949
211x211)456, skipping

---
Do you think, the file will help?

A few problems are new:

- can't change to german
- no right bar in the album view (comment, tags, map etc...)
- no settings for the import, import doesn't work
- only 15 kipiplugins?

starting digikam leads to this message:
"Error message: The database is not valid: the "DBThumbnailsVersion" setting
does not exist. The current database schema version cannot be verified. Try to
start with an empty database."

This comes since updating to 5.0.0..

Thanks for your support

uhai

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

[plasmashell] [Bug 366153] New: All Window Icons Are Intermittently Become "Active" on Task Manager Falsely

[Mikiya Okuno via KDE Bugzilla]

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

Bug ID: 366153
   Summary: All Window Icons Are Intermittently Become "Active" on
Task Manager Falsely
   Product: plasmashell
   Version: 5.7.2
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: mikiya.ok...@gmail.com
CC: plasma-b...@kde.org

When working on KF 5.24/KDE Plasma 5.7, window icons on task manager become
falsly active intermittently. I mean all window icons have same colors as if
they are active. After mouse over, window icons are fixed and become inactive
if they are actually inactive.

Reproducible: Sometimes

Steps to Reproduce:
1. Open/close windows.
2. Switch desktop using pager.
3. Make one window full-screen.
etc etc

Actual Results:  
You'll see the problem intermittently under normal operation.

Expected Results:  
Window icon should indicate the actual status.

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

[kmymoney4] [Bug 366043] KMyMoney crashes along with KNotify when searching for transactions

[Rob V via KDE Bugzilla]

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

--- Comment #11 from Rob V  ---
I have tried with Breeze initially, then switched back to Oxygen, and the crash
occurs consistently with both.

-Original Message-
From: "Rex Dieter via KDE Bugzilla" 
Sent: ‎27/‎07/‎2016 00:19
To: "rvalk...@gmail.com" 
Subject: [kmymoney4] [Bug 366043] KMyMoney crashes along with KNotify
whensearching for transactions

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

--- Comment #10 from Rex Dieter  ---
What widget style are you using (if other than default breeze)?

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

[gwenview] [Bug 366152] New: video crash

[via KDE Bugzilla]

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

Bug ID: 366152
   Summary: video crash
   Product: gwenview
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: kng.r...@yahoo.com
CC: myr...@kde.org

Application: gwenview (15.12.3)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-31-generic x86_64
Distribution: Ubuntu 16.04.1 LTS

-- Information about the crash:
was spacing through a directory of images and videos. the images displayed
correctly and the video played correctly. the crash occurs EVERY TIME i move
onto the next item whether it is video or an image

-- Backtrace:
Application: Gwenview (gwenview), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x in ?? ()
#7  0x7f80ef1e1db1 in
QGraphicsItem::dragLeaveEvent(QGraphicsSceneDragDropEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x7f80ef1f650c in QGraphicsItemPrivate::setVisibleHelper(bool, bool,
bool, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x7f80ef20f0a2 in QGraphicsProxyWidget::eventFilter(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x7f80edc31412 in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f80eeef403c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x7f80eeef9516 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x7f80edc3162b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f80eef32013 in QWidgetPrivate::hide_helper() () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x7f80eef367c0 in QWidget::setVisible(bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x7f80eef321e1 in
QWidgetPrivate::close_helper(QWidgetPrivate::CloseMode) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x7f80eef327cb in QWidget::~QWidget() () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x7f80ebb44c9c in ?? () from
/usr/lib/x86_64-linux-gnu/libphonon4qt5.so.4
#19 0x7f80ef20adba in QGraphicsProxyWidget::~QGraphicsProxyWidget() () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x7f80f1a58b59 in ?? () from
/usr/lib/x86_64-linux-gnu/libgwenviewlib.so.5
#21 0x7f80ef1fc156 in QGraphicsItem::~QGraphicsItem() () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#22 0x7f80ef1fc3e3 in QGraphicsObject::~QGraphicsObject() () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#23 0x7f80ef24b9b5 in QGraphicsWidget::~QGraphicsWidget() () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#24 0x7f80f1a4d859 in Gwenview::DocumentView::~DocumentView() () from
/usr/lib/x86_64-linux-gnu/libgwenviewlib.so.5
#25 0x7f80edc60ec0 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x7f80ef24ce8b in QGraphicsWidget::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#27 0x7f80eeef405c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#28 0x7f80eeef9516 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#29 0x7f80edc3162b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#30 0x7f80edc33a26 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#31 0x7f80edc87673 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#32 0x7f80e83411a7 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#33 0x7f80e8341400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#34 0x7f80e83414ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#35 0x7f80edc87a7f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#36 0x7f80edc2edea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#37 0x7f80edc36e8c in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#38 0x0044ba70 in main ()

Possible duplicates by query: bug 350528, bug 346415, bug 344809.

Reported using DrKonqi

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

[user-manager] [Bug 339784] Only 2 of 3 installed sytemusers are shown in usermanagement

[Burkhard Lueck via KDE Bugzilla]

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

Burkhard Lueck  changed:

   What|Removed |Added

 CC||lu...@hube-lueck.de

--- Comment #1 from Burkhard Lueck  ---
https://bugs.kde.org/show_bug.cgi?id=361832
https://bugs.kde.org/show_bug.cgi?id=336677
https://bugs.kde.org/show_bug.cgi?id=336994

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

[valgrind] [Bug 366035] valgrind misses buffer overflow, segfaults in malloc in localtime

[Frederick Eaton via KDE Bugzilla]

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

--- Comment #8 from Frederick Eaton  ---
> Forcing the channel to 1 at that 'BUG' place has other consequences than just
> allocating a 'too small' buffer.
> As I understand, after this 'forcing to 1', we will also have
> sfinfo.channels that will
> be 1 instead of 2. No idea if that participates (or not) to the problem.

I don't think it does, sfinfo is just used for the output file, if we
give it a smaller number of channels then it will read less data from
the buffer.

> So, I will assume that this snd_pcm_readi is not doing a read syscall but is
> rather
> an ioctl, probably corresponding to this trace:
> SYSCALL[14734,1](16) sys_ioctl ( 4, 0x80184151, 0xffefff170 ) --> [async]
> ... 
> SYSCALL[14734,1](16) ... [async] --> Success(0x0) 
> 
> I am not sure how to translate this 0x80184151 into one of the 'symbolic'
> ioctl
> SND/PCM things handled in syswrap-linux.c.
> I suspect that some SND/PCM ioctl are not properly described  as
> reading/writing the memory
> pointed to by the ARG3 of the ioctl. Then of course, that might do a buffer
> overrun
> which is undetected by Valgrind, which then corrupts the end of the buffer
> block
> and the malloc data structure/memory/blocks following this (too small)
> buffer.

That sounds very likely to be the source of the problem, good
detective work!

> So, at this point, what we need to confirm is:
>   is snd_pcm_readi really doing an ioctl ?
>   if yes, which one ? (i.e. which 'symbolic' ioctl is it doing ?)
> e.g. maybe it is  case VKI_SOUND_PCM_READ_CHANNELS:
> and if this is the case, then syswrap-linux.c describes that this ioctl
> is writing the
> size of an int, while it clearly reads more than an int, if the ioctl is
> reading real data.
>  If now that is the bug, and syswrap-linux.c really should describe that it
> reads a bunch
>  of bytes depending on previously set parameters, then I think that is a lot
> of work to do,
>  as basically syswrap-linux.c will need to record the previous SND/PCM ioctl
> to know what
>  is the expected size of such an ioctl ARG3.
> 
>  Now, maybe this ioctl is rather something like VKI_SNDRV_CTL_IOCTL_TLV_READ
>  but I do not see how that matches this buffer logic and the snd_pcm_readi,
> which only
>   has a buffer argument.
> 
> So, to understand where the undetected buffer overflow comes from, I guess
> some
> alsa/snd lib source code reading might be needed, to see how snd_pcm_readi
> is implemented
> in terms of ioctl.
> We can then check if syswrap-linux.c properly describes what this ioctl is
> accessing
> in read and/or write mode.
> 
> Hoping this helps 

I hope it helps too! What do you want me to do now? Is there some
other tracing facility which I should run to help you identify the
problematic ioctl? Do you want me to make the example program more
minimal? Perhaps I could do the latter, otherwise I don't really have
much time - I just wanted to report this bug as a kind of housekeeping
task, so that upstream knows about the problem. We can maybe rename it
to something like "valgrind doesn't correctly track buffer overflows
from certain ALSA ioctls". Thank you,

Frederick

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

[kdenlive] [Bug 366069] Keyboard commands ALT+ and ALT+ get stuck on Guides

[Steve via KDE Bugzilla]

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

--- Comment #3 from Steve  ---
Make sure "Show Markers Comments" is enabled to see the labels Skit 1, Skit 2
etc.

It still fails with it disabled, but this makes it easier to see what I am
talking about.

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

[kdenlive] [Bug 366069] Keyboard commands ALT+ and ALT+ get stuck on Guides

[Steve via KDE Bugzilla]

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

--- Comment #2 from Steve  ---
Created attachment 100324
  --> https://bugs.kde.org/attachment.cgi?id=100324=edit
TEST-Orphantastic.kdenlive

I have uploaded my latest project file minus the media clips
(TEST-Orphantastic.kdenlive).

Open it and just use placeholders for all of the media. I tested this and the
error occurs.

When I ALT+ through this project it gets stuck on the guides. Just
play with it moving though the project left and right. I am interested to hear
if you can reproduce this error. 

>From the beginning going from left to right I get stuck on Skit 1, Skit 2, Skit
3. I can pass though Skit 4.

Cursor after Skit 4 going from right to left I get stuck on Skit 4. I can pass
through Skit (321) all the way to the beginning.

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

[Akonadi] [Bug 366151] New: Gmail shutting down

[J Coombs via KDE Bugzilla]

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

Bug ID: 366151
   Summary: Gmail shutting down
   Product: Akonadi
   Version: unspecified
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: IMAP resource
  Assignee: chrig...@fastmail.fm
  Reporter: gribn...@hotmail.com
CC: kdepim-b...@kde.org, vkra...@kde.org

Application: akonadi_imap_resource (4.14)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.16.0-38-generic x86_64
Distribution: Linux Mint 17.2 Rafaela

-- Information about the crash:
- What I was doing when the application crashed:
Using Vivaldi Browser and watching Flash video on Forefox browser. Alert popped
up. Was not using mail at he time.

-- Backtrace:
Application: Google Mail (bigdaddymobaddie) of type IMAP E-Mail Server
(akonadi_imap_resource), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f38cd5fc7c0 (LWP 2711))]

Thread 2 (Thread 0x7f38b3fff700 (LWP 4172)):
#0  0x7f38c8f90fdd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f38c7f16fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f38c7f170ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f38ccc2f7be in QEventDispatcherGlib::processEvents
(this=0x7f38a800f490, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#4  0x7f38ccc010af in QEventLoop::processEvents
(this=this@entry=0x7f38b3ffee20, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f38ccc013a5 in QEventLoop::exec (this=this@entry=0x7f38b3ffee20,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7f38ccafdc5f in QThread::exec (this=) at
thread/qthread.cpp:537
#7  0x7f38ccb0032f in QThreadPrivate::start (arg=0xc4ec50) at
thread/qthread_unix.cpp:349
#8  0x7f38c85fb184 in start_thread (arg=0x7f38b3fff700) at
pthread_create.c:312
#9  0x7f38c8f9e37d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f38cd5fc7c0 (LWP 2711)):
[KCrash Handler]
#6  0x0001 in ?? ()
#7  0x7f38ccc15999 in QObject::disconnect (sender=0xc44fd0, signal=0xc41819
"stateChanged(KIMAP::Session::State,KIMAP::Session::State)",
signal@entry=0x47b588
"2stateChanged(KIMAP::Session::State,KIMAP::Session::State)",
receiver=receiver@entry=0xc17b70, method=0xc469b9
"onSessionStateChanged(KIMAP::Session::State,KIMAP::Session::State)",
method@entry=0x47b540
"1onSessionStateChanged(KIMAP::Session::State,KIMAP::Session::State)") at
kernel/qobject.cpp:2883
#8  0x0044fbb5 in SessionPool::killSession (this=this@entry=0xc17b70,
session=0xc44fd0, termination=termination@entry=SessionPool::LogoutSession) at
../../../resources/imap/sessionpool.cpp:182
#9  0x0044ff55 in SessionPool::disconnect (this=0xc17b70,
termination=termination@entry=SessionPool::LogoutSession) at
../../../resources/imap/sessionpool.cpp:115
#10 0x0043108b in ImapResourceBase::doSetOnline (this=0xb9b3d0,
online=) at ../../../resources/imap/imapresourcebase.cpp:575
#11 0x7f38ccffc3d1 in Akonadi::AgentBase::setOnlineInternal(bool) () from
/usr/lib/libakonadi-kde.so.4
#12 0x7f38ccffc622 in Akonadi::AgentBase::setTemporaryOffline(int) () from
/usr/lib/libakonadi-kde.so.4
#13 0x0042e8fe in ImapResourceBase::onConnectDone (this=0xb9b3d0,
errorCode=-1090044704, errorString=...) at
../../../resources/imap/imapresourcebase.cpp:314
#14 0x004644ff in ImapResourceBase::qt_static_metacall (_o=0xc44fd0,
_c=3204922592, _id=1, _a=0x0) at moc_imapresourcebase.cpp:123
#15 0x7f38ccc1687a in QMetaObject::activate (sender=sender@entry=0xc17b70,
m=m@entry=0x482160 ,
local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x7ffcbf074090)
at kernel/qobject.cpp:3539
#16 0x004649a4 in SessionPool::connectDone (this=this@entry=0xc17b70,
_t1=_t1@entry=8, _t2=...) at moc_sessionpool.cpp:160
#17 0x00450bf4 in SessionPool::cancelSessionCreation
(this=this@entry=0xc17b70, session=,
errorCode=errorCode@entry=8, errorMessage=...) at
../../../resources/imap/sessionpool.cpp:247
#18 0x00451008 in SessionPool::onLoginDone (this=0xc17b70,
job=0xc4ce30) at ../../../resources/imap/sessionpool.cpp:372
#19 0x00464a0c in SessionPool::qt_static_metacall (_o=0xc44fd0,
_c=3204922592, _id=1, _a=0x0) at moc_sessionpool.cpp:94
#20 0x7f38ccc1687a in QMetaObject::activate (sender=sender@entry=0xc4ce30,
m=m@entry=0x7f38c9eb0600 ,
local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffcbf0743c0)
at kernel/qobject.cpp:3539
#21 0x7f38c9b20912 in KJob::result (this=this@entry=0xc4ce30,
_t1=_t1@entry=0xc4ce30) at ./kjob.moc:207
#22 0x7f38c9b20950 in KJob::emitResult (this=0xc4ce30) at
../../kdecore/jobs/kjob.cpp:318
#23 0x7f38ca8806b7 in 

[kdenlive] [Bug 366107] Crash when clicking on track compositing menu

[farid via KDE Bugzilla]

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

--- Comment #3 from farid  ---
OK I just compiled MLT from git and it didn't crash. Is there going to be an
MLT release before 16.08?

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

[digikam] [Bug 366150] New: Tags don't appear at all

[Robinson Twins via KDE Bugzilla]

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

Bug ID: 366150
   Summary: Tags don't appear at all
   Product: digikam
   Version: 5.0.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tags
  Assignee: digikam-de...@kde.org
  Reporter: robinsontwin...@gmail.com

I have Digikam 5.0 on a Windows 10 machine and tags come up without a problem.
But my other computer is running Ubuntu Linux and tags don't appear at all and
when I try to add a Tag I get an error message: Failed to add tag to database.
What can I do about this problem?

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

[kicker] [Bug 50457] let me change the menu show delay

[Zane Tu via KDE Bugzilla]

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

Zane Tu  changed:

   What|Removed |Added

 CC||zan...@gmail.com

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

[plasma-pa] [Bug 366149] Cannot handle pulseaudio card profile and sink change

[Raman Gupta via KDE Bugzilla]

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

Raman Gupta  changed:

   What|Removed |Added

Summary|Cannot handle pulseaudio|Cannot handle pulseaudio
   |card profile change |card profile and sink
   ||change

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

[plasma-pa] [Bug 366149] New: Cannot handle pulseaudio card profile change

[Raman Gupta via KDE Bugzilla]

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

Bug ID: 366149
   Summary: Cannot handle pulseaudio card profile change
   Product: plasma-pa
   Version: 5.7.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: rocketra...@gmail.com
CC: plasma-b...@kde.org

This is a regression in Plasma 5.7.1 relative to Plasma 5.6.5.

I have an Intel-HDA card with PulseAudio 7.1.1 on Fedora 23. My card is hooked
up to both my external speakers as well as a headset. I can switch the audio
from headset to speakers by using the commands:

```
pactl set-card-profile alsa_card.pci-_00_1b.0
output:analog-surround-40+input:analog-stereo
pactl set-sink-port alsa_output.pci-_00_1b.0.analog-surround-40
analog-output-lineout
amixer -c $CARD sset "Auto-Mute Mode" Disabled
amixer -c $CARD sset 'Headphone',1 100 mute
```

and vice-versa:

```
pactl set-card-profile alsa_card.pci-_00_1b.0
output:analog-stereo+input:analog-stereo
pactl set-sink-port alsa_output.pci-_00_1b.0.analog-stereo
analog-output-headphones
amixer -c $CARD sset "Auto-Mute Mode" Enabled
amixer -c $CARD sset 'Headphone',1 100 unmute
```

As of Plasma 5.7.1, the above commands still work, but KDE seems to lose its
connection to PulseAudio when they are run. In `.xsession-errors`, immediately
upon the switch I see:

org.kde.plasma.pulseaudio: No object for name
"alsa_output.pci-_00_1b.0.analog-surround-40"

After that point, I cannot, use the volume up/down/mute keys successfully.
Though moving the sliders in the pulse-pa applet does still work.

A restart of plasma restores the connection to pulseaudio and restores the
up/down/mute key functionality.

Reproducible: Always

Steps to Reproduce:
1. Change pulseaudio card profile and sink port
2. Attempt to use volume up/down/mute buttons

Actual Results:  
Volume buttons no longer work

Expected Results:  
Volume buttons should still work

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

[kmymoney4] [Bug 362373] layout seems to be changed to TXT mode, losing HTML formats

[CPL via KDE Bugzilla]

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

CPL  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from CPL  ---
Even with 4.8 version, the problem still remains.

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

[dolphin] [Bug 363548] file area becomes inaccessible for the mouse after opening a file on hidpi screen when using a multi monitor setting

[Michael via KDE Bugzilla]

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

--- Comment #4 from Michael  ---
Took a closer look at this bug since I'd quite like it fixed.

In KItemListController.cpp around line 529, the function: 

bool KItemListController::mousePressEvent(QGraphicsSceneMouseEvent* event,
const QTransform& transform)

does not seem to be receiving any mouse events when clicking on the left half
of the view after the bug is triggered. Debug output is generated from clicks
in this part of the screen before opening a file, but after opening a file the
debug output is gone.

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

[okular] [Bug 366148] New: don't exit 'continuous' mode when operating on markers

[via KDE Bugzilla]

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

Bug ID: 366148
   Summary: don't exit 'continuous' mode when operating on markers
   Product: okular
   Version: 0.24.0
  Platform: unspecified
OS: All
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: ric...@nakts.net

https://docs.kde.org/trunk4/en/kdegraphics/okular/annotations.html says "With a
single left mouse button click on an annotation tool button you can use a tool
once. If you e.g. want to highlight all important parts of a text, activate
that tool permanently by double clicking on the tool button." (implemented in
https://bugs.kde.org/show_bug.cgi?id=161020).

this works - but the marker tool (shortcut 4) is deselected whenever the marked
area is doubleclicked to add text to it, or some marked area is rightclicked to
remove it.

it would be great if these two actions would not exit the 'continuous' mode.

usecase : i have to mark a lot of text and provide some comment on what's wrong
with it. currently, the continuous mode doesn't help as doubleclicking a marked
area to comment on it deselects the continuous mode (and the same with
rightclicking to remove incorrectly added marking).

(sidenote - i was glad to see that the basic feature is already there, thanks
for adding it years ago :) )

Reproducible: Always

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

[plasmashell] [Bug 366147] New: Plasmashell crash when doing a search of application in the application launcher

[Alassane via KDE Bugzilla]

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

Bug ID: 366147
   Summary: Plasmashell crash when doing a search of application
in the application launcher
   Product: plasmashell
   Version: 5.7.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: azou8...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.7.1)

Qt Version: 5.6.1
Frameworks Version: 5.24.0
Operating System: Linux 4.6.4-301.fc24.x86_64 x86_64
Distribution: "Fedora release 24 (Twenty Four)"

-- Information about the crash:
- What I was doing when the application crashed:
Open any application launcher and start typing a search. Plasmashell crash im
- Unusual behavior I noticed:
Dolphin also seem to crash a lot, not sure if related

The crash can be reproduced sometimes.

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

Thread 25 (Thread 0x7fba840cf700 (LWP 6751)):
#0  0x7fbb69401bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fbb6acb001a in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7fbaab0838c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#3  0x7fbaab087a68 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#4  0x7fbaab082a3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#5  0x7fbaab087ac2 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#6  0x7fbaab082a3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#7  0x7fbaab085909 in ThreadWeaver::Thread::run() () at
/lib64/libKF5ThreadWeaver.so.5
#8  0x7fbb6acaf99a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#9  0x7fbb693fc5ca in start_thread () at /lib64/libpthread.so.0
#10 0x7fbb6a0a2ead in clone () at /lib64/libc.so.6

Thread 24 (Thread 0x7fba85774700 (LWP 6750)):
#0  0x7fbb69401bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fbb6acb001a in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7fbaab0838c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#3  0x7fbaab087a68 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#4  0x7fbaab082a3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#5  0x7fbaab087ac2 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#6  0x7fbaab082a3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#7  0x7fbaab085909 in ThreadWeaver::Thread::run() () at
/lib64/libKF5ThreadWeaver.so.5
#8  0x7fbb6acaf99a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#9  0x7fbb693fc5ca in start_thread () at /lib64/libpthread.so.0
#10 0x7fbb6a0a2ead in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7fba85f75700 (LWP 6749)):
#0  0x7fbb69401bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fbb6acb001a in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7fbaab0838c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#3  0x7fbaab087a68 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#4  0x7fbaab082a3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#5  0x7fbaab087ac2 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#6  0x7fbaab082a3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#7  0x7fbaab085909 in ThreadWeaver::Thread::run() () at
/lib64/libKF5ThreadWeaver.so.5
#8  0x7fbb6acaf99a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#9  0x7fbb693fc5ca in start_thread () at /lib64/libpthread.so.0
#10 0x7fbb6a0a2ead in clone () at /lib64/libc.so.6

Thread 22 (Thread 0x7fba86776700 (LWP 6748)):
#0  0x7fbb69401bd0 in 

[dolphin] [Bug 363548] file area becomes inaccessible for the mouse after opening a file on hidpi screen when using a multi monitor setting

[Michael via KDE Bugzilla]

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

Michael  changed:

   What|Removed |Added

 CC||miabr...@gmail.com

--- Comment #3 from Michael  ---
I'm getting the same thing with current KDE Neon. (Plasma 5.6.1, Frameworks
5.24.0, Dolphin 16.04.2)

On my center monitor, mouse clicks register correctly on the right half of the
Dolphin window but not on the left half.

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

[plasmashell] [Bug 356706] The system activity manager insists on opening partially off-screen

[Raman Gupta via KDE Bugzilla]

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

Raman Gupta  changed:

   What|Removed |Added

Version|5.5.0   |5.7.1

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

[systemsettings] [Bug 61582] Feature Request: Display applications in File Associations Window

[Holger via KDE Bugzilla]

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

Holger  changed:

   What|Removed |Added

 CC||h.kl...@gmx.de

--- Comment #10 from Holger  ---
I wanted to associate my little program to three filetypes. The first was peace
of cake, just hit "add" and it will automatically create a appname.desktop file
in ~/.local/share/applications/, but on the second mime-type, it created a
second appname-2.desktop file for the same application. That was not, what I
had hoped for. So I tried it the other way round: Edit the first application
and add more mime-types to it. But since there are a thousand in the tree under
application/ and the tree is not sorted at all, finding my desired type is
really a pain in the ass, forcing me to read the whole list very carefully.

This tree should be sorted and there should be the same search feature in the
small dialog as in the main kcontrol-app.

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

[digikam] [Bug 350574] MIGRATION: MySQL to SQLite fails [patch]

[Richard Mortimer via KDE Bugzilla]

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

--- Comment #11 from Richard Mortimer  ---
(In reply to caulier.gilles from comment #10)
> Richard,
> 
> Swati has proposed a simple patch for this file. Any viewpoint about ?
> 
> Gilles Caulier

I've been discussing the issue with Swati via email today. I don't think that
the patch is a fix for the problem.

The TagsTree is getting migrated wrongly. The attempt to remove the triggers
was just to show that the trigger was definitely causing the problem. I can see
a number of issues:

First off the Tags migration is potentially broken because to work properly
with referential integrity the entries need to be migrated from the root of the
tree outwards. Without that the parent references may not be present when a
child is added. In most cases things will work out fine because the parent will
likely have a lower numbered primary key than the child and hence sorting by id
will make things better. But it is easy to see how things might go wrong if
tags are moved around in the tree. It is easy to detect by looking for entries
where pid > id. But at present things may be broken.

Secondly it seems that either duplicate TagsTree entries are getting added or
maybe somehow not getting added correctly. This needs investigation. It should
be fairly simple to do because it seems that things can be reproduced easily so
it will be possible to use the sqlite3 commandline to investigate the state of
the database when things go wrong.

I'm actually wondering if the add_tag (and other) trigger is getting added to
the database twice. I think I remember that SQLite can have multiple triggers
on one table so maybe there are two triggers trying to add an entry into the
TagsTree table.

Looking at the coreschemaupdater.cpp file there are two places where
createTriggers() is called so that may be relevant. Note I only did a very
quick look at the source so it might be a misleading idea. But I think there is
more investigation that needs doing to find the cause of the problem.

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

[plasmashell] [Bug 365014] All windows hide on repeating desktop click

[Root via KDE Bugzilla]

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

--- Comment #19 from Root  ---
Plasma desktop 5.7.2-1, still experiencing the same glitch after updating

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

[plasmashell] [Bug 362941] Java Process Is Unresponsive In System Tray - Jitsi

[Martin Klapetek via KDE Bugzilla]

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

Martin Klapetek  changed:

   What|Removed |Added

 CC|mklape...@kde.org   |

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

[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU

[via KDE Bugzilla]

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

--- Comment #147 from madc...@atlas.cz ---
You need both qt5-declarative and plasma-nm package built with debugging
symbols to get a useful backtrace. Are you sure you set options=("!strip") in
plasma-nm's PKGBUILD? Without it the debugging symbols get stripped away. I'm
not sure what is the point to run gdb through codedumpctl, running just plain
gdb worked perfectly fine for me.

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

[plasmashell] [Bug 362941] Java Process Is Unresponsive In System Tray - Jitsi

[Joerg Mensmann via KDE Bugzilla]

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

Joerg Mensmann  changed:

   What|Removed |Added

 CC||bugs-...@bitplanet.de

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

[kcontrol] [Bug 127362] the "beeper" feature for the mouse cursor

[Holger via KDE Bugzilla]

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

Holger  changed:

   What|Removed |Added

 CC||h.kl...@gmx.de

--- Comment #3 from Holger  ---
There is an option under visual effects to highlight the current mouseposition
(default shortcut Ctrl+Alt) ... I think this bug is obsolete now.

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

[plasmashell] [Bug 366146] New: Plasma crashes when trying to add second panel

[Pulfer via KDE Bugzilla]

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

Bug ID: 366146
   Summary: Plasma crashes when trying to add second panel
   Product: plasmashell
   Version: master
  Platform: ROSA RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: pul...@list.ru

Plasma crashes when trying to add second panel.

1. Download the ISO from here:
https://abf.rosalinux.ru/platforms/rosa2014.1/products/137/product_build_lists/15748
2. Install it (or boot in live mode)
3. Try to add second panel

Plasma will crash, then restart with second panel added and crash BT info
provided. 

Reproducible: Always

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

[kmymoney4] [Bug 366043] KMyMoney crashes along with KNotify when searching for transactions

[Rex Dieter via KDE Bugzilla]

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

--- Comment #10 from Rex Dieter  ---
What widget style are you using (if other than default breeze)?

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

[plasmashell] [Bug 359661] Digital clock is not updated consistently

[via KDE Bugzilla]

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

k...@barrayar.org changed:

   What|Removed |Added

 CC||k...@barrayar.org

--- Comment #6 from k...@barrayar.org ---
I can confirm this behavior on Plasma 5.6.5 (using backports PPA on Kubuntu
16.04). The clock widget only seems to update once every two seconds.
Occasionally it'll show two consecutive seconds. My usual display is 24-hour
time with seconds and long date, e.g.

16:10:26
Tuesday, July 26, 2016

I thought maybe it might have something to do with the fact that I normally
have two clock widgets, one at the right edge of the bottom panel on each of my
two monitors, but I removed one of the clocks and the other clock still only
updates every ~2 seconds or so.

Also, Plasmashell is currently using about 30% CPU according to GNU top. (By
contrast, on my old 14.04 machine, plasma-desktop is currently using about 0.7%
CPU.) I killed plasmashell (with "kdequitapp5 plasmashell") and then ran
plasmashell & again, and now it's using around 1% CPU, and the clock widget is
updating every second.

So it looks like it's not a bug with the clock per se, but the fact that
Plasmashell eventually decides to just start chewing up tons of CPU for no
apparent reason.

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

[user-manager] [Bug 361832] System settings; account details; user manager: doesn't display the other users. I'm administrator. Using Kubuntu 15.10.

[Holger via KDE Bugzilla]

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

Holger  changed:

   What|Removed |Added

 CC||h.kl...@gmx.de

--- Comment #3 from Holger  ---
please have a look at bug 336677

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

[user-manager] [Bug 354634] User account management: newly entered user does not appear in user list

[Holger via KDE Bugzilla]

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

Holger  changed:

   What|Removed |Added

 CC||h.kl...@gmx.de

--- Comment #1 from Holger  ---
Did you log in as the new user as per bug 336994 ?

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

[user-manager] [Bug 354315] Just the icon of the admin is shown, Some Users are hidden

[Holger via KDE Bugzilla]

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

Holger  changed:

   What|Removed |Added

 CC||h.kl...@gmx.de

--- Comment #1 from Holger  ---
see also bug 336677

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

[user-manager] [Bug 336677] Not all users are shown

[Holger via KDE Bugzilla]

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

Holger  changed:

   What|Removed |Added

 CC||h.kl...@gmx.de

--- Comment #8 from Holger  ---
another possible duplicate could be bug 339784

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

[user-manager] [Bug 336994] User Manager does not show one particular user in the list unless I login as that user

[Holger via KDE Bugzilla]

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

Holger  changed:

   What|Removed |Added

 CC||h.kl...@gmx.de

--- Comment #7 from Holger  ---
On May 8th 2015 I added accounts for my 2 nephews.
The younger nephew username "simon" uid 1001 is missing in kcontrol. He only
logged in that very day and never again (no idea, if he even remembers his
password).
The older nephew username "tobias" uid 1002 logged in a few times (last on June
16th 2016) and is showing in kcontrol as expected.

I've created a new user, showing up fine and also deleted the new user. But
simon is still lost, despite the switch-session-screen offers him for login.

@Gus thanx for the KUser tip, now I can at least change his password, should
the need arise.

There have been intermediate release-upgrades of Kubuntu ... apport claims I
started out with 14.04, working up all the way through 14.10, 15.04, 15.10 and
finally 16.04 now

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

[plasmashell] [Bug 366145] Plasmashell crash after reconnecting WiFi

[Raf via KDE Bugzilla]

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

--- Comment #1 from Raf  ---
Probably it's a replication of bug 346118

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

[plasmashell] [Bug 366145] New: Plasmashell crash after reconnecting WiFi

[Raf via KDE Bugzilla]

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

Bug ID: 366145
   Summary: Plasmashell crash after reconnecting WiFi
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: raf...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.1.27-27-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
My wi-fi acces point was turned off for a couple of minutes. When I turned it
on and my laptop recovered the WiFi connection the plasmashell error occured.

The crash can be reproduced every time.

-- Backtrace:
Application: Plazma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa476a9c7c0 (LWP 2634))]

Thread 16 (Thread 0x7fa460503700 (LWP 2636)):
#0  0x7fa46ffa4bfd in poll () at /lib64/libc.so.6
#1  0x7fa474ef8422 in  () at /usr/lib64/libxcb.so.1
#2  0x7fa474efa00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7fa4626543c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fa47069f32f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fa46f7ae0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7fa46ffad02d in clone () at /lib64/libc.so.6

Thread 15 (Thread 0x7fa45d8d1700 (LWP 2640)):
#0  0x7fa470697ccf in QMutex::unlock() () at /usr/lib64/libQt5Core.so.5
#1  0x7fa4708d1cc5 in  () at /usr/lib64/libQt5Core.so.5
#2  0x7fa46c6814ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fa46c681d80 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7fa46c681f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7fa4708d1d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7fa470878d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7fa47069a61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7fa4739aee18 in  () at /usr/lib64/libQt5Qml.so.5
#9  0x7fa47069f32f in  () at /usr/lib64/libQt5Core.so.5
#10 0x7fa46f7ae0a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7fa46ffad02d in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7fa44c520700 (LWP 2696)):
#0  0x7fa46c681817 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#1  0x7fa46c681df8 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fa46c681f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fa4708d1d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fa470878d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fa47069a61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fa4739aee18 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fa47069f32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fa46f7ae0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fa46ffad02d in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7fa44ac7c700 (LWP 2726)):
#0  0x7fa46ffa4bfd in poll () at /lib64/libc.so.6
#1  0x7fa46c681e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fa46c681f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fa4708d1d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fa470878d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fa47069a61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fa4739aee18 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fa47069f32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fa46f7ae0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fa46ffad02d in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7fa449419700 (LWP 2758)):
#0  0x7fa46f7b203f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fa47617d86b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7fa47617d899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7fa46f7ae0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fa46ffad02d in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7fa3bb40f700 (LWP 2825)):
#0  0x7fa46c67f1ee in  () at /usr/lib64/libglib-2.0.so.0
#1  0x7fa46c68144b in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fa46c681d80 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fa46c681f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fa4708d1d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fa470878d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fa47069a61a 

[konsole] [Bug 178320] Konsole split view: in both views same content

[Praise via KDE Bugzilla]

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

Praise  changed:

   What|Removed |Added

 CC||praiseta...@tiscalinet.it

--- Comment #36 from Praise  ---
I'd like to help this too, as the current behaviour is total nonsense.

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

[kaddressbook] [Bug 331896] Regression: Categories in edit contact window no longer showing

[Johannes Studt via KDE Bugzilla]

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

Johannes Studt  changed:

   What|Removed |Added

 CC||johan...@studt.de

--- Comment #8 from Johannes Studt  ---
(In reply to Martin Burnicki from comment #7)

+1

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

[kdenlive] [Bug 366144] git master - Project bin doesn't automatically switch to Clip Properties widget when "Clip Properties" option is clicked.

[Jesse via KDE Bugzilla]

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

--- Comment #3 from Jesse  ---
Definitely, completely understand for past configurations and behaviors. I do
like the way things are progressing now. I'll test once the updated pops up in
the ppa.

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

[kdenlive] [Bug 366107] Crash when clicking on track compositing menu

[farid via KDE Bugzilla]

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

--- Comment #2 from farid  ---
Compiling from source using AUR in Archlinux. I am using MLT 6.2.

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

[digikam] [Bug 339607] MYSQL : Images not show if corresponding ImageInformation entry does not exist in database [patch]

[via KDE Bugzilla]

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

--- Comment #10 from caulier.gil...@gmail.com ---
Richard,

This patch from Swati sound acceptable for you ?

Gilles Caulier

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

[digikam] [Bug 339607] MYSQL : Images not show if corresponding ImageInformation entry does not exist in database [patch]

[via KDE Bugzilla]

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

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

   What|Removed |Added

Summary|MYSQL : Images not show if  |MYSQL : Images not show if
   |corresponding   |corresponding
   |ImageInformation entry does |ImageInformation entry does
   |not exist in database   |not exist in database
   ||[patch]

--- Comment #9 from caulier.gil...@gmail.com ---
Swati, 

In your patch, did you touch the sqlite schema or only mysql one ?

The patch is a little bit intrusive. Do you test this patch to see if side
effects are introduced in general digiKam use cases ?

Gilles Caulier

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

[kdenlive] [Bug 366107] Crash when clicking on track compositing menu

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #1 from Jean-Baptiste Mardelle  ---
Are you compiling from source or using one of our PPA ? There seems to be a
problem between MLT and Kdenlive.

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

[skrooge] [Bug 366025] Skrooge perpetually asks me to save updated tab state

[via KDE Bugzilla]

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

--- Comment #8 from dberg...@gmail.com ---
Interesting. Can you confirm that all pages are showing a modified state even
after just opening the file? That shouldn't happen, should it?

I have attached a video showing the results of the command you mentioned, as
well as the popups. You can also see that each tab has the "save" icon on it,
even after it has just been opened.

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

[skrooge] [Bug 366025] Skrooge perpetually asks me to save updated tab state

[via KDE Bugzilla]

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

--- Comment #7 from dberg...@gmail.com ---
Created attachment 100323
  --> https://bugs.kde.org/attachment.cgi?id=100323=edit
Proof video

Video showing the bug in action

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

[digikam] [Bug 350574] MIGRATION: MySQL to SQLite fails [patch]

[via KDE Bugzilla]

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

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

   What|Removed |Added

 CC||richm+...@oldelvet.org.uk
Summary|MIGRATION: MySQL to SQLite  |MIGRATION: MySQL to SQLite
   |fails   |fails [patch]

--- Comment #10 from caulier.gil...@gmail.com ---
Richard,

Swati has proposed a simple patch for this file. Any viewpoint about ?

Gilles Caulier

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

[digikam] [Bug 350574] MIGRATION: MySQL to SQLite fails

[via KDE Bugzilla]

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

--- Comment #9 from caulier.gil...@gmail.com ---
Swati,

With your patch, are you able to migrate code without error with Tags table ?

Gilles Caulier

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

[digikam] [Bug 350574] MIGRATION: MySQL to SQLite fails

[via KDE Bugzilla]

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

--- Comment #8 from caulier.gil...@gmail.com ---
Peter,

Do not use 4.x to migrate. Swati currently to fix code relevant in 5.x

Gilles Caulier

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

[kdenlive] [Bug 366144] git master - Project bin doesn't automatically switch to Clip Properties widget when "Clip Properties" option is clicked.

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||http://commits.kde.org/kden
   ||live/71dbf637b09250ad799eb0
   ||57e66bb55505c80426
 Resolution|--- |FIXED

--- Comment #2 from Jean-Baptiste Mardelle  ---
Git commit 71dbf637b09250ad799eb057e66bb55505c80426 by Jean-Baptiste Mardelle.
Committed on 26/07/2016 at 21:53.
Pushed by mardelle into branch 'Applications/16.08'.

Make Clip Properties panel raise even if it was under Project Bin

M  +3-4src/bin/bin.cpp

http://commits.kde.org/kdenlive/71dbf637b09250ad799eb057e66bb55505c80426

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

[kdenlive] [Bug 366144] git master - Project bin doesn't automatically switch to Clip Properties widget when "Clip Properties" option is clicked.

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Jean-Baptiste Mardelle  ---
If the clip properties widget is tabbed under the bin widget, it does not pop
up. This was implemented some time ago because it feels strange to make the
current bin widget "disappear" on double clicking a clip (which does the same
as context menu > Clip Properties).

However with the new behavior, maybe it's better to make the properties dialog
pop up even if it hides the Bin widget... I think you are right, fixing it
right now.

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

[kdenlive] [Bug 366144] git master - Project bin doesn't automatically switch to Clip Properties widget when "Clip Properties" option is clicked.

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

 CC||jesse.dub...@gmail.com

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

[kdenlive] [Bug 366144] New: git master - Project bin doesn't automatically switch to Clip Properties widget when "Clip Properties" option is clicked.

[Jesse via KDE Bugzilla]

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

Bug ID: 366144
   Summary: git master - Project bin doesn't automatically switch
to Clip Properties widget when "Clip Properties"
option is clicked.
   Product: kdenlive
   Version: unspecified
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: jesse.dub...@gmail.com

I think the behavior of the Clip Properties widget is much more congruent with
Kdenlive thanks to a recent commit, but there's a bug - at least I think - in
the new changes: right-clicking on a clip in the Project Bin, then selecting
"Clip Properties" should, I believe, switch the active widget to the Clip
Properties widget, displaying the properties of the corresponding clip.

Reproducible: Always

Steps to Reproduce:
1. Right-click on Video/Image/Sound clip in Project Bin
2. Select "Clip Properties"

Actual Results:  
Nothing happens.

Expected Results:  
Clip Properties widget becomes the active widget, showing the properties of the
corresponding clip selected.

Bug discovered while using Kdenlive git master build via
ppa:kdenlive/kdenlive-master.

Linux Mint 18 x64 (Ubuntu base), Cinnamon 3.0.7 desktop environment.

KDE Frameworks 5.18.0.

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

[dolphin] [Bug 157650] can't navigate by pasting url with middle button or mouse wheel

[Holger via KDE Bugzilla]

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

Holger  changed:

   What|Removed |Added

 CC||h.kl...@gmx.de

--- Comment #17 from Holger  ---
Middle Click on a folder/zip-archiv still opens a new tab, but pasting a
directory-name on middle-click into the white nowhere beyond files does nothing
in dolphin 15.12.3 ... this feature was lost over time?

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

[kmymoney4] [Bug 366043] KMyMoney crashes along with KNotify when searching for transactions

[Rob V via KDE Bugzilla]

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

--- Comment #9 from Rob V  ---
4.8.0 still has the same bug.

Backtrace:

Application: KMyMoney (kmymoney), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x7f715bc036f5 in raise () at /lib64/libc.so.6
#7  0x7f715bc052fa in abort () at /lib64/libc.so.6
#8  0x7f715bc44600 in __libc_message () at /lib64/libc.so.6
#9  0x7f715bc4eb53 in _int_malloc () at /lib64/libc.so.6
#10 0x7f715bc4ff50 in malloc () at /lib64/libc.so.6
#11 0x7f715c54e978 in operator new(unsigned long) () at
/lib64/libstdc++.so.6
#12 0x7f715daf660a in QRegion::QRegion(QRect const&, QRegion::RegionType)
() at /lib64/libQtGui.so.4
#13 0x7f715daa0e86 in QPainter::clipRegion() const () at
/lib64/libQtGui.so.4
#14 0x7f715d9a66c3 in QWidget::render(QPainter*, QPoint const&, QRegion
const&, QFlags) () at /lib64/libQtGui.so.4
#15 0x7f71445f56c8 in Oxygen::TransitionWidget::grabBackground(QPixmap&,
QWidget*, QRect&) const () at /usr/lib64/kde4/plugins/styles/oxygen.so
#16 0x7f71445f4b88 in Oxygen::TransitionWidget::grab(QWidget*, QRect) () at
/usr/lib64/kde4/plugins/styles/oxygen.so
#17 0x7f71445f12a9 in Oxygen::LineEditData::initializeAnimation() () at
/usr/lib64/kde4/plugins/styles/oxygen.so
#18 0x7f71445f0524 in Oxygen::LineEditData::textChanged() () at
/usr/lib64/kde4/plugins/styles/oxygen.so
#19 0x7f715cec3090 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /lib64/libQtCore.so.4
#20 0x7f715dd7cfc2 in QLineEdit::textChanged(QString const&) () at
/lib64/libQtGui.so.4
#21 0x7f715dd7d3f9 in QLineEdit::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () at /lib64/libQtGui.so.4
#22 0x7f715cec3090 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /lib64/libQtCore.so.4
#23 0x7f715dff28d5 in QLineControl::textChanged(QString const&) () at
/lib64/libQtGui.so.4
#24 0x7f715dd814e1 in QLineControl::finishChange(int, bool, bool) () at
/lib64/libQtGui.so.4
#25 0x7f715dd81a7c in QLineControl::internalSetText(QString const&, int,
bool) () at /lib64/libQtGui.so.4
#26 0x7f715e7c049e in KDatePicker::dateChangedSlot(QDate const&) () at
/lib64/libkdeui.so.5
#27 0x7f715cec3090 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /lib64/libQtCore.so.4
#28 0x7f715e7c3542 in KDateTable::dateChanged(QDate const&) () at
/lib64/libkdeui.so.5
#29 0x7f715e7c3662 in KDateTable::setDate(QDate const&) () at
/lib64/libkdeui.so.5
#30 0x7f715e7c0c63 in KDatePicker::selectYearClicked() () at
/lib64/libkdeui.so.5
#31 0x7f715cec3090 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /lib64/libQtCore.so.4
#32 0x7f715dfef692 in QAbstractButton::toggled(bool) () at
/lib64/libQtGui.so.4
#33 0x7f715dd2792e in QAbstractButton::setChecked(bool) () at
/lib64/libQtGui.so.4
#34 0x7f715dd274d3 in QAbstractButtonPrivate::click() () at
/lib64/libQtGui.so.4
#35 0x7f715dd27624 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) ()
at /lib64/libQtGui.so.4
#36 0x7f715ddecb6a in QToolButton::mouseReleaseEvent(QMouseEvent*) () at
/lib64/libQtGui.so.4
#37 0x7f715d9a8720 in QWidget::event(QEvent*) () at /lib64/libQtGui.so.4
#38 0x7f715d951edc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQtGui.so.4
#39 0x7f715d95a557 in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQtGui.so.4
#40 0x7f715e71e64a in KApplication::notify(QObject*, QEvent*) () at
/lib64/libkdeui.so.5
#41 0x7f715ceaeeed in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /lib64/libQtCore.so.4
#42 0x7f715d95857b in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at
/lib64/libQtGui.so.4
#43 0x7f715d9d327d in QETWidget::translateMouseEvent(_XEvent const*) () at
/lib64/libQtGui.so.4
#44 0x7f715d9d19ac in QApplication::x11ProcessEvent(_XEvent*) () at
/lib64/libQtGui.so.4
#45 0x7f715d9fa419 in x11EventSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQtGui.so.4
#46 0x7f7155f80703 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#47 0x7f7155f80ab0 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#48 0x7f7155f80b5c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#49 0x7f715cedf47e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQtCore.so.4
#50 0x7f715d9fa5b6 in
QGuiEventDispatcherGlib::processEvents(QFlags)
() at /lib64/libQtGui.so.4
#51 0x7f715cead7bf in
QEventLoop::processEvents(QFlags) () at
/lib64/libQtCore.so.4
#52 0x7f715ceadb25 in
QEventLoop::exec(QFlags) () at
/lib64/libQtCore.so.4
#53 0x7f715ceb3779 in QCoreApplication::exec() () at /lib64/libQtCore.so.4
#54 0x00627198 in runKMyMoney(KApplication*, KStartupLogo*)
(a=0x2032b20, splash=0x21a3900) at

[neon] [Bug 363851] "A stop job is running for Session 1 of user neon" during shutdown

[via KDE Bugzilla]

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

--- Comment #27 from romulu...@gmail.com ---
I also set KillYUserProcesses=yes and removed comments to see if it really
avoid the waiting, but it did not worked in my case. I'm using Neon in case.

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

[dolphin] [Bug 152574] Create soft links from dolphin context menu

[Holger via KDE Bugzilla]

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

Holger  changed:

   What|Removed |Added

 CC||h.kl...@gmx.de

--- Comment #13 from Holger  ---
My Dolphin 15.12.3 already has such an entry in the New ... submenu

Only thing left: I could not find a keyboard-only shortcut to paste as a
symlink ... but there is always a Konsole on F4 ... so I don't really need one
either :-)

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

[valgrind] [Bug 366035] valgrind misses buffer overflow, segfaults in malloc in localtime

[Philippe Waroquiers via KDE Bugzilla]

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

--- Comment #7 from Philippe Waroquiers  ---
(In reply to Frederick Eaton from comment #6)
> Hi Philippe,
> 
> Thanks for responding.
> 
> I'm using Arch Linux, it's weird that the default Arch package is not
> to your liking. 
The assumption is that valgrind is (basically) build using
   configure/make/make install
and that the resulting executables are not stripped (to ensure a.o. that the
crash stack traces contains symbolic information).
But everybody is free to compile valgrind as they want, this is free software
:).
And of course, then to get some help from Valgrind developers, very likely,
we will prefer to have non stripped executables :).


> Well I compiled from ABS adding (!strip debug) to
> OPTIONS in /etc/makepkg.conf, the new version gives line numbers for
> the backtrace. I attached the new output and also the output with the
> verbose options you recommended.
Thanks. This line/source nr allows to confirm that the valgrind malloc
structure has been 
heavily corrupted.

> In the original version I just called `snd_pcm_hw_params_set_channels`
> and assumed the setting had been honored by ALSA. I requested 1
> channel, ALSA created 2 channels per device constraints, I allocated
> space for 32768 1-channel "frames", ALSA return 32768 2-channel
> frames. I got a buffer overflow. I hope this answers your question. I
> imagine that my original submission was a bit confusing.
Forcing the channel to 1 at that 'BUG' place has other consequences than just
allocating a 'too small' buffer.
As I understand, after this 'forcing to 1', we will also have sfinfo.channels
that will
be 1 instead of 2. No idea if that participates (or not) to the problem.
But what you might do instead of changing channels to 1 is to just allocate a
buffer
with a size equal to frames * 2.
Then we know that the only thing which is 'wrong' is the buffer size.

That being said, assuming the too small buffer is the only cause of this
corruption,
the only 'modify' use of this buffer is likely in the source line:
res = snd_pcm_readi(handle, buffer, frames);
In the detailed trace, we see no matching read system call.
So, I will assume that this snd_pcm_readi is not doing a read syscall but is
rather
an ioctl, probably corresponding to this trace:
SYSCALL[14734,1](16) sys_ioctl ( 4, 0x80184151, 0xffefff170 ) --> [async] ... 
SYSCALL[14734,1](16) ... [async] --> Success(0x0) 

I am not sure how to translate this 0x80184151 into one of the 'symbolic' ioctl
SND/PCM things handled in syswrap-linux.c.
I suspect that some SND/PCM ioctl are not properly described  as
reading/writing the memory
pointed to by the ARG3 of the ioctl. Then of course, that might do a buffer
overrun
which is undetected by Valgrind, which then corrupts the end of the buffer
block
and the malloc data structure/memory/blocks following this (too small) buffer.

So, at this point, what we need to confirm is:
  is snd_pcm_readi really doing an ioctl ?
  if yes, which one ? (i.e. which 'symbolic' ioctl is it doing ?)
e.g. maybe it is  case VKI_SOUND_PCM_READ_CHANNELS:
and if this is the case, then syswrap-linux.c describes that this ioctl is
writing the
size of an int, while it clearly reads more than an int, if the ioctl is
reading real data.
 If now that is the bug, and syswrap-linux.c really should describe that it
reads a bunch
 of bytes depending on previously set parameters, then I think that is a lot of
work to do,
 as basically syswrap-linux.c will need to record the previous SND/PCM ioctl to
know what
 is the expected size of such an ioctl ARG3.

 Now, maybe this ioctl is rather something like VKI_SNDRV_CTL_IOCTL_TLV_READ
 but I do not see how that matches this buffer logic and the snd_pcm_readi,
which only
  has a buffer argument.

So, to understand where the undetected buffer overflow comes from, I guess some
alsa/snd lib source code reading might be needed, to see how snd_pcm_readi is
implemented
in terms of ioctl.
We can then check if syswrap-linux.c properly describes what this ioctl is
accessing
in read and/or write mode.

Hoping this helps 

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

[konsole] [Bug 366143] Gray color is not visible in 'solarized' theme

[Simon Huerlimann via KDE Bugzilla]

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

--- Comment #1 from Simon Huerlimann  ---
Created attachment 100321
  --> https://bugs.kde.org/attachment.cgi?id=100321=edit
Non-visible Text in solarized

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

[neon] [Bug 363851] "A stop job is running for Session 1 of user neon" during shutdown

[via KDE Bugzilla]

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

romulu...@gmail.com changed:

   What|Removed |Added

 CC||romulu...@gmail.com

--- Comment #26 from romulu...@gmail.com ---
I suspect it can be responsible by some inconsistencies on multi-screens setups
as save session in my experience, has correctly managed my panels position and
screen configuration... When it gracefully shut down

Otherwise I get a plethora of strange comportment, monitor position resetting,
panels arrangement reorganizing around default screen, etc. But I'm not sure of
this.

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

[skrooge] [Bug 366025] Skrooge perpetually asks me to save updated tab state

[Stephane MANKOWSKI via KDE Bugzilla]

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

--- Comment #6 from Stephane MANKOWSKI  ---
Hi,

I am not able to reproduce the issue with your file.
In settings, options are well on "Never", so there is no panel asking to save
the state.

Could you launch the following command and confirm that you have only one file
found?
find ~/ -name skroogerc

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

[konsole] [Bug 366143] Gray color is not visible in 'solarized' theme

[Simon Huerlimann via KDE Bugzilla]

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

--- Comment #2 from Simon Huerlimann  ---
Created attachment 100322
  --> https://bugs.kde.org/attachment.cgi?id=100322=edit
Visible Text in solarized light

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

[kde] [Bug 59818] Assigning scripts to folders ("Watched folders")

[Holger via KDE Bugzilla]

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

Holger  changed:

   What|Removed |Added

 CC||h.kl...@gmx.de

--- Comment #4 from Holger  ---
There's a related bug 163079 focusing on file conversion actions, overlapping
with this as a special case of general script execution.

I wonder, if this is really a useful feature to integrate into dolphin. Maybe a
standalone demon can watch certain folders and run scripts. The configuration
and writing those scripts certainly requires a plethora of options and IMHO
necessitates a new application.

It's like saying: "I want AutoKey-features in the keyboard-layout switcher ..."
just because both applications happen to be related to keyboard input.

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

[konsole] [Bug 366143] New: Gray color is not visible in 'solarized' theme

[Simon Huerlimann via KDE Bugzilla]

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

Bug ID: 366143
   Summary: Gray color is not visible in 'solarized' theme
   Product: konsole
   Version: unspecified
  Platform: Kubuntu Packages
   URL: https://github.com/mattbrictson/airbrussh/issues/84
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: simon.huerlim...@huerlisi.ch

When using the 'solarized' theme, text output that uses the ANSI escapes for
gray is not visible. it seems to use the same color as the background color.

It is okay with all other themes, including 'solarized light'.

It seem to be the same on "'Solarized' Color Scheme on Ubuntu Gnome 16.04" so
the issue might be in some share upstream code.

Please see https://github.com/mattbrictson/airbrussh/issues/84 for some
screenshots and more information.

Reproducible: Always

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

[kmymoney4] [Bug 366043] KMyMoney crashes along with KNotify when searching for transactions

[Rob V via KDE Bugzilla]

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

--- Comment #8 from Rob V  ---
The KMyMoney crash does occur with all date picker widgets, not just the Find
Transaction one.

Regenerating the VLC plugin cache worked to sort of fix the KNotify crash
(KNotify no longer crashes, and a sound of some description is now emitted, a
very garbled version of the usual dialog box sound). It's clear that the two
crashes are completely unrelated (KMyMoney still crashes even now that KNotify
is fixed), but initially I thought there may have been a chance they were
related.

Clearing the pixmap cache, however, made no difference to KMyMoney's crash on
entering a year into the date picker widget. I'll try updating to 4.8.0 in case
that fixes things.

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

[valgrind] [Bug 366142] New: Illegal opcode _mm_maskload_ps

[Marios Hadjieleftheriou via KDE Bugzilla]

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

Bug ID: 366142
   Summary: Illegal opcode _mm_maskload_ps
   Product: valgrind
   Version: 3.10.0
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: callgrind
  Assignee: josef.weidendor...@gmx.de
  Reporter: mha...@gmail.com

I am trying to profile a program compiled with gcc using -mavx, and including
immintrin.h. I get the following error:
==5880== Process terminating with default action of signal 4 (SIGILL)
==5880==  Illegal opcode at address 0x43AA5E
==5880==at 0x43AA5E: ... (avxintrin.h:928)

Looking at avxintrin.h line 928, I see this instruction:
927 extern __inline __m128 __attribute__((__gnu_inline__, __always_inline__,
__artificial__))
 928 _mm_maskload_ps (float const *__P, __m128i __M)
 929 {
 930   return (__m128) __builtin_ia32_maskloadps ((const __v4sf *)__P,
 931  (__v4si)__M);
 932 }



Reproducible: Always

Steps to Reproduce:
1. Run any executable that uses _mm_maskload_ps

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

[dolphin] [Bug 236606] wish context menu entry "open with" in folder-view (on left)

[Holger via KDE Bugzilla]

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

Holger  changed:

   What|Removed |Added

 CC||h.kl...@gmx.de

--- Comment #5 from Holger  ---
superseded by bug 295575

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

[kate] [Bug 366141] Search and Replace regression after upgrade from KDE-4 to Plasma-5

[Sergey via KDE Bugzilla]

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

--- Comment #5 from Sergey  ---
Video how did it look like before:
https://www.youtube.com/watch?v=7kDLd7bYJkA
It was easy there to type CTRL+F, to find smth, then to click on small green
button on the right and after click on this small button "down arrow" (instead
of big and UGLY "Search and Replace" button in new Kate and Plasma-5) there was
Replace field which appeared right after clicking on this small nice button.
There were no 2 fields with "Find". And "Replace" filed was easily removable
too. As well as "Search and replace dialog" was also easy removable too.
Please, move changes back as it was. Current version is unworkable at all.

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

[digikam] [Bug 325655] MIGRATION : after MySQL to Sqlite database conversion, random tags are assigned to new images

[Thomas Bleher via KDE Bugzilla]

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

--- Comment #6 from Thomas Bleher  ---
So I have long ago switched to sqlite and have no intention of setting up MySQL
just to recheck that bug. If you think the bug should no longer happen, it is
OK for me if you just close it.

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

[kate] [Bug 366141] Search and Replace regression after upgrade from KDE-4 to Plasma-5

[Sergey via KDE Bugzilla]

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

--- Comment #4 from Sergey  ---
Suggstion is to leave the same behaviour as it was in KDE-4 in some of the
previous versions of either kate or its plugin. Current behaviour is
REGRESSION. There were no problems in that respect before upgrade to glitchy
Plasm-5 (with a pile of bugs and regressions).

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

[digikam] [Bug 339607] MYSQL : Images not show if corresponding ImageInformation entry does not exist in database

[via KDE Bugzilla]

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

--- Comment #8 from swatilodh...@gmail.com ---
Created attachment 100320
  --> https://bugs.kde.org/attachment.cgi?id=100320=edit
Patch to fix this issue.

I've changed INNER JOIN to LEFT JOIN at several places in the source code to
ensure that images are visible in UI, even if entry is removed from Image
Information table.

Please test and provide feedback.

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

[digikam] [Bug 339607] MYSQL : Images not show if corresponding ImageInformation entry does not exist in database

[via KDE Bugzilla]

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

--- Comment #7 from swatilodh...@gmail.com ---
MySQL and SQLite return the same results. Both do not show images if the entry
for that image id is removed from Image Information table.

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

[plasmashell] [Bug 361915] plasma5, Folder menu does not have hot key letter selectors.

[Nicolas L . via KDE Bugzilla]

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

Nicolas L.  changed:

   What|Removed |Added

 CC||k...@nicolaslecureuil.fr

--- Comment #4 from Nicolas L.  ---
any news on this bugreport ? It is still valid on plasma 5.7.2 for the reporter

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

[kde] [Bug 253547] Regression: since 4.5.2, KDE downloads multimedia files instead of letting applications stream them

[Dmitry via KDE Bugzilla]

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

Dmitry  changed:

   What|Removed |Added

 CC||nrn...@gmail.com

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

[kate] [Bug 366141] Search and Replace regression after upgrade from KDE-4 to Plasma-5

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

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

--- Comment #3 from Dominik Haumann  ---
That is not true, it was exactly the same in KDE 4. Granted, it is confusing to
have two search lines at the same time, but that's since the one is from the
editor, and the other one from the plugin... Suggestions for improvements are
welcome, even more so patches.

All in all, the described issue is not a bug, therefore, will close for now,
sorry.

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

[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU

[via KDE Bugzilla]

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

--- Comment #146 from white...@gmail.com ---
I installed the debug version of qt-declarative but still no backtrace.
Which of the packages at the following link could be the correct one in your
opinion?

https://github.com/The-Compiler/qt-debug-pkgbuild

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

[kdenlive] [Bug 361976] git master (re-opened) - Playback of certain video files produces large distortion artifacts (video example & sample footage included)

[Jesse via KDE Bugzilla]

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

--- Comment #8 from Jesse  ---
I'm still doing some testing to see if the clips still have the
artifacts/distortions with a lower bit-rate when Blender is rendering. Will
post more soon.

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

[kdenlive] [Bug 366017] mp4 audio bitrate gets set to 64 after selecting render profile

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kden
   ||live/ff1787c962b99ad933715d
   ||24d3d7419d912a0105
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Jean-Baptiste Mardelle  ---
Git commit ff1787c962b99ad933715d24d3d7419d912a0105 by Jean-Baptiste Mardelle.
Committed on 26/07/2016 at 19:40.
Pushed by mardelle into branch 'Applications/16.08'.

Fix render bitrates incorrectly set when selecting another profile

M  +5-0src/dialogs/renderwidget.cpp

http://commits.kde.org/kdenlive/ff1787c962b99ad933715d24d3d7419d912a0105

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

[kdenlive] [Bug 365955] crash if I insert a track

[Wegwerf via KDE Bugzilla]

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

--- Comment #9 from Wegwerf  ---
Stable version is 16.04.3, see here:
https://launchpad.net/~kdenlive/+archive/ubuntu/kdenlive-stable

I'm wondering how you got the development version at all, yet don't know about
the stable repositories...? Which specific Ubuntu repo are you using that
contains an unstable development version??

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

[kdenlive] [Bug 364891] title clip rendering is broken in mlt-6.2

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #4 from Wegwerf  ---
Nikita, can you please be so kind as to close this bug if the answer works for
you? Thank you very much for you cooperation!

If you like to see what's upcoming, that is, the improved easy of use
Jean-Baptiste is talking about:
*
http://thediveo-e.blogspot.de/2016/07/new-kdenlive-transition-composite-and.html
* http://thediveo-e.blogspot.de/2016/07/kdenlive-easy-compositing-with.html

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

[dolphin] [Bug 171743] Shortcut for moving between parts in Split View

[Holger via KDE Bugzilla]

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

Holger  changed:

   What|Removed |Added

 CC||h.kl...@gmx.de

--- Comment #35 from Holger  ---
Another duplicate in bug 366050 ...

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

[kdenlive] [Bug 366119] git master: only subset of scalable icons installed

[Wegwerf via KDE Bugzilla]

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

--- Comment #1 from Wegwerf  ---
More research shows that the system-wide breeze icons seem to take precedence,
when they are of a better size match than their locally installed generally
scalable cousins. Looks as if we need to more carefully install icons
locally...

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

[kdenlive] [Bug 366103] git master - consider improving behavior of how Project Bin handles Clip Properties widget (video included)

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kden
   ||live/9abdc258d59b1a2f720b7c
   ||0fbf8db35b15783e66
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Jean-Baptiste Mardelle  ---
Git commit 9abdc258d59b1a2f720b7c0fbf8db35b15783e66 by Jean-Baptiste Mardelle.
Committed on 26/07/2016 at 19:08.
Pushed by mardelle into branch 'Applications/16.08'.

Remove strange behavior clip properties icon in bin toolbar, make clip
properties widget behave like any other

M  +10   -18   src/bin/bin.cpp
M  +2-2src/bin/bin.h
M  +2-3src/mainwindow.cpp
M  +7-7src/mltcontroller/clippropertiescontroller.cpp

http://commits.kde.org/kdenlive/9abdc258d59b1a2f720b7c0fbf8db35b15783e66

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

[kate] [Bug 366141] Search and Replace regression after upgrade from KDE-4 to Plasma-5

[Sergey via KDE Bugzilla]

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

--- Comment #2 from Sergey  ---
Created attachment 100319
  --> https://bugs.kde.org/attachment.cgi?id=100319=edit
Screenshot005

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

[kate] [Bug 366141] Search and Replace regression after upgrade from KDE-4 to Plasma-5

[Sergey via KDE Bugzilla]

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

Sergey  changed:

   What|Removed |Added

 CC||energumenos...@gmail.com

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

[kate] [Bug 366141] Search and Replace regression after upgrade from KDE-4 to Plasma-5

[Sergey via KDE Bugzilla]

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

--- Comment #1 from Sergey  ---
Created attachment 100318
  --> https://bugs.kde.org/attachment.cgi?id=100318=edit
Screenshot004

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

[kate] [Bug 366141] New: Search and Replace regression after upgrade from KDE-4 to Plasma-5

[Sergey via KDE Bugzilla]

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

Bug ID: 366141
   Summary: Search and Replace regression after upgrade from KDE-4
to Plasma-5
   Product: kate
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: energumenos...@gmail.com

First of all, I don't like redesign of Kate and changes in Find and Replace
button placement/behaviour. But it also became buggy. Search smth with CTRL+F
in Kate (See screenshot004.png), input some text to find, then click on button
"Search and Replace". And surprise! You'll have to input text again! See
screenshot005 below. There were no such bugs in Kate in KDE:4 and there was
better overall design too.

Reproducible: Always

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

[dolphin] [Bug 366050] There is no keyboard shortcut to switch between panes and tabs

[Holger via KDE Bugzilla]

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

Holger  changed:

   What|Removed |Added

 CC||h.kl...@gmx.de

--- Comment #1 from Holger  ---
Ctrl+[1..3] is already taken to toggle between preview icons, list- and
tree-view
Tab and Ctrl-Tab should work to some extent ... only you can't tab out of a F4
Konsole, as tab is used for completion.

I suggest F6 to toggle between left and right side. Especially the selection
per side has to be preserved, which is a pain in the ass when activating the
inactive side with a mouse-click. To edit the location, there is still the
widely known Ctrl+L in place as a redundant fallback.

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

[digikam] [Bug 312054] Cannot add a collection on the network in Gnome-based environment

[Tobias Puetz via KDE Bugzilla]

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

Tobias Puetz  changed:

   What|Removed |Added

 CC||puetz-tob...@web.de

--- Comment #19 from Tobias Puetz  ---
Hi,
I am having a Gnome environment as well on Fedora 24. 
It seem to be different if you use a samba share in Gnome or KDE.

I have got a work around which let me use a samba share for my Database and my
photos.

Install with your favorite software package program a KDE package called "
Smb4k"
You can use this to create a network shortcut in
"/home/YourUserName/smb4k/YourSambaShare/..." this path you can copy and paste
into your digikam database location field.
cheers
Tobs

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

[kdenlive] [Bug 361360] git master (re-opened) - playback speed/framerate slows WAY down when using video clips in multiple tracks in timeline (video example included)

[Jesse via KDE Bugzilla]

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

--- Comment #47 from Jesse  ---
No doubt! Definitely getting better and better with each release. :) Thanks for
the dev' support and open collaboration JB.

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

[Akonadi] [Bug 365991] Starting Kontact/Kmail causes crash. Command line shows - akonadicore_log: Failed SpecialCollectionsRequestJob::slotResult "Failed to fetch the resource collection."

[Pip via KDE Bugzilla]

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

--- Comment #5 from Pip  ---
Kontact will start if akonadiconnectionrc has the UnixPath entry removed. But
then it won't do anything as it can't connect to the akonadi service. As far as
I can figure it.

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

[digikam] [Bug 350574] MIGRATION: MySQL to SQLite fails

[via KDE Bugzilla]

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

--- Comment #7 from swatilodh...@gmail.com ---
Created attachment 100317
  --> https://bugs.kde.org/attachment.cgi?id=100317=edit
To migrate from MySQL to SQLite

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

[kdenlive] [Bug 361360] git master (re-opened) - playback speed/framerate slows WAY down when using video clips in multiple tracks in timeline (video example included)

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #46 from Jean-Baptiste Mardelle  ---
Thanks Jesse for the feedback. For sure we all want to be able to composite 6
tracks in high quality without any drop in framerate. But for Kdenlive's 16.08
release I will not do any further changes, it's too late in the release cycle.
But for sure there is definitely room for improvement.

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

[kdenlive] [Bug 366069] Keyboard commands ALT+ and ALT+ get stuck on Guides

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #1 from Jean-Baptiste Mardelle  ---
I never experienced this issue. Please let me know if you find a way to
reproduce.

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

[plasmashell] [Bug 366140] Date is to the left of the Time on Digital Clock instead of under it, font is too big too

[Sergey via KDE Bugzilla]

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

Sergey  changed:

   What|Removed |Added

 CC||energumenos...@gmail.com

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

[plasmashell] [Bug 366140] Date is to the left of the Time on Digital Clock instead of under it, font is too big too

[Sergey via KDE Bugzilla]

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

--- Comment #2 from Sergey  ---
Created attachment 100316
  --> https://bugs.kde.org/attachment.cgi?id=100316=edit
Screenshot02

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

[plasmashell] [Bug 366140] Date is to the left of the Time on Digital Clock instead of under it, font is too big too

[Sergey via KDE Bugzilla]

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

--- Comment #1 from Sergey  ---
Created attachment 100315
  --> https://bugs.kde.org/attachment.cgi?id=100315=edit
Screenshot01

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

[kio] [Bug 350884] Dolphin doesn't generate (or cannot access?) thumbnails for new .jpgs

[Holger via KDE Bugzilla]

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

Holger  changed:

   What|Removed |Added

 CC||h.kl...@gmx.de

--- Comment #7 from Holger  ---
Previews are stored in ~/.thumbnails ... maybe, there is something wrong in
this folder? You could try to rename it to ~/.thumbnails.old and navigate to
you're pictures and press F5 to see, if the thumbnails are shown with a freshly
created folderstructure in ~/.thumbnails.

Just guessing ...

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

[plasmashell] [Bug 315488] icon-only task manager groups chrome/chromium web apps with chrome/chromium

[Kilian via KDE Bugzilla]

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

Kilian  changed:

   What|Removed |Added

 CC|kilian.lackh...@gmail.com   |

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

[plasmashell] [Bug 315488] icon-only task manager groups chrome/chromium web apps with chrome/chromium

[Sudhir Khanger via KDE Bugzilla]

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

--- Comment #35 from Sudhir Khanger  ---
Thank you Eike. That's awesome.

Is there a global setting to enable it for all apps?

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