[akregator] [Bug 373018] New: When filtering for „new“ article all are marked as read

[Jonathan Kolberg]

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

Bug ID: 373018
   Summary: When filtering for „new“ article all are marked as
read
   Product: akregator
   Version: GIT (master)
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: j_kolber...@cs.uni-kl.de
  Target Milestone: ---

Steps to reproduce:
1. Open Akregator
2. Go to a folder which contains some unread articles
3. Set the filter to 'Unread'

Actuall behaviour:
All unread articles are marked as read

Expected behaviour:
Shows a list of unread articles allowing to read them one by one.

Related bugs:
Seems to be a regression that happend before (see #271640 )

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

[kdenlive] [Bug 372995] unable to exit full sceen in kdenlive

[Colin]

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

--- Comment #8 from Colin  ---
Yes still unsolved but appears to be to do with cinnamon rather than
kdenlive

Colin

On 27 Nov 2016 23:28, "farid"  wrote:

> https://bugs.kde.org/show_bug.cgi?id=372995
>
> farid  changed:
>
>What|Removed |Added
> 
> 
>  CC||snd.no...@gmail.com
>
> --- Comment #7 from farid  ---
> Hi Colin,
>
> Can we close this report?
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[kate] [Bug 372950] Fortran syntax highlighting: distinguish free format and fixed format

[bugzilla_noreply]

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

--- Comment #2 from ja...@gcc.gnu.org ---
Submitted for review here:

https://git.reviewboard.kde.org/r/129569/

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

[frameworks-kdeclarative] [Bug 368701] Missing touch event support in MouseEventListener

[Eike Hein]

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

Eike Hein  changed:

   What|Removed |Added

 CC||doublejiniti...@gmail.com

--- Comment #4 from Eike Hein  ---
*** Bug 373010 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 373010] Folder View does not accept touchscreen input

[Eike Hein]

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

Eike Hein  changed:

   What|Removed |Added

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

--- Comment #1 from Eike Hein  ---


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

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

[kdevelop] [Bug 373017] Background parser memory on large project

[bugzilla_noreply]

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

gnu...@gmail.com changed:

   What|Removed |Added

 CC||gnu...@gmail.com

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

[kdevelop] [Bug 373017] New: Background parser memory on large project

[bugzilla_noreply]

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

Bug ID: 373017
   Summary: Background parser memory on large project
   Product: kdevelop
   Version: 5.0.2
  Platform: Appimage
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: code completion
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: gnu...@gmail.com
  Target Milestone: ---

Hi,

First of all thank you very much for this nice piece of SW.

I'm using it on a rather large project about 2mio LOC consisting of
C/C++/QML/Python/CMake and expecting big troubles with the background parser.

My project consists of about 30 sub-projects which are all loaded in a single
session.

If I use background parsing of source KDevelop-5.0.2-1 starts to fill up my
memory (16GB + 16GB Swap) within a few minutes when I use 8 background threads.
When I just use 1 it would take a few minutes longer to eat my memory.

Turning off background parsing, solves the problem for me currently (just very
small leakage), but I really love (and need) the benefits the background
parsing gives me... At least for such a large project.

Thanks in advance and keep up the good work!

Best,
 gnux

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

[plasmashell] [Bug 371991] Multi monitor setup crash in Plasma 5.8.3

[bugzilla_noreply]

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

lester.elli...@gmail.com changed:

   What|Removed |Added

 CC||lester.elli...@gmail.com

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

[konsole] [Bug 373016] New: Konsole Crash when opening menu

[JohnApple]

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

Bug ID: 373016
   Summary: Konsole Crash when opening menu
   Product: konsole
   Version: 16.08.2
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: joap...@au1.ibm.com
  Target Milestone: ---

Application: konsole (16.08.2)

Qt Version: 5.6.1
Frameworks Version: 5.27.0
Operating System: Linux 4.8.8-200.fc24.x86_64 x86_64
Distribution: "Fedora release 24 (Twenty Four)"

-- Information about the crash:
- What I was doing when the application crashed:
//If this is important: I am using the Solarized-dark colorscheme, and the
default Breeze dark-theme for KDE//
Open multiple Konsole windows open, across 2 activities
Switch to the virtual desktop to close it
Move mouse up to menu bar to attempt to work with the application
All Konsole windows die with the error reported here

This has happened 3 times to me in the past month, but I usually have no issue

The crash can be reproduced sometimes.

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f66480c4940 (LWP 4481))]

Thread 3 (Thread 0x7f663cfcc700 (LWP 4484)):
#0  0x7f66564bb56d in poll () at /lib64/libc.so.6
#1  0x7f66526efa06 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f66526efb1c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f66572c124b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f66572705ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f66570cf343 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f665c3f8559 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#7  0x7f66570d399a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f6654e8c5ca in start_thread () at /lib64/libpthread.so.0
#9  0x7f66564c70ed in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f663e912700 (LWP 4483)):
#0  0x7f66564bb56d in poll () at /lib64/libc.so.6
#1  0x7f6653f78f80 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7f6653f7ab79 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7f664165dda9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7f66570d399a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7f6654e8c5ca in start_thread () at /lib64/libpthread.so.0
#6  0x7f66564c70ed in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f66480c4940 (LWP 4481)):
[KCrash Handler]
#6  0x7f66572a1481 in QObject::~QObject() () at /lib64/libQt5Core.so.5
#7  0x7f6657d942d9 in QActionGroup::~QActionGroup() () at
/lib64/libQt5Widgets.so.5
#8  0x7f6658c42900 in KSelectAction::~KSelectAction() () at
/lib64/libKF5WidgetsAddons.so.5
#9  0x7f6658c42a39 in KSelectAction::~KSelectAction() () at
/lib64/libKF5WidgetsAddons.so.5
#10 0x7f66572a04fc in QObjectPrivate::deleteChildren() () at
/lib64/libQt5Core.so.5
#11 0x7f66572a15ff in QObject::~QObject() () at /lib64/libQt5Core.so.5
#12 0x7f6657d905b9 in QAction::~QAction() () at /lib64/libQt5Widgets.so.5
#13 0x7f6657de2d8d in QWidgetAction::~QWidgetAction() () at
/lib64/libQt5Widgets.so.5
#14 0x7f6658c42921 in KSelectAction::~KSelectAction() () at
/lib64/libKF5WidgetsAddons.so.5
#15 0x7f665a5d4ee9 in KCodecAction::~KCodecAction() () at
/lib64/libKF5ConfigWidgets.so.5
#16 0x7f66572a04fc in QObjectPrivate::deleteChildren() () at
/lib64/libQt5Core.so.5
#17 0x7f66572a15ff in QObject::~QObject() () at /lib64/libQt5Core.so.5
#18 0x7f665be61e89 in Konsole::SessionController::~SessionController() ()
at /lib64/libkonsoleprivate.so.16
#19 0x7f665be61ec9 in Konsole::SessionController::~SessionController() ()
at /lib64/libkonsoleprivate.so.16
#20 0x7f665729ac10 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#21 0x7f6657d99c0c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#22 0x7f6657d9f0ef in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQt5Widgets.so.5
#23 0x7f66572717aa in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#24 0x7f665727384f in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /lib64/libQt5Core.so.5
#25 0x7f66572c11b3 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQt5Core.so.5
#26 0x7f66526ef6ba in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#27 0x7f66526efa70 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#28 0x7f66526efb1c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#29 0x7f66572c122f in
QEventDispatcherGlib::processEvents(QFlags) ()
at 

[dolphin] [Bug 373015] New: With many files selected, viewer is late to start

[Tracy]

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

Bug ID: 373015
   Summary: With many files selected, viewer is late to start
   Product: dolphin
   Version: 16.08.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: j90...@yahoo.com
  Target Milestone: ---

Sometimes there are many jpeg files in a folder, let us say, thousands.

I start Dolphin and select many of them to view in a photo viewer, let us say,
500 photos. The selection's background changes color. Then I right-click,
select "Open with", select "Gwenview" or other viewer.

Do you think the Gwenview starts?

Instead of the viewer starting and showing me the first picture, a very
intensive disk activity begins. For 500 photos, it lasts 30 seconds. For
thousands of photos, it takes minutes! Likely, during this time thumbnailing or
caching is occurring.

Then only the viewer starts and from there on works correctly. 

Besides, there is a few seconds delay after the right click, before the popup
dialog to select the viewer appears.

It wasn't so a year ago or so, with earlier versions of openSUSE. The viewer
there was beginning to show the first image immediately.


The user shall have some control over thumbnailing or caching. I don't want to
wait for minutes until an activity that I don't need is finished. The
thumbnailng or caching can occur during viewing of the first few photos, or
shall be disable-able. I haven't seen any hard drive activity more intense than
this; I am worried about the disk. 

My home holder is on a mechanical hard drive. The OS and swap are on a SSD. The
viewer's starting is different when it is started from command line: gwenview
my_pattern*.jpg

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

[digikam] [Bug 372093] corrupts image file when crashing

[bugzilla_noreply]

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

--- Comment #7 from caulier.gil...@gmail.com ---
No.

Please use the AppImage Bundle for Linux and forget DK from your system, as i
said in comment #4.

The AppImage do not install anything and have the last libraries mandatory for
DK embedded inside. For ex, Exiv2 is 0.26-rc...

Gilles Caulier

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

[digikam] [Bug 360955] digikam - EXIF caption no longer copied to captions area

[bugzilla_noreply]

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

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

   What|Removed |Added

Version|5.0.0   |5.4.0

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

[plasmashell] [Bug 373014] New: Plasmashell crashed

[bugzilla_noreply]

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

Bug ID: 373014
   Summary: Plasmashell crashed
   Product: plasmashell
   Version: 5.8.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: h...@bahnhof.se
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.4)

Qt Version: 5.7.0
Frameworks Version: 5.28.0
Operating System: Linux 4.8.10-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
Changing entries's visibility in system tray settings

The crash does not seem to be reproducible.

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

Thread 18 (Thread 0x7f493cb69700 (LWP 28876)):
#0  0x7f4a1771148d in poll () at /usr/lib/libc.so.6
#1  0x7f4a129d9786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f4a129d989c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f4a1803372b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f4a17fdd23a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f4a17e000f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f4a1b1632d5 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f4a17e04d78 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f4a16f14454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f4a1771a7df in clone () at /usr/lib/libc.so.6

Thread 17 (Thread 0x7f493dffb700 (LWP 18840)):
#0  0x7f4a16f1a10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f4a17e05c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f49619111c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f4961915988 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f4961910263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f49619159e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f4961910263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f49619131f9 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f4a17e04d78 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f4a16f14454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f4a1771a7df in clone () at /usr/lib/libc.so.6

Thread 16 (Thread 0x7f493e7fc700 (LWP 18839)):
#0  0x7f4a16f1a10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f4a17e05c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f49619111c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f4961915988 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f4961910263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f49619159e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f4961910263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f49619131f9 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f4a17e04d78 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f4a16f14454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f4a1771a7df in clone () at /usr/lib/libc.so.6

Thread 15 (Thread 0x7f493effd700 (LWP 18838)):
#0  0x7f4a16f1a10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f4a17e05c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f49619111c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f4961915988 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f4961910263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f49619159e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f4961910263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f49619159e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f4961910263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#9  0x7f49619159e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#10 0x7f4961910263 

[frameworks-knewstuff] [Bug 365777] add-on installer will not load

[Tim leonard]

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

Tim leonard  changed:

   What|Removed |Added

 CC||maggieti...@gmail.com

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

[frameworks-knotifications] [Bug 348414] Crash in KNotification::flags() (NotifyByAudio::onAudioFinished)

[awilfox]

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

--- Comment #67 from A. Wilcox (awilfox)  ---
After months of not having this error, I have just hit it again closing an
unsaved file in KWrite:

Thread 1 (Thread 0x7fde50bba780 (LWP 6985)):
[KCrash Handler]
#6  0x7fde3ef727b4 in KNotification::flags (this=0x371f6e0) at
/var/tmp/portage/kde-frameworks/knotifications-5.26.0/work/knotifications-5.26.0/src/knotification.cpp:233
#7  0x7fde3ef90cc8 in NotifyByAudio::onAudioFinished (this=0x2fa3d90) at
/var/tmp/portage/kde-frameworks/knotifications-5.26.0/work/knotifications-5.26.0/src/notifybyaudio.cpp:147
#8  0x7fde4dd19e50 in QMetaObject::activate (sender=0x30261a0,
signalOffset=, local_signal_index=,
argv=) at kernel/qobject.cpp:3730
#9  0x7fde4dd1336f in QObject::event (this=0x30261a0, e=) at
kernel/qobject.cpp:1256
#10 0x7fde4e582792 in QApplicationPrivate::notify_helper (this=, receiver=0x30261a0, e=0x3667800) at kernel/qapplication.cpp:3804
#11 0x7fde4e5845c2 in QApplication::notify (this=,
receiver=0x30261a0, e=0x3667800) at kernel/qapplication.cpp:3163
#12 0x7fde4dceb73b in QCoreApplication::notifyInternal2
(receiver=0x30261a0, event=0x3667800) at kernel/qcoreapplication.cpp:1015
#13 0x7fde4dcec2f8 in QCoreApplication::sendEvent (receiver=0x30261a0,
event=0x3667800) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:225
#14 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0,
data=0x241b610) at kernel/qcoreapplication.cpp:1650
#15 0x7fde4dd395a3 in postEventSourceDispatch (s=0x247e490) at
kernel/qeventdispatcher_glib.cpp:270
#16 0x7fde48790dcd in g_main_dispatch (context=) at
/var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3154
#17 g_main_context_dispatch (context=) at
/var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3769
#18 0x7fde487910f9 in g_main_context_iterate (context=,
block=, dispatch=, self=) at
/var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3840
#19 0x7fde4879117e in g_main_context_iteration (context=,
may_block=1) at
/var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3901
#20 0x7fde4dd390fc in QEventDispatcherGlib::processEvents (this=0x2484df0,
flags=...) at kernel/qeventdispatcher_glib.cpp:417
#21 0x7fde4dce8001 in QEventLoop::processEvents (flags=..., this=) at kernel/qeventloop.cpp:128
#22 QEventLoop::exec (this=0x7ffe4dfe1b30, flags=...) at
kernel/qeventloop.cpp:204
#23 0x7fde4dcebd63 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1285
#24 0x00410460 in main (argc=, argv=) at
/var/tmp/portage/kde-apps/kwrite-16.08.1/work/kate-16.08.1/kwrite/main.cpp:284

As noted in the backtrace I am still on KF 5.26.  I will upgrade to 5.28 and
see if this persists.  Oddly I have been on 5.26 since 22 September with no
crash until now.  uptime(1) shows only 10 days 2 hours 41 minutes, so it
doesn't look related to that either.  Just random.

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

[bugzilla_noreply]

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

--- Comment #208 from abrah...@acm.org ---
(In reply to David Rankin from comment #207)
David said it perfectly.

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

[valgrind] [Bug 352395] Please provide SVN revision info in --version

[Austin English]

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

--- Comment #22 from Austin English  ---
(In reply to Ivo Raisr from comment #20)
> Patch #6 seems to be working well. I tested it on Solaris, inside SVN tree,
> outside and after 'make dist'.
> 
> In addition to the last comment by Austin, please change also:
> 
> auxprogs/make_or_upd_vgversion_h:
> -   when using command lines options:  -v --version 
> +   when using command line options:  -v --version 
> 
> and make sure that auxprogs/make_or_upd_vgversion_h is marked as executable
> in SVN repository.

Yeah, it fails for me out of the box, with:
echo "# This is a generated file, composed of the following suppression rules:"
> default.supp
auxprogs/make_or_upd_vgversion_h
make: execvp: auxprogs/make_or_upd_vgversion_h: Permission denied
Makefile:1374: recipe for target 'vgversion.h' failed
make: *** [vgversion.h] Error 127
make: *** Waiting for unfinished jobs
echo "# " exp-sgcheck.supp xfree-3.supp xfree-4.supp glibc-2.X-drd.supp
glibc-2.34567-NPTL-helgrind.supp glibc-2.X.supp  >> default.supp
cat exp-sgcheck.supp xfree-3.supp xfree-4.supp glibc-2.X-drd.supp
glibc-2.34567-NPTL-helgrind.supp glibc-2.X.supp >> default.supp

chmod +x auxprogs/make_or_upd_vgversion_h gets past that problem.

Next, it fails for VEX, with git svn:
valgrind-3.12.0.SVN-16107-vex-

+git svn info $1 | grep '^Revision' | cut -d ' ' -f2 | tr -d '\n'

won't work the way you expect. It needs to be in the VEX directory for this to
work:
austin@austin2:~/src/valgrind-git$ git svn info | grep Revision
Revision: 16107

austin@austin2:~/src/valgrind-git$ git svn info VEX | grep Revision
svn: 'VEX' is not under version control

austin@austin2:~/src/valgrind-git$ cd VEX && git svn info | grep Revision
Revision: 3276

FYI, I can also text on OSX (once these issues are sorted out ;) ).

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

[digikam] [Bug 360955] digikam - EXIF caption no longer copied to captions area

[Knut Hildebrandt]

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

--- Comment #3 from Knut Hildebrandt  ---
Yes the problem still persists. 

The entry in question is "Exif.Photo.UserComment". It is set automatically by
the camera and used to be copied at import time to the caption area by
digicam4.

Cheers

Knut

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

[plasmashell] [Bug 372907] shell plugin org.kde.plasma.desktop can NOT be loaded

[Leslie Zhai]

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

--- Comment #2 from Leslie Zhai  ---
> Kactivities was made mandatory in the last release. 
Why is it not running?

I will check it out, thanks for your reply ;-)

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

[David Rankin]

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

David Rankin  changed:

   What|Removed |Added

 CC||drankinatty@suddenlinkmail.
   ||com

--- Comment #207 from David Rankin  ---
Why not just enable different wallpaper on each virtual desktop like KDE3?
Choose the virtual desktop, set the wallpaper for that desktop. 

I have no use for activities, and could care less about widgets. To me that
nonsense has been nothing but a 9 year waste of time that should be an optional
package, but I do like a different wallpaper on each desktop. There is no
reason anyone should have to set 10 different activity and widget settings just
to have a different wallpaper on each virtual desktop work and have the task
manager and desktop switcher still continue to function correctly.

As of Frameworks 5.28.0 and Qt 5.7.0, there is still no simple way to put a
different wallpaper on each virtual desktop in system settings.

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

[kate] [Bug 373013] New: KWrite crashes when closing the application

[bugzilla_noreply]

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

Bug ID: 373013
   Summary: KWrite crashes when closing the application
   Product: kate
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: kwrite
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: bbresla...@gmail.com
  Target Milestone: ---

Application: kwrite (16.08.3)

Qt Version: 5.7.0
Frameworks Version: 5.28.0
Operating System: Linux 4.5.4-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
Whenever I try to close KWrite, it crashes instead, around the time when the
"do you want to save" dialog opens up. I see the dialog start to open up, but
then it crashes before I have a chance to click a button in the dialog.

The crash can be reproduced every time.

-- Backtrace:
Application: KWrite (kwrite), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4097cdfc80 (LWP 8495))]

Thread 3 (Thread 0x7f407c23b700 (LWP 8497)):
#0  0x7f4093d0248d in poll () at /usr/lib/libc.so.6
#1  0x7f408dc57786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f408dc5789c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f409462472b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f40945ce23a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f40943f10f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f40905b4e55 in  () at /usr/lib/libQt5DBus.so.5
#7  0x7f40943f5d78 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f408f677454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f4093d0b7df in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f4084c55700 (LWP 8496)):
#0  0x7f4093d0248d in poll () at /usr/lib/libc.so.6
#1  0x7f408c1c48e0 in  () at /usr/lib/libxcb.so.1
#2  0x7f408c1c6679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#3  0x7f40873da449 in  () at /usr/lib/libQt5XcbQpa.so.5
#4  0x7f40943f5d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f408f677454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f4093d0b7df in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f4097cdfc80 (LWP 8495)):
[KCrash Handler]
#6  0x7f406966cb94 in  () at /usr/lib/libQtGui.so.4
#7  0x7f4097bbf4fa in call_init.part () at /lib64/ld-linux-x86-64.so.2
#8  0x7f4097bbf60b in _dl_init () at /lib64/ld-linux-x86-64.so.2
#9  0x7f4097bc3b38 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2
#10 0x7f4097bbf3a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#11 0x7f4097bc32d9 in _dl_open () at /lib64/ld-linux-x86-64.so.2
#12 0x7f408df20ee9 in  () at /usr/lib/libdl.so.2
#13 0x7f4097bbf3a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#14 0x7f408df21521 in  () at /usr/lib/libdl.so.2
#15 0x7f408df20f82 in dlopen () at /usr/lib/libdl.so.2
#16 0x7f4078da0bb0 in  () at /usr/lib/libvlccore.so.8
#17 0x7f4078d84ebb in  () at /usr/lib/libvlccore.so.8
#18 0x7f4078d851e8 in  () at /usr/lib/libvlccore.so.8
#19 0x7f4078d85144 in  () at /usr/lib/libvlccore.so.8
#20 0x7f4078d856c4 in  () at /usr/lib/libvlccore.so.8
#21 0x7f4078d85cca in  () at /usr/lib/libvlccore.so.8
#22 0x7f4078d0beb1 in libvlc_InternalInit () at /usr/lib/libvlccore.so.8
#23 0x7f4078adccee in libvlc_new () at /usr/lib/libvlc.so.5
#24 0x7f407903d2c8 in  () at
/usr/lib/qt5/plugins/phonon4qt5_backend/phonon_vlc.so
#25 0x7f4079012586 in  () at
/usr/lib/qt5/plugins/phonon4qt5_backend/phonon_vlc.so
#26 0x7f4079041195 in qt_plugin_instance () at
/usr/lib/qt5/plugins/phonon4qt5_backend/phonon_vlc.so
#27 0x7f40945b8cdb in QPluginLoader::instance() () at
/usr/lib/libQt5Core.so.5
#28 0x7f407e3eb180 in  () at /usr/lib/libphonon4qt5.so.4
#29 0x7f407e3edada in  () at /usr/lib/libphonon4qt5.so.4
#30 0x7f407e3ee179 in  () at /usr/lib/libphonon4qt5.so.4
#31 0x7f407e3eeaa4 in Phonon::Factory::backend(bool) () at
/usr/lib/libphonon4qt5.so.4
#32 0x7f407e3ef339 in  () at /usr/lib/libphonon4qt5.so.4
#33 0x7f407e3e3031 in  () at /usr/lib/libphonon4qt5.so.4
#34 0x7f407f2a48e0 in  () at /usr/lib/libKF5Notifications.so.5
#35 0x7f407f283220 in  () at /usr/lib/libKF5Notifications.so.5
#36 0x7f407f27f4f0 in KNotification::sendEvent() () at
/usr/lib/libKF5Notifications.so.5
#37 0x7f40945fc4b9 in QObject::event(QEvent*) () at
/usr/lib/libQt5Core.so.5
#38 0x7f40952afe0c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#39 0x7f40952b7581 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#40 0x7f40945cfde0 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#41 

[valgrind] [Bug 373012] xen: wrong DOMCTL identification for getvcpuaffinity

[Jose Mendes]

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

Jose Mendes  changed:

   What|Removed |Added

 CC||jmmlmen...@gmail.com

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

[valgrind] [Bug 373012] xen: wrong DOMCTL identification for getvcpuaffinity

[Jose Mendes]

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

Jose Mendes  changed:

   What|Removed |Added

  Component|helgrind|general

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

[valgrind] [Bug 373012] New: xen: wrong DOMCTL identification for getvcpuaffinity

[Jose Mendes]

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

Bug ID: 373012
   Summary: xen: wrong DOMCTL identification for getvcpuaffinity
   Product: valgrind
   Version: unspecified
  Platform: Other
OS: unspecified
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: helgrind
  Assignee: jsew...@acm.org
  Reporter: jmmlmen...@gmail.com
  Target Milestone: ---

Created attachment 102488
  --> https://bugs.kde.org/attachment.cgi?id=102488=edit
Patch 1/1

The getvcpuaffinity DOMCTL is wrongly identified as setvcpuaffinity. The
attached patch fixes it.

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

[dolphin] [Bug 211531] Dolphin is not honouring the LC_COLLATE setting

[Konstantinos Smanis]

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

--- Comment #16 from Konstantinos Smanis  ---
Created attachment 102487
  --> https://bugs.kde.org/attachment.cgi?id=102487=edit
en_US.utf8 locale breaking on some weird file names

Dolphin 16.08.3
Qt 5.6.1
KF 5.28.0

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

[dolphin] [Bug 211531] Dolphin is not honouring the LC_COLLATE setting

[Konstantinos Smanis]

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

--- Comment #15 from Konstantinos Smanis  ---
Created attachment 102486
  --> https://bugs.kde.org/attachment.cgi?id=102486=edit
C locale working properly on some weird file names

Dolphin 16.08.3
Qt 5.6.1
KF 5.28.0

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

[dolphin] [Bug 211531] Dolphin is not honouring the LC_COLLATE setting

[Konstantinos Smanis]

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

--- Comment #14 from Konstantinos Smanis  ---
Created attachment 102485
  --> https://bugs.kde.org/attachment.cgi?id=102485=edit
C locale working properly

Dolphin 16.08.3
Qt 5.6.1
KF 5.28.0

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

[dolphin] [Bug 211531] Dolphin is not honouring the LC_COLLATE setting

[Konstantinos Smanis]

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

Konstantinos Smanis  changed:

   What|Removed |Added

 Status|NEEDSINFO   |CONFIRMED
 Resolution|WAITINGFORINFO  |---

--- Comment #13 from Konstantinos Smanis  ---
Well, not all is peachy.

The 'C' locale seems to be properly collated, but other locales (e.g.
'en_US.utf8') are not.

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

[kolourpaint] [Bug 373011] New: Rotates images 90 deg. upon opening

[bugzilla_noreply]

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

Bug ID: 373011
   Summary: Rotates images 90 deg. upon opening
   Product: kolourpaint
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kolourpaint-supp...@lists.sourceforge.net
  Reporter: wade_me...@icloud.com
  Target Milestone: ---

A photo taken on a phone, say of a chair, then passed to the Ubuntu workstation
and opened, shows the chair 90 degrees rotated.  In the file viewer on the
workstation that preview icon shows the chair normally as photographed.
Rotating and saving the photo does not however change the file viewer icon
preview.  Minor flaw just adds and extra step to my editing every time.
Dell Optiplex GX620.

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

[digikam] [Bug 372093] corrupts image file when crashing

[Kai]

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

--- Comment #6 from Kai  ---
sorry for taking this long

I got the version from the kubuntu-backports for ubuntu trusty, which - sadly -
is v. 4.0.0 (cannot set this version number in the metadata of this bug entry).
LibExiv2 is tagged with version 0.23 here.

Up to now I only used this version that I can install from packages sources.

Nonetheless I uploaded a <1M corrupted jpg file to demonstrate what I'm trying
to describe (the file should be 5M to 8M).

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

[digikam] [Bug 372093] corrupts image file when crashing

[Kai]

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

--- Comment #5 from Kai  ---
Created attachment 102484
  --> https://bugs.kde.org/attachment.cgi?id=102484=edit
corrupted example jpg

corrupted example jpg

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

[plasmashell] [Bug 373010] New: Folder View does not accept touchscreen input

[Jacob]

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

Bug ID: 373010
   Summary: Folder View does not accept touchscreen input
   Product: plasmashell
   Version: 5.8.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Folder
  Assignee: h...@kde.org
  Reporter: doublejiniti...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

I am using Manjaro 16.10 with Plasma 5.8.4 and a Wacom touchscreen. The Folder
View plasmoid does not accept touchscreen input, regardless of how it is
configured, while other plasmoids work as expected.

Steps to reproduce:
1. Add a Folder View plasmoid anywhere on the desktop or in a panel.
2. Attempt to select or open an item using a touchscreen.

Actual Results:
The plasmoid does not register a click or display hover feedback.

Expected Results:
The plasmoid responds to the touchscreen the same as it would with a mouse or
touchpad.

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

[kate] [Bug 372997] SUGGESTION: KATE to have a ruler

[yereverluvinunclebert]

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

--- Comment #1 from yereverluvinunclebert  ---
I always run Kate with the line number feature switched on and in combination
with such a ruler, I could instantly find/report my position in the code as an
x,y position. Yes, I think it would be very useful.

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

[kdenlive] [Bug 372995] unable to exit full sceen in kdenlive

[farid]

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

farid  changed:

   What|Removed |Added

 CC||snd.no...@gmail.com

--- Comment #7 from farid  ---
Hi Colin,

Can we close this report?

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

[kdenlive] [Bug 370480] WISHLIST: Add Support for hardware encoders

[farid]

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

farid  changed:

   What|Removed |Added

 CC||snd.no...@gmail.com

--- Comment #1 from farid  ---
This is probable something you need to request from MLT upstream... I might be
wrong though.

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

[kdenlive] [Bug 364833] Crash when adding .wtv (Windows Media Center) clip.

[farid]

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

--- Comment #4 from farid  ---
Should we keep this open?

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

[kdenlive] [Bug 370907] Kdenlive freeze through rdesktop / xrdp

[farid]

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

farid  changed:

   What|Removed |Added

 CC||snd.no...@gmail.com

--- Comment #1 from farid  ---
Please test latest version and let us know... if fixed mark as solved.

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

[kdenlive] [Bug 370749] Import clip in fullscreen mode

[farid]

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

farid  changed:

   What|Removed |Added

 CC||snd.no...@gmail.com

--- Comment #1 from farid  ---
Cannot reproduce this issue ...

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

[digikam] [Bug 372540] fileSize field in Images table limited to 4GB

[Kusi]

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

--- Comment #3 from Kusi  ---
what about those who already have updated to schema v8? They're not getting
this fix, do they?

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

[kate] [Bug 373009] New: indention following single-statement loop over-indents the following command, must undo twice

[David Rankin]

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

Bug ID: 373009
   Summary: indention following single-statement loop over-indents
the following command, must undo twice
   Product: kate
   Version: 16.08
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: indentation
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: drankina...@suddenlinkmail.com
  Target Milestone: ---

Indent config: Soft Tabs: 4 (Indent using spaces)

If you attempt to add an additional line before the next statement after a
single-statement loop in a C source, autoindent indents the statement on the
current line 3-levels too many. Example, save the following as a C-source (e.g.
bug.c)

while (whatever) printf ("please fix indentation.\n");
return 0;

(make sure it has 4-spaces, a single level of indention before it in the file,
e.g. select it and press ctrl+i) Now place the cursor at the insertion point
immediately before the 'r' in 'return' (or at the beginning of the line) and
press enter ('.' inserted to preserve spacing below):

while (whatever) printf ("please fix indentation.\n");

..return 0;

That is 14-spaces before 'return' instead of the expected `4`. The expected
result is simply 4-spaces before each line with a blank line in between the
commands. Moreover, `14` spaces??? That should never happen anyway with 'Soft
Tabs: 4' set. Your indents are at 12 or 16, but never 14, something is borked.

Now try and 'undo' (e.g. ctrl+z). You can't in one step. You have to undo
twice. You should never have to 'undo' twice for the result of a single
keystroke. One keystroke, one undo should restore to the previous state.

Both of these make the indent model in kate/kwrite seems clumsy and broken.
With more than a decade using kate/kwrite, these bugs were never present and
the indent model in kde3. That indent model was very elegant and enjoyable to
use for C, C++, php, html, etc.. There were never any surprises and it was
rock-solid. The current indent model is more annoying than helpful in many
circumstances. A slip of the finger attempting to insert a 'single-quote' that
hits enter key and inserts a new line now takes '2 ctrl+z' to undo and restore
the editor state. That's just broken and a symptom of fundamental problems with
the current indent model. Is that a problem with KDE or Qt?

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

[kdenlive] [Bug 368816] git master - Saving a project on non-kde desktop doesn't automatically add the ".kdenlive" extension to the file name

[farid]

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

farid  changed:

   What|Removed |Added

  Flags||low_hanging?
 CC||snd.no...@gmail.com

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

[Akonadi] [Bug 372236] Akonadi will not start

[Etienne]

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

--- Comment #9 from Etienne  ---
Found DENIED access reports in Syslog so I disabled mysqld-akonady profile in
AppArmor.
Found /var/lib/mysql-files not found trying to start "/usr/sbin/mysqld-akonadi
--defaults-file=/etc/xdg/akonadi/mysql-global.conf --initialize
--datadir=/home/titi/.local/share/akonadi/db_data/" manually
Installed mysql-server

Finally got an Unknown Error... Don't know where to look further.

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

[kdenlive] [Bug 371553] Render issues

[farid]

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

farid  changed:

   What|Removed |Added

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

--- Comment #3 from farid  ---
This seems to be Krita and not Kdenlive related. Closing...

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

[kdenlive] [Bug 371900] I can't render animation from Krita

[farid]

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

farid  changed:

   What|Removed |Added

 CC||snd.no...@gmail.com

--- Comment #1 from farid  ---
give us more info like which version of kdenlive and what are the steps you are
doing...

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

[kwin] [Bug 372931] Plasma 5 get frozen if I grab a window and move it to any edge of the screen (on wayland)

[eduardo]

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

--- Comment #3 from eduardo  ---
I took this while I was using wayland
https://paste.kde.org/peslqxmiq

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

[kdenlive] [Bug 367776] Volume (keyframable) isn't

[farid]

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

farid  changed:

   What|Removed |Added

  Flags||low_hanging?

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

[kate] [Bug 373008] New: kate/kwrite autocomplete typecast in ternary deletes variable after conditional

[David Rankin]

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

Bug ID: 373008
   Summary: kate/kwrite autocomplete typecast in ternary deletes
variable after conditional
   Product: kate
   Version: 16.08
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: drankina...@suddenlinkmail.com
  Target Milestone: ---

In kate/kwrite in a C source, attempting to insert a typecast before the
variable name in the 'true condition' of a ternary causes autocomplete to
overwrite/delete the variable name. This is reproducible 100% of the time.

Example, save the following a as a C-source file (e.g. bug.c)

/* attempt to insert (ssize_t) as typecast following '?' with autocomplete
 * will cause autocomplete to delete 'idx' resulting in:
 *
 *   return idx ? (ssize_t : -1;
 *
 * after accepting the proposed autocomplete
 */
return idx ? idx : -1;

Now, with autocomplete enabled, attempt to insert '(ssize_t)' prior to the
'idx' following the '?'. [ e.g. start typing '(ssiidx' ] When autocomplete
suggests 'ssize_t in the autocomplete window, hit 'return' to accept the
proposal. 'idx' is delete leaving only:

return idx ? (ssize_t : -1;

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

[digikam] [Bug 373003] wrongly calculated uniqueHash

[Kusi]

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

--- Comment #4 from Kusi  ---
Maik, where exactly can I update to v2? I don't see any option in the settings
of DK5.2

Kusi

PS: thanks for the fast fix!

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

[libqgit2] [Bug 373007] Fix build with libgit2 >= 0.23

[rezso]

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

rezso  changed:

   What|Removed |Added

 CC||re...@rezso.net

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

[libqgit2] [Bug 373007] New: Fix build with libgit2 >= 0.23

[rezso]

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

Bug ID: 373007
   Summary: Fix build with libgit2 >= 0.23
   Product: libqgit2
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: nilsfen...@web.de
  Reporter: re...@rezso.net
  Target Milestone: ---

Created attachment 102483
  --> https://bugs.kde.org/attachment.cgi?id=102483=edit
libgit2 0.23 patch

I can't build libqgit2.git@bc8e7b0 with libgit2 0.24.1, bacause of API/ABI
changes in libgit2.
The attached patch fixes this; but it requires libgit2 >= 0.23.

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

[plasmashell] [Bug 373006] New: Plasma crash when using search box

[bugzilla_noreply]

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

Bug ID: 373006
   Summary: Plasma crash when using search box
   Product: plasmashell
   Version: 5.8.4
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: kdebt45...@outlook.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.4)

Qt Version: 5.7.1
Frameworks Version: 5.28.0
Operating System: Linux 4.4.27-2-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
Plasma almost always crashes when I use the search box in the start menu, or
from the desktop

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 0x7f74f7e73900 (LWP 3016))]

Thread 15 (Thread 0x7f740a7fc700 (LWP 3592)):
#0  0x7f74f0e270af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f74f1d0f46b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f743c83e3ff in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f743c841dca in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f743c83c42b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f743c841e12 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f743c83c42b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f743c841e12 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f743c83c42b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7f743c83fa26 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7f74f1d0e7f9 in  () at /usr/lib64/libQt5Core.so.5
#11 0x7f74f0e22734 in start_thread () at /lib64/libpthread.so.0
#12 0x7f74f1621d3d in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7f740affd700 (LWP 3591)):
#0  0x7f74f0e270af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f74f1d0f46b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f743c83e3ff in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f743c841dca in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f743c83c42b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f743c841e12 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f743c83c42b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f743c841e12 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f743c83c42b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7f743c83fa26 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7f74f1d0e7f9 in  () at /usr/lib64/libQt5Core.so.5
#11 0x7f74f0e22734 in start_thread () at /lib64/libpthread.so.0
#12 0x7f74f1621d3d in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7f740b7fe700 (LWP 3590)):
#0  0x7f74f0e270af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f74f1d0f46b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f743c83e3ff in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f743c841dca in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f743c83c42b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f743c841e12 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f743c83c42b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f743c841e12 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f743c83c42b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7f743c83fa26 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7f74f1d0e7f9 in  () at /usr/lib64/libQt5Core.so.5
#11 0x7f74f0e22734 in start_thread () at /lib64/libpthread.so.0
#12 0x7f74f1621d3d in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7f740bfff700 (LWP 3589)):
#0  0x7f74f0e270af in 

[KScreen] [Bug 372945] kscreen-console monitor crashes when the primary display changes

[Sebastian Kügler]

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

--- Comment #3 from Sebastian Kügler  ---
Hi Jan-Matthias,

Thanks a lot for the patch! I've reviewed and merged it into the stable and
master branches, and it'll be available in 5.8.5.

We usually use phabricator for patch workflows, so if you have anything in the
future, you may want to checkout phabricator.kde.org.

Again, thanks for the patch and rock on!

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

[KScreen] [Bug 372945] kscreen-console monitor crashes when the primary display changes

[Sebastian Kügler]

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

Sebastian Kügler  changed:

   What|Removed |Added

  Latest Commit|https://commits.kde.org/ksc |https://commits.kde.org/ksc
   |reen/d79dc2b8ca4f8c9daf6c6e |reen/d72edf2795a4a7206a8975
   |6f5f3e40580f6d224c  |1264a61a7b3d652ffe

--- Comment #2 from Sebastian Kügler  ---
Git commit d72edf2795a4a7206a89751264a61a7b3d652ffe by Sebastian Kügler.
Committed on 27/11/2016 at 22:22.
Pushed by sebas into branch 'master'.

guard against nullptr-access to the OutputPtr

output may be null here, as we don't necessarily have a primary display.
Guard against that case.

Patch by Jan-Matthias Braun, thanks!

CCMAIL:jan_br...@gmx.net
FIXED-IN:5.8.5

M  +6-1console/console.cpp

https://commits.kde.org/kscreen/d72edf2795a4a7206a89751264a61a7b3d652ffe

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

[KScreen] [Bug 372945] kscreen-console monitor crashes when the primary display changes

[Sebastian Kügler]

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

Sebastian Kügler  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||5.8.5
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/ksc
   ||reen/d79dc2b8ca4f8c9daf6c6e
   ||6f5f3e40580f6d224c

--- Comment #1 from Sebastian Kügler  ---
Git commit d79dc2b8ca4f8c9daf6c6e6f5f3e40580f6d224c by Sebastian Kügler.
Committed on 27/11/2016 at 22:20.
Pushed by sebas into branch 'Plasma/5.8'.

guard against nullptr-access to the OutputPtr

output may be null here, as we don't necessarily have a primary display.
Guard against that case.

Patch by Jan-Matthias Braun, thanks!

CCMAIL:jan_br...@gmx.net
FIXED-IN:5.8.5

M  +6-1console/console.cpp

https://commits.kde.org/kscreen/d79dc2b8ca4f8c9daf6c6e6f5f3e40580f6d224c

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

[KScreen] [Bug 372961] KScreen sends a lot of messages to system log

[Sebastian Kügler]

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

Sebastian Kügler  changed:

   What|Removed |Added

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

--- Comment #2 from Sebastian Kügler  ---
Thanks for the report!

The messages you see in the system log are needed for us to analyze problems in
the screen setup code, so these are useful as they help us to fix problems on
users' machines.

They're quite easy to disable, you can put the following in the 
~/.config/QtProject/qtlogging.ini

[Rules]
kscreen.*=false

And these messages will be gone.

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

[KXStitch] [Bug 372988] Importing image with with fractionals crashes KXStitch

[Steve Allewell]

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

Steve Allewell  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Steve Allewell  ---
I have tried a few images and some crash, some work as expected.  I will
investigate.

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

[digikam] [Bug 373003] wrongly calculated uniqueHash

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #3 from Maik Qualmann  ---
If you are still at uniqueHash v1 version, see you in setup->database the
update button for the uniqueHash v2 version.

Maik

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

[digikam] [Bug 373003] wrongly calculated uniqueHash

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

   Version Fixed In||5.4.0
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/dig
   ||ikam/2b8265ab1c785fae668dec
   ||4b468242cc898acc83

--- Comment #2 from Maik Qualmann  ---
Git commit 2b8265ab1c785fae668dec4b468242cc898acc83 by Maik Qualmann.
Committed on 27/11/2016 at 21:39.
Pushed by mqualmann into branch 'master'.

fix wrongly calculated uniqueHash v1
FIXED-IN: 5.4.0

M  +2-1NEWS
M  +1-1libs/dimg/loaders/dimgloader.cpp
M  +2-1utilities/setup/setupdatabase.cpp

https://commits.kde.org/digikam/2b8265ab1c785fae668dec4b468242cc898acc83

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

[dolphin] [Bug 373005] New: Dolphin crashes when dragging unused device somewhere

[Sascha Zenglein]

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

Bug ID: 373005
   Summary: Dolphin crashes when dragging unused device somewhere
   Product: dolphin
   Version: 16.08.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: panels: places
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: sascha.zengl...@yahoo.de
  Target Milestone: ---

If dragging a device that is unused from the (normally left) side panel into
some folder, dolphin crashes. 
Dolphin should either mount to the dragged directory or tell the user that it's
not possible.

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

[kdevelop] [Bug 373004] New: Segfault when switchin compiler

[bugzilla_noreply]

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

Bug ID: 373004
   Summary: Segfault when switchin compiler
   Product: kdevelop
   Version: 5.0.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: linus.kardell+kdeb...@gmail.com
  Target Milestone: ---

Application: kdevelop (5.0.1)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.27-2-default x86_64
Distribution: "openSUSE Leap 42.2"

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

Set CMAKE_C_COMPILER and CMAKE_CXX_COMPILER to gcc-6 and g++-6 and clicked OK.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1f7fd4b940 (LWP 20087))]

Thread 33 (Thread 0x7f1ea5648700 (LWP 20379)):
#0  0x7f1f7cb0751d in read () at /lib64/libc.so.6
#1  0x7f1f6e7d6073 in  () at /usr/lib64/tls/libnvidia-tls.so.367.57
#2  0x7f1f759b3670 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f1f75972e49 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f1f759732a8 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f1f7597342c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#6  0x7f1f7d41732b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#7  0x7f1f7d3c4fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#8  0x7f1f7d1fff1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#9  0x7f1f7ad25dd3 in  () at /usr/lib64/libKDevPlatformLanguage.so.10
#10 0x7f1f7d2049e9 in  () at /usr/lib64/libQt5Core.so.5
#11 0x7f1f765eb734 in start_thread () at /lib64/libpthread.so.0
#12 0x7f1f7cb13d3d in clone () at /lib64/libc.so.6

Thread 32 (Thread 0x7f1ec77fe700 (LWP 20366)):
#0  0x7f1f765f00af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f1f7d20565b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f1f71acf42f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f1f71ad2dea in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f1f71acd45b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f1f71ad0a46 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f1f7d2049e9 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f1f765eb734 in start_thread () at /lib64/libpthread.so.0
#8  0x7f1f7cb13d3d in clone () at /lib64/libc.so.6

Thread 31 (Thread 0x7f1ec7fff700 (LWP 20365)):
#0  0x7f1f765f00af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f1f7d20565b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f1f71acf42f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f1f71ad2dea in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f1f71acd45b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f1f71ad0a46 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f1f7d2049e9 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f1f765eb734 in start_thread () at /lib64/libpthread.so.0
#8  0x7f1f7cb13d3d in clone () at /lib64/libc.so.6

Thread 30 (Thread 0x7f1ee0ff9700 (LWP 20364)):
#0  0x7f1f765f00af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f1f7d20565b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f1f71acf42f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f1f71ad2dea in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f1f71acd45b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f1f71ad0a46 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f1f7d2049e9 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f1f765eb734 in start_thread () at /lib64/libpthread.so.0
#8  0x7f1f7cb13d3d in clone () at /lib64/libc.so.6

Thread 29 (Thread 0x7f1ee17fa700 (LWP 20363)):
#0  0x7f1f765f00af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f1f7d20565b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f1f71acf42f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, 

[kmymoney4] [Bug 372996] KMyMoney

[Thomas Baumgart]

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

Thomas Baumgart  changed:

   What|Removed |Added

 CC||mar...@aqbanking.de

--- Comment #1 from Thomas Baumgart  ---
Something is wrong with the information managed by AqBanking. Did you ever use
AqBanking for production purposes? Are there any mapped accounts with valid
information setup? Do you use another application (e.g. GnuCash) that uses
AqBanking? I am asking, becuase it might be the easiest to wipe out the
AqBanking data that is certainly missing something. But before I tell you how
to do it, I want to make sure we don't wipe out important data.

You could try to start KMyMoney from the command line with option -n which
prevents opening the last opened file after startup. Goto Settings/Aqbanking
settings and remove entries for accounts and users you don't need. See if that
makes a difference when loading a KMyMoney file.

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

[dolphin] [Bug 372489] when right clicking to select open with dolphin crashes

[konstan]

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

--- Comment #3 from konstan  ---
Created attachment 102482
  --> https://bugs.kde.org/attachment.cgi?id=102482=edit
New crash information added by DrKonqi

dolphin (15.12.3) using Qt 5.5.1

- Unusual behavior I noticed: kwin starts freezing the desktop but that's a
special issue causes by my computer (radeon-drm trouble)

-- Backtrace (Reduced):
#6  QVector::isEmpty (this=) at
../../include/QtCore/../../src/corelib/tools/qvector.h:84
#7  QThreadStorageData::finish (p=p@entry=0xf8) at
thread/qthreadstorage.cpp:169
#8  0x7f0eedaf4965 in QThreadPrivate::finish (arg=arg@entry=0x489ab10) at
thread/qthread_unix.cpp:351
#9  0x7f0eedaf57df in __pthread_cleanup_class::~__pthread_cleanup_class
(this=, __in_chrg=) at
/usr/include/pthread.h:561
#10 QThreadPrivate::start (arg=0x489ab10) at thread/qthread_unix.cpp:290

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

[dolphin] [Bug 372489] when right clicking to select open with dolphin crashes

[konstan]

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

konstan  changed:

   What|Removed |Added

 CC||gazd...@yahoo.com

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

[valgrind] [Bug 352395] Please provide SVN revision info in --version

[Ivo Raisr]

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

--- Comment #21 from Ivo Raisr  ---
There is also online tool at: http://www.shellcheck.net/
However it did not catch the problem with mismatched then...

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

[valgrind] [Bug 352395] Please provide SVN revision info in --version

[Ivo Raisr]

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

--- Comment #20 from Ivo Raisr  ---
Patch #6 seems to be working well. I tested it on Solaris, inside SVN tree,
outside and after 'make dist'.

In addition to the last comment by Austin, please change also:

auxprogs/make_or_upd_vgversion_h:
-   when using command lines options:  -v --version 
+   when using command line options:  -v --version 

and make sure that auxprogs/make_or_upd_vgversion_h is marked as executable in
SVN repository.

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

[plasmashell] [Bug 372963] plasmashell does not handle changes of the primary screen

[Jan-Matthias Braun]

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

Jan-Matthias Braun  changed:

   What|Removed |Added

   Keywords||multiscreen

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

[plasmashell] [Bug 372963] plasmashell does not handle changes of the primary screen

[Jan-Matthias Braun]

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

--- Comment #9 from Jan-Matthias Braun  ---
Of course, for the final patches I forgot to go to the root folder. They have
to be applied directly in the shell folder...

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

[digikam] [Bug 373003] wrongly calculated uniqueHash

[bugzilla_noreply]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #1 from caulier.gil...@gmail.com ---
You are right. 

A patch can be easy to make against git/master...

Gilles Caulier

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

[valgrind] [Bug 352395] Please provide SVN revision info in --version

[Bart Van Assche]

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

Bart Van Assche  changed:

   What|Removed |Added

 CC||bvanass...@acm.org

--- Comment #19 from Bart Van Assche  ---
Although it's not a compiler, the following tool is very convenient for
checking the syntax of shell scripts: https://github.com/koalaman/shellcheck. I
build and install it as follows:
git clone https://github.com/koalaman/shellcheck
cd shellcheck
cabal update
cabal install cabal-install
cabal install

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

[plasmashell] [Bug 372963] plasmashell does not handle changes of the primary screen

[Jan-Matthias Braun]

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

--- Comment #8 from Jan-Matthias Braun  ---
Created attachment 102481
  --> https://bugs.kde.org/attachment.cgi?id=102481=edit
Reimplement desktopForScreen without using m_ScreenPool, now providing correct
results and fixing the primary output switching problem.

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

[plasmashell] [Bug 372963] plasmashell does not handle changes of the primary screen

[Jan-Matthias Braun]

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

--- Comment #7 from Jan-Matthias Braun  ---
Created attachment 102480
  --> https://bugs.kde.org/attachment.cgi?id=102480=edit
Remove a bizzare include.

This patch removes a ktexteditor include in shellcorona.cpp.

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

[plasmashell] [Bug 372963] plasmashell does not handle changes of the primary screen

[Jan-Matthias Braun]

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

--- Comment #6 from Jan-Matthias Braun  ---
Okay. Looks like the m_screenPool-Numbering is inconsistend with the
m_desktopViewforId-Numbering. THerefore, in primaryOutputChanged, the id for
the old as well as the new primary DesktopView is == 0 and no swap takes place!

In general, desktopForScreen does not return the correct DesktopView. This
should be the reason, why the assert fails. When patching desktopForScreen, the
Q_ASSERT does not explode.

When using the patched desktopForScreen insted of the m_screenPool in
primaryOutputChanged, then it does not explode, too, and the primary desktop is
at the right place.

I will attach the patch now.

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

[valgrind] [Bug 352395] Please provide SVN revision info in --version

[Philippe Waroquiers]

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

--- Comment #18 from Philippe Waroquiers  ---
Created attachment 102479
  --> https://bugs.kde.org/attachment.cgi?id=102479=edit
try7 : fix syntax error in the git extract version

bash -n is not reporting any syntax error on this :(

(my kingdom for a shell compiler)

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

[valgrind] [Bug 352395] Please provide SVN revision info in --version

[Philippe Waroquiers]

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

Philippe Waroquiers  changed:

   What|Removed |Added

 Attachment #102468|0   |1
is obsolete||

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

[plasmashell] [Bug 372907] shell plugin org.kde.plasma.desktop can NOT be loaded

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #1 from David Edmundson  ---
Kactivities was made mandatory in the last release. 

Partly to resolve a bug that KActivities has two different enum statuses for
loading, but not differentiating status between loading and failed to load.

Why is it not running? A Netrunner thing?

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

[digikam] [Bug 373003] wrongly calculated uniqueHash

[Kusi]

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

Kusi  changed:

   What|Removed |Added

 CC||k...@forum.titlis.org

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

[digikam] [Bug 373003] New: wrongly calculated uniqueHash

[Kusi]

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

Bug ID: 373003
   Summary: wrongly calculated uniqueHash
   Product: digikam
   Version: 5.2.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Database-Mysql
  Assignee: digikam-de...@kde.org
  Reporter: k...@forum.titlis.org
  Target Milestone: ---

A new uniqueHash algorithm was implemented a few years ago. See
https://bugs.kde.org/show_bug.cgi?id=210353. The new algorithm in uniqueHashV2
was only made available for newly created databases. An already existing
database was (and is till today) still using the old uniqueHash algorithm. My
10 years old digikam db still uses the old uniqueHash algo. The old algo worked
fine till digikam 4.14. During the porting to DK 5, a bug was introduced for
the old algo:

In dimgloaded.cpp, the KDE4 command for the old v1 uniqueHash algo

   KMD5 md5;
   ...
   hash = md5.hexDigest();

was replaced in the KDE5 porting with ( still uniqueHash v1)

   QCryptographicHash md5(QCryptographicHash::Md5);
   ...
   hash = md5.result();

which is wrong. Instead, it should have been replaced by

   QCryptographicHash md5(QCryptographicHash::Md5);
   ...
   hash = md5.result().toHex();

See the migration document
https://api.kde.org/frameworks/kdelibs4support/html/classKMD5.html#a49b31c3e5eb180fa8be8c8f576266221

As a consequence, a database created before 2010 calculates different
uniqueHash values in DK5 compared to DK4. Furthermore, UTF8 cannot be used
since some of the now calculated uniqueHash values are not valid UTF8
characters, the SQL server erorrs with

  "REPLACE INTO Images  ( album, name, status, category, modificationDate,
  fileSize, uniqueHash )  VALUES (?,?,?,?,?,?,?);"
  Error messages: "QMYSQL3: Unable to execute statement" "Incorrect string
  value: '\\xF1\\x9E\\xA6\\x87' for column 'uniqueHash' at row 1" 1366 2
  Bound values:  (QVariant(int, 118053), QVariant(QString, "P4240656.JPG"),
  QVariant(int, 1), QVariant(int, 1), QVariant(QString,
  "2016-10-30T19:16:42"), QVariant(qlonglong, 6951936), QVariant(QString,
  "m�7�\U0005E987"))

There is uniqueHashVersion in the System table, but the value "2" in DK4 and
DK5 return different hash values.

The fix would be easy, just add the missing ".toHex()". However, all images
added in DK5 already contain the invalid hash values. They need legacy
treatment.

The most clean solution is to get rid of hashValue version 1 and recalculate
all hash values in the next DK release

As as sidenote: hashValueV2 is not affected by this bug. This means a db
created after 2010 is not affected

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

[digikam] [Bug 372680] Cannot delete files from NAS

[dajomu]

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

--- Comment #5 from dajomu  ---
This might be a bit more informative.

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

[digikam] [Bug 372680] Cannot delete files from NAS

[dajomu]

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

--- Comment #4 from dajomu  ---
Created attachment 102478
  --> https://bugs.kde.org/attachment.cgi?id=102478=edit
digikam Console debug report

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

[kdenlive] [Bug 372995] unable to exit full sceen in kdenlive

[Colin]

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

--- Comment #6 from Colin  ---
Thank you I will try that I have mint xfce on another PC I will check that
also

Colin

On 27 Nov 2016 19:56, "Jean-Baptiste Mardelle" 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=372995
>
> --- Comment #5 from Jean-Baptiste Mardelle  ---
> I just tested on Linux Mint 18 Xfce with the official packages, KDE
> Frameworks
> 5.18, Qt 5.5.1, Kdenlive 16.08.2 and everything works fine, Ctrl+Shift+f
> does
> switch fullscreen. Did you maybe define a custom shortcut that conflicts
> with
> this ? Otherwise my guess is that Cinnamon does block the shortcut, in
> which
> case this is not a Kdenlive issue. Can you check another KDE application,
> like
> kwrite that should behave the same on ctrl+shift+f ?
>
> Cinnamon seems to have some global shortcuts that maybe come in the way,
> see:
> https://www.lifewire.com/how-to-change-the-linux-mint-
> cinnamon-keyboard-shortcuts-4064754
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[kdevelop] [Bug 373001] Output file encoding becomes ISO-8859-15 after saving

[Anthony Dentinger]

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

--- Comment #1 from Anthony Dentinger  ---
I'm getting the same problem with other header files, but not CPP files. Either
the problem concerns only header files, or the heuristic is confused by my
Doxygen comments (which I have only in headers).

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

[kate] [Bug 373002] New: Single line comment in Less begins a new region

[bugzilla_noreply]

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

Bug ID: 373002
   Summary: Single line comment in Less begins a new region
   Product: kate
   Version: 16.08
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: syntax
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: gscs...@gmail.com
  Target Milestone: ---

If you type // in a Less (LESSCSS) file, Kate incorrectly opens a new region
(it should do it in case of multiline comment, /*…*/). If you try to hide that
region (using the arrow that's next to line number) it actually hides
everything in the file starting from the comment.

Fixing this bug requires removing ' beginRegion="lessComment" ' from line 924
(of less.xml) and incrementing file version number on line 3.

Single line comments are part of Less, as stated here:
http://lesscss.org/features/#features-overview-feature-comments

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

[digikam] [Bug 372540] fileSize field in Images table limited to 4GB

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/dig
   ||ikam/80017e16f30e9ea4e97fe1
   ||a7c78dbaab7e66bd94
 Resolution|--- |FIXED
   Version Fixed In||5.4.0

--- Comment #2 from Maik Qualmann  ---
Git commit 80017e16f30e9ea4e97fe1a7c78dbaab7e66bd94 by Maik Qualmann.
Committed on 27/11/2016 at 19:58.
Pushed by mqualmann into branch 'master'.

change fileSize field to BIGINT in MySQL DB schema v8
FIXED-IN: 5.4.0

M  +2-1NEWS
M  +4-2data/database/dbconfig.xml.cmake.in

https://commits.kde.org/digikam/80017e16f30e9ea4e97fe1a7c78dbaab7e66bd94

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

[kdenlive] [Bug 372995] unable to exit full sceen in kdenlive

[Jean-Baptiste Mardelle]

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

--- Comment #5 from Jean-Baptiste Mardelle  ---
I just tested on Linux Mint 18 Xfce with the official packages, KDE Frameworks
5.18, Qt 5.5.1, Kdenlive 16.08.2 and everything works fine, Ctrl+Shift+f does
switch fullscreen. Did you maybe define a custom shortcut that conflicts with
this ? Otherwise my guess is that Cinnamon does block the shortcut, in which
case this is not a Kdenlive issue. Can you check another KDE application, like
kwrite that should behave the same on ctrl+shift+f ?

Cinnamon seems to have some global shortcuts that maybe come in the way, see:
https://www.lifewire.com/how-to-change-the-linux-mint-cinnamon-keyboard-shortcuts-4064754

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

[krita] [Bug 372679] Crash when creating new document

[bugzilla_noreply]

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

--- Comment #3 from jeanlucpont...@gmail.com ---
Any word on this? According to what I attached previously, my system
supports up to Open GL4. It has no issues at all running any other
graphics/art programs.

 Additionally, it ran without incident when I installed it--as stated
previously, it only had problems after I turned off Open GL, then turned it
back on again.

On Mon, Nov 21, 2016 at 9:36 PM, Jean Luc Pontiac 
wrote:

> Hi Boudewijn,
>
> That's what I thought too, except that when I first installed it, it
> worked fine. It was only after I unchecked OpenGL and then rechecked it
> that the troubles began.
> I'm using Intel HD 4000 integrated graphics, which apparently is
> compatible with Open GL 4.0, but potentially not Krita's implementation of
> it? I hadn't updated anything for a long time, and as I say, when I first
> installed, it worked fine. 2.9.11.0 works perfectly, so for the time being,
> that's what I'll use.
>
> I did update my display drivers to the latest available, then tried to
> install 3.0.1.1 over 2.9.11.0 (which didn't work), and also tried
> uninstalling completely and reinstalling from scratch (also didn't work).
> Same result each time, always crashes when I try to create a new document.
>
> In any case, hopefully the attached is helpful. I'm running a pretty
> middle-of-the-road machine, so it might be helpful for other casual users
> to know of potential issues with similar machines.
>
> Thanks for taking a look! I'm always blown away how fast you respond! I'm
> glad you and your team are around--Krita is amazing (even the slightly
> older versions)!
>
> JLP
>
>
> On Mon, Nov 21, 2016 at 5:09 AM, Boudewijn Rempt  > wrote:
>
>> https://bugs.kde.org/show_bug.cgi?id=372679
>>
>> Boudewijn Rempt  changed:
>>
>>What|Removed |Added
>> 
>> 
>>  CC||b...@valdyas.org
>>
>> --- Comment #1 from Boudewijn Rempt  ---
>> I suspect that your graphics driver isn't compatible with Krita's opengl
>> canvas: which GPU and driver version do you have?
>>
>> --
>> You are receiving this mail because:
>> You reported the bug.
>
>
>
>
> --
> "If Milli Vanilli fall in the forest, does someone else make a sound?"
>

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

[kio] [Bug 354647] kio slaves die for all KDE4 applications using Plasma 5 (15.08.2) and KF 5.15.0 on migrated profiles

[Leszek Lesner]

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

Leszek Lesner  changed:

   What|Removed |Added

 CC||leszek.les...@web.de

--- Comment #4 from Leszek Lesner  ---
I can confirm this. 
Removing the kdebugrc fixes the issue.

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

[plasmashell] [Bug 372963] plasmashell does not handle changes of the primary screen

[Jan-Matthias Braun]

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

--- Comment #5 from Jan-Matthias Braun  ---
There aren't many (0!) comments indicating what should happen.
But from looking at other parts of the code,
QScreen *oldPrimary = m_desktopViewforId.value(0)->screen();

the primary DesktopView always has id 0.

Now, primaryOutputChanged is called before removeDesktop. As far as I
understand it, the screen for the primary desktopView is switched and thus the
assert does
not hold anymore, when removeDesktop is called now.

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

[kdevelop] [Bug 373001] New: Output file encoding becomes ISO-8859-15 after saving

[Anthony Dentinger]

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

Bug ID: 373001
   Summary: Output file encoding becomes ISO-8859-15 after saving
   Product: kdevelop
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: all editors
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: a.dentin...@gmail.com
  Target Milestone: ---

Created attachment 102475
  --> https://bugs.kde.org/attachment.cgi?id=102475=edit
Specific file of which KDevelop changes Encoding after saving

1) Under 'Settings > Configure Editor... > Open/Save > General', make sure
Encoding and Fallback-Encoding are UTF-8 and Encoding Detection is Universal.
2) Open attached file with Kate, file should be UTF-8.
3) Open file with KDevelop.
3) Save file with KDevelop.
4) Open file with Kate. File is now ISO-8859-15.

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

[kdevelop] [Bug 373001] Output file encoding becomes ISO-8859-15 after saving

[Anthony Dentinger]

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

Anthony Dentinger  changed:

   What|Removed |Added

   Severity|normal  |minor

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

[frameworks-kio] [Bug 343452] Does not sort numbers naturally any longer

[Konstantinos Smanis]

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

--- Comment #15 from Konstantinos Smanis  ---
This bug managed to annoy the hell out of that itching part of my brain, so I
did a little digging. I posted my review on
https://git.reviewboard.kde.org/r/128574/

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

[dolphin] [Bug 211531] Dolphin is not honouring the LC_COLLATE setting

[Konstantinos Smanis]

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

Konstantinos Smanis  changed:

   What|Removed |Added

 CC||konstantinos.smanis@gmail.c
   ||om

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

[kdenlive] [Bug 372995] unable to exit full sceen in kdenlive

[Colin]

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

--- Comment #4 from Colin  ---
Yes it's KDE framework 5.18.0
Qt 5.5.1
And Linux Mint 18 cinnamon 64-bit
Linux Kernel 4.4.0-47-generic
Colin

On 27 Nov 2016 18:55, "Jean-Baptiste Mardelle" 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=372995
>
> --- Comment #3 from Jean-Baptiste Mardelle  ---
> I cannot reproduce. The Fullscreen feature is a standard KDE function. The
> problem might be caused by some older KDE libraries. Can you go in
> Kdenlive's
> menu:
>
> Help > About Kdenlive > Version
>
> And tell me what versions of KDE frameworks you are using ? Also which Mint
> version ?
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[kdenlive] [Bug 372995] unable to exit full sceen in kdenlive

[Jean-Baptiste Mardelle]

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

--- Comment #3 from Jean-Baptiste Mardelle  ---
I cannot reproduce. The Fullscreen feature is a standard KDE function. The
problem might be caused by some older KDE libraries. Can you go in Kdenlive's
menu:

Help > About Kdenlive > Version

And tell me what versions of KDE frameworks you are using ? Also which Mint
version ?

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

[kdenlive] [Bug 372995] unable to exit full sceen in kdenlive

[Colin]

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

--- Comment #2 from Colin  ---
This does not work I have tried this and full screen still remains,
disabling full screen in the settings does not work either

Colin

On 27 Nov 2016 18:37, "Jean-Baptiste Mardelle" 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=372995
>
> --- Comment #1 from Jean-Baptiste Mardelle  ---
> Well, the shortcut for Fullscreen mode is, like described in the "Settings"
> menu:
>
> Ctrl+Shift+F
>
> This will enable/disable the fullscreen mode. Is that what you were looking
> for?
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[kdenlive] [Bug 372995] unable to exit full sceen in kdenlive

[Jean-Baptiste Mardelle]

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

--- Comment #1 from Jean-Baptiste Mardelle  ---
Well, the shortcut for Fullscreen mode is, like described in the "Settings"
menu:

Ctrl+Shift+F

This will enable/disable the fullscreen mode. Is that what you were looking
for?

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

[ark] [Bug 372999] Compress and Extract plugins freezing application for long time if many files selected

[Elvis Angelaccio]

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

--- Comment #4 from Elvis Angelaccio  ---
Actually, it's 

m_pluginManager->preferredPluginsFor()

that is slow.

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

[kate] [Bug 373000] New: Kate opens new tab if a file is opened twice (from dolphin)

[bugzilla_noreply]

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

Bug ID: 373000
   Summary: Kate opens new tab if a file is opened twice (from
dolphin)
   Product: kate
   Version: 16.08
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: h...@gmx.at
  Target Milestone: ---

* klick on file in dolphin
  * kate opens

* klick on same file again 
  * kate opens second tab

You end up with two tabs for the same file. If you edit both of them it, you
get
strange messages about

* klick on file in dolphin
  * kate opens
  * edit

* klick on same file again 
  * kate opens second tab
  * message "file was not saved regulary" (Translation from my de-Environment)
  * choice "reload" -- files are in sync

* edit both tabs
  * save first tab -- ok
  * save second tab -- "file was changed by external program"

same behavior on mint 18-kde (kate 15.12.3) and gentoo (16.08)

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

[ark] [Bug 372999] Compress and Extract plugins freezing application for long time if many files selected

[Elvis Angelaccio]

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

--- Comment #3 from Elvis Angelaccio  ---
The bottle-neck is in extractfileitemaction.cpp:

foreach (const QUrl , fileItemInfos.urlList()) {
const QMimeType mimeType = determineMimeType(url.fileName());
if (m_pluginManager->preferredPluginsFor(mimeType).isEmpty()) {
continue;
}
...
}

For some reason, determineMimeType() is slow (query to the mime DB?)

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

[kdenlive] [Bug 372867] wizard uses old logo

[Jean-Baptiste Mardelle]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kde
   ||nlive/2719cc32779afbef53d60
   ||805f1083c9464c1b7cf
 Status|CONFIRMED   |RESOLVED

--- Comment #1 from Jean-Baptiste Mardelle  ---
Git commit 2719cc32779afbef53d60805f1083c9464c1b7cf by Jean-Baptiste Mardelle.
Committed on 27/11/2016 at 18:01.
Pushed by mardelle into branch 'Applications/16.12'.

Several First run wizard fixes:
Fix icon, codec detection, add warning if frei0r or breeze are not installed

M  +46   -18   src/dialogs/wizard.cpp
M  +1-1src/mainwindow.cpp

https://commits.kde.org/kdenlive/2719cc32779afbef53d60805f1083c9464c1b7cf

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

[Touchpad-KCM] [Bug 370588] Global keyboard shortcut for KDE Daemon:Toggle Touchpad actually maps to Disable Touchpad

[nicholas]

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

nicholas  changed:

   What|Removed |Added

 CC||ndcunli...@gmail.com

--- Comment #14 from nicholas  ---
i have the same problem on ASUS UX305 (using the default mapping FN-F9) 
opensuse tumbleweed on 5.8.4. 
[i have had to map ctrl-F9 to enable touchpad to prevent lockout]

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