[kdeconnect] [Bug 378488] New: abort() when transfering big files

[Yuxuan Shui]

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

Bug ID: 378488
   Summary: abort() when transfering big files
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: yshu...@gmail.com
  Target Milestone: ---

(gdb) bt
#0  0x7efe20b8ca10 in raise () from /usr/lib/libc.so.6
#1  0x7efe20b8e13a in abort () from /usr/lib/libc.so.6
#2  0x7efe20f8e4ed in __gnu_cxx::__verbose_terminate_handler ()
at /build/gcc-multilib/src/gcc/libstdc++-v3/libsupc++/vterminate.cc:95
#3  0x7efe20f8c2a6 in __cxxabiv1::__terminate (handler=)
at /build/gcc-multilib/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:47
#4  0x7efe20f8c2f1 in std::terminate () at
/build/gcc-multilib/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:57
#5  0x7efe20f8c508 in __cxxabiv1::__cxa_throw (obj=0xbaa260,
tinfo=0x7efe21276770 , 
dest=0x7efe20f8a650 ) at
/build/gcc-multilib/src/gcc/libstdc++-v3/libsupc++/eh_throw.cc:87
#6  0x7efe21314362 in qBadAlloc() () from /usr/lib/libQt5Core.so.5
#7  0x7efe2133635a in QByteArray::reallocData(unsigned int,
QFlags) () from /usr/lib/libQt5Core.so.5
#8  0x7efe2133650a in QByteArray::resize(int) () from
/usr/lib/libQt5Core.so.5
#9  0x7efe21439bd3 in QIODevice::readAll() () from /usr/lib/libQt5Core.so.5
#10 0x7efe233328ae in
DownloadJob::socketFailed(QAbstractSocket::SocketError) () from
/usr/lib/libkdeconnectcore.so.1
#11 0x7efe21538d49 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#12 0x7efe208babe1 in QAbstractSocket::error(QAbstractSocket::SocketError)
() from /usr/lib/libQt5Network.so.5
#13 0x7efe208fc52d in ?? () from /usr/lib/libQt5Network.so.5
#14 0x7efe208e73c1 in ?? () from /usr/lib/libQt5Network.so.5
#15 0x7efe21538d49 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#16 0x7efe208bba93 in ?? () from /usr/lib/libQt5Network.so.5
#17 0x7efe208bbb4c in ?? () from /usr/lib/libQt5Network.so.5
#18 0x7efe208c7101 in ?? () from /usr/lib/libQt5Network.so.5
#19 0x7efe221ef34c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#20 0x7efe221f6b61 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#21 0x7efe2150d440 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#22 0x7efe215624fd in ?? () from /usr/lib/libQt5Core.so.5
#23 0x7efe1b1515a7 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#24 0x7efe1b151810 in ?? () from /usr/lib/libglib-2.0.so.0
#25 0x7efe1b1518bc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#26 0x7efe2156204f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#27 0x7efe2150b89a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#28 0x7efe21513de4 in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
---Type  to continue, or q  to quit---
#29 0x00401cc4 in ?? ()
#30 0x7efe20b79511 in __libc_start_main () from /usr/lib/libc.so.6
#31 0x00401d2a in _start ()

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

[kwin] [Bug 378486] KWin crashes after unlocking locked session

[Martin Gräßlin]

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

--- Comment #1 from Martin Gräßlin  ---
please provide output of:
qdbus org.kde.KWin /KWin supportInformation

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

[i18n] [Bug 378479] Bad Spanish translation in Application Dashboard

[Burkhard Lueck]

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

Burkhard Lueck  changed:

   What|Removed |Added

   Assignee|h...@kde.org|kde-l10n...@kde.org
Product|kdeplasma-addons|i18n
Version|5.9.4   |unspecified
 CC||lu...@hube-lueck.de
  Component|Application Dashboard   |es

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

[Spectacle] [Bug 378468] Section in window

[Burkhard Lueck]

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

Burkhard Lueck  changed:

   What|Removed |Added

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

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

[kate] [Bug 378487] New: Incorrect termination of \iffalse comment for latex highlight

[Andrea]

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

Bug ID: 378487
   Summary: Incorrect termination of \iffalse comment for latex
highlight
   Product: kate
   Version: Git
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: syntax
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: andrea.turr...@gmail.com
  Target Milestone: ---

The latex.xml syntax highlight file contains the following snippets of code for
identifying a multiline comment obtained by means of \iffalse ... \fi:








It induces the correct highlighting in several cases, except when the part of
text between \iffalse and \fi contains a command starting with "\fi", like
\fill.
In such a case, the comment highlighting stops at \fi of \fill and this may
cause a completely wrong highlighting of the remaining part of the text, in
particular when this happens inside a math mode.

A possible fix for this situation is to replace the code






with 






which prevents to match \fi and \else as termination of the multiline comment
when they occur as prefix of another command (like \fi in \fill).

The fix has been checked with kile 2.1.3 and kate 3.14.9 in openSUSE 13.2 as
well as with kate 16.08.2 in openSUSE Leap 42.2; the shipped syntax file is the
same as the one in the git repository, so it should apply there as well.

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

[kwin] [Bug 378486] New: KWin crashes after unlocking locked session

[Rodrigo]

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

Bug ID: 378486
   Summary: KWin crashes after unlocking locked session
   Product: kwin
   Version: 5.8.6
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: rmsi...@cmicro.com.br
  Target Milestone: ---

Application: kwin_x11 (5.8.6)

Qt Version: 5.7.1
Frameworks Version: 5.32.0
Operating System: Linux 4.10.8-200.fc25.x86_64 x86_64
Distribution: "Fedora release 25 (Twenty Five)"

-- Information about the crash:
- What I was doing when the application crashed:
Desktop is set to lock after 5 min, require password after 35secs. Sometimes
unlocking works as expected; sometimes KWin crashes (and restarts) after
unlocking. Other times the desktop is completely messed up with with ever
changing shapes (squares, triangles) containing distorted (zoomed, shifted)
application windows contents.  In this scenario, unlocking does not work by
entering the password. It is necessary to log into another tty and issue an
"loginctl unlock-sessions" in order for the session to be usable again. After
manual unlock as root, I can return to X and session is correctly restored.
- Unusual behavior I noticed:

- Custom settings of the application:
System running NVIDIA proprietary drivers (378.13). Fedora 25 with linux
4.10.8-200. 4K display using DP connector. This behavior (especially the messed
up lock screen) seems to occur  more often after a fresh boot. If the machine
is suspended one or more times, unlocking problems occur less frequently (but
will eventually happen again). Every week or so, even unlocking from the
console fails and an X restart is needed to be able to log into KDE again.

The crash can be reproduced sometimes.

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

Thread 6 (Thread 0x7f28d0dfe700 (LWP 32473)):
#0  0x7f291e29d460 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f2923b642f4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQt5Script.so.5
#2  0x7f2923b64339 in  () at /lib64/libQt5Script.so.5
#3  0x7f291e2976ca in start_thread () at /lib64/libpthread.so.0
#4  0x7f291b486f7f in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f28e9208700 (LWP 32471)):
#0  0x7f291e29d809 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f28f051be44 in  () at /lib64/libGLX_nvidia.so.0
#2  0x7f28e9fd4394 in  () at /lib64/libnvidia-glcore.so.378.13
#3  0x7f28f051b12c in  () at /lib64/libGLX_nvidia.so.0
#4  0x7f291e2976ca in start_thread () at /lib64/libpthread.so.0
#5  0x7f291b486f7f in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f28f0ffd700 (LWP 32468)):
#0  0x7f291b47b0e1 in ppoll () at /lib64/libc.so.6
#1  0x7f291c27d971 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /lib64/libQt5Core.so.5
#2  0x7f291c27ee86 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#3  0x7f291c23268a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#4  0x7f291c08f5e3 in QThread::exec() () at /lib64/libQt5Core.so.5
#5  0x7f2922db94e5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#6  0x7f291c0939ca in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7f291e2976ca in start_thread () at /lib64/libpthread.so.0
#8  0x7f291b486f7f in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f2902e18700 (LWP 32464)):
#0  0x7f291b47b0e1 in ppoll () at /lib64/libc.so.6
#1  0x7f291c27d971 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /lib64/libQt5Core.so.5
#2  0x7f291c27ee86 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#3  0x7f291c23268a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#4  0x7f291c08f5e3 in QThread::exec() () at /lib64/libQt5Core.so.5
#5  0x7f291ddb2739 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#6  0x7f291c0939ca in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7f291e2976ca in start_thread () at /lib64/libpthread.so.0
#8  0x7f291b486f7f in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f29044da700 (LWP 32463)):
#0  0x7f291b47b01d in poll () at /lib64/libc.so.6
#1  0x7f291db80d10 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7f291db82aa9 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7f29053b4d69 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7f291c0939ca in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7f291e2976ca in start_thread () at /lib64/libpthread.so.0
#6  0x7f291b486f7f in clone () at 

[krita] [Bug 378485] New: I can't draw anythig at all

[bugzilla_noreply]

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

Bug ID: 378485
   Summary: I can't draw anythig at all
   Product: krita
   Version: 3.1.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: zulmagua...@gmail.com
  Target Milestone: ---

When I select a brush and try to draw on the canvas, nothing appears. The
cursor of the brush stays in one place and doesn't move. When I click the 'X'
on the upper right corner to close the program and it says do you want to save
it, whatever I had tried to draw appears.

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

[krita] [Bug 360723] won't allow me to draw

[bugzilla_noreply]

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

zulmagua...@gmail.com changed:

   What|Removed |Added

 CC||zulmagua...@gmail.com

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

[digikam] [Bug 378478] Small Improvement of subalbum display in thumbnails view

[bugzilla_noreply]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com
   Severity|normal  |wishlist

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

[krita] [Bug 378484] New: Popup Palette usability issues of unwanted right-click selecting & holding-releasing right-click actions

[Tyson Tan]

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

Bug ID: 378484
   Summary: Popup Palette usability issues of unwanted right-click
selecting & holding-releasing right-click actions
   Product: krita
   Version: 3.1.3-alpha
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: tyson...@mail.com
  Target Milestone: ---

In Krita 3.1.x and older, Popup palette has a few usability issues that cause
unwanted actions:

1) Right-click can pick color and select brush presets. 

As Krita 3.1.x's current design, when the cursor is above the popup palette,
another right click selects something on the palette before closing it down.
This is bad because: Right click is associated with BRINGING UP the popup
palette -- we expect another right-click to be associated with CLOSING DOWN the
palette. We normally don't pay attention to the cursor position when we close
the palette, so it is very easy to select unwanted colors and brush presets
accidentally, breaking the flow.

2) Holding Right-click and release automatically selects brush preset and close
popup palette.

Holding right click over canvas can bring up popup palette. Keep holding it and
move the cursor over a brush preset icon and release, the preset will be
selected and the palette close down immediately. This aggravates the problem of
(1). What's more, releasing the right button over the palette's color picker
doesn't do anything, an inconsistency of UI interaction. 

Allowing holding-key command is usually a bad idea because mouse and stylus
does not work the same:

A) A mouse runs on a solid surface, which means a CLICK can be done in a clean
and reliable way.

B) A stylus is supported by soft flesh. When the force over a barrel button is
lifted, the bouncing back flesh keeps the button activated for a longer period.
We cannot predict when the clicking mechanism is bring released. In this case,
many (EXPECTED) CLICKS are recognized as HOLDING by the system. That's why it's
very difficult to use a 1-button in-line remote control of a headset to perform
NEXT (2-clicks) and BACK (3-clicks).

Therefore, we should always consider that on a stylus, CLICKS and HOLDING
cannot be executed in a reliable way and they always mix with each other. 

The issues above cause too many unwanted changes of color and brush and
confusion in Krita. Therefore I suggest:

A) Do not allow right click to select popup palette items.

B) Do not auto-select-and-close when a holding-right-click is released, keep
the popup palette up so we can have time to look, think, select.

C) Treat all holding right-clicks as 1 normal right-click. Do not assign
different functions to right-click and holding-right-click.

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

[frameworks-kio] [Bug 371721] slaveinterface.cpp do not compile under Centos 6.8

[Aleix Pol]

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

--- Comment #18 from Aleix Pol  ---
Upstream patch...
https://gitlab.kitware.com/cmake/cmake/merge_requests/671

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

[frameworks-kio] [Bug 371721] slaveinterface.cpp do not compile under Centos 6.8

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|INVALID |---

--- Comment #17 from Aleix Pol  ---
Reopening because this requires changes in cmake that won't be backported.
Bug report in upstream cmake:
https://gitlab.kitware.com/cmake/cmake/issues/16640

Will see into offering a workaround meanwhile.

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

[kdeplasma-addons] [Bug 378342] Input Method Panel doesn't seem to work

[Nate Graham]

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

--- Comment #11 from Nate Graham  ---
Excellent!

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

[okular] [Bug 362856] [Frameworks] Wrong render resolution, possibly caused by Plasma 5 "Scale Display"

[Tavian Barnes]

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

Tavian Barnes  changed:

   What|Removed |Added

 CC||taviana...@gmail.com

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

[kde] [Bug 378483] New: Plasma crashed on an attempt to add KNote widget

[bugzilla_noreply]

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

Bug ID: 378483
   Summary: Plasma crashed on an attempt to add KNote widget
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: exc...@yandex.ru
  Target Milestone: ---

Application: plasma-desktop (4.11.22)
KDE Platform Version: 4.14.21
Qt Version: 4.8.7
Operating System: Linux 4.4.38 x86_64
Distribution (Platform): Slackware Packages

-- Information about the crash:
- What I was doing when the application crashed:
Unlocked the task bar panel.
Chose to add new widgets.
Typed "not" to find "KNotes"
Captured "KNotes" by mouse and dragged to the right-bottom screen corner. I
just tried to collapse all app windows to see the clean desktop. As the Plasma
configured such: if the mouse pointer is in the right-bottom corner of the
screen, all app windows should collapse.
But happen sth strange. The dragging stopped & a gray rectangle appeared to the
right of the clock widget.
Then I tried to remove that rectangle. Clicked much time on it & so on. No
effect.
Then near of it right-click -> remove the widget "Panel" -> ... CRASH!!!

-- Backtrace:
Application: Оболочка Plasma (plasma-desktop), signal: Segmentation fault
[KCrash Handler]
#6  0x7f41c2f329f8 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/qt/lib/libQtCore.so.4
#7  0x7f410bbdfc11 in  () at
/usr/lib64/kde4/imports/org/kde/draganddrop/libdraganddropplugin.so
#8  0x7f410bbe2372 in  () at
/usr/lib64/kde4/imports/org/kde/draganddrop/libdraganddropplugin.so
#9  0x7f410bbe2419 in  () at
/usr/lib64/kde4/imports/org/kde/draganddrop/libdraganddropplugin.so
#10 0x7f41c26508f0 in  () at /usr/lib64/qt/lib/libQtGui.so.4
#11 0x7f41c265505e in  () at /usr/lib64/qt/lib/libQtGui.so.4
#12 0x7f41c2655bcf in  () at /usr/lib64/qt/lib/libQtGui.so.4
#13 0x7f41c265d616 in
QGraphicsScene::mouseMoveEvent(QGraphicsSceneMouseEvent*) () at
/usr/lib64/qt/lib/libQtGui.so.4
#14 0x7f41c266a3b7 in QGraphicsScene::event(QEvent*) () at
/usr/lib64/qt/lib/libQtGui.so.4
#15 0x7f41c207448c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/qt/lib/libQtGui.so.4
#16 0x7f41c207af5c in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/qt/lib/libQtGui.so.4
#17 0x7f41c3f7e8ea in KApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libkdeui.so.5
#18 0x7f41c2f1fc0d in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/qt/lib/libQtCore.so.4
#19 0x7f41c267f91f in
QGraphicsViewPrivate::mouseMoveEventHandler(QMouseEvent*) () at
/usr/lib64/qt/lib/libQtGui.so.4
#20 0x7f41c268060a in QGraphicsView::mouseMoveEvent(QMouseEvent*) () at
/usr/lib64/qt/lib/libQtGui.so.4
#21 0x7f41c20c74d0 in QWidget::event(QEvent*) () at
/usr/lib64/qt/lib/libQtGui.so.4
#22 0x7f41c246efae in QFrame::event(QEvent*) () at
/usr/lib64/qt/lib/libQtGui.so.4
#23 0x7f41c2681cbf in QGraphicsView::viewportEvent(QEvent*) () at
/usr/lib64/qt/lib/libQtGui.so.4
#24 0x7f41c2f1fd76 in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at
/usr/lib64/qt/lib/libQtCore.so.4
#25 0x7f41c207446c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/qt/lib/libQtGui.so.4
#26 0x7f41c207b0c3 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/qt/lib/libQtGui.so.4
#27 0x7f41c3f7e8ea in KApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libkdeui.so.5
#28 0x7f41c2f1fc0d in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/qt/lib/libQtCore.so.4
#29 0x7f41c207a75d in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at
/usr/lib64/qt/lib/libQtGui.so.4
#30 0x7f41c20f1af9 in  () at /usr/lib64/qt/lib/libQtGui.so.4
#31 0x7f41c20efdf5 in QApplication::x11ProcessEvent(_XEvent*) () at
/usr/lib64/qt/lib/libQtGui.so.4
#32 0x7f41c2117942 in  () at /usr/lib64/qt/lib/libQtGui.so.4
#33 0x7f41bd7db797 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#34 0x7f41bd7db9c8 in  () at /usr/lib64/libglib-2.0.so.0
#35 0x7f41bd7dba6c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#36 0x7f41c2f4e0ae in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/qt/lib/libQtCore.so.4
#37 0x7f41c21179e6 in  () at /usr/lib64/qt/lib/libQtGui.so.4
#38 0x7f41c2f1e5d1 in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/qt/lib/libQtCore.so.4
#39 0x7f41c2f1e8e5 in
QEventLoop::exec(QFlags) () at
/usr/lib64/qt/lib/libQtCore.so.4
#40 0x7f41c2f23ec9 in QCoreApplication::exec() () at
/usr/lib64/qt/lib/libQtCore.so.4
#41 0x7f41aad46874 in kdemain () at

[Discover] [Bug 378482] New: don't show applications

[josevallegas]

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

Bug ID: 378482
   Summary: don't show applications
   Product: Discover
   Version: 5.6.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: josevalle...@gmail.com
  Target Milestone: ---

Discover don't show any of the installed or the available applications. So I
cannot install new applications to complete the configuration.  
The platform is Kubuntu 16.04

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

[frameworks-kio] [Bug 371721] slaveinterface.cpp do not compile under Centos 6.8

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 CC||aleix...@kde.org

--- Comment #16 from Aleix Pol  ---
I just reproduced this issue while building ARM32 binaries on Flatpak.

This is a bug related to both our bigger upstreams...
https://bugreports.qt.io/browse/QTBUG-57796
https://gitlab.kitware.com/cmake/cmake/issues/16640

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

[krunner] [Bug 372635] do not follow mousepointer when accessing krunner via keyboard

[Aetf]

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

Aetf <7437...@gmail.com> changed:

   What|Removed |Added

 CC||7437...@gmail.com

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

[kdevelop] [Bug 378451] Crashes on creation/opening of a project

[marcthe12]

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

marcthe12  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED

--- Comment #2 from marcthe12  ---
Works in 5.10

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

[kexi] [Bug 378481] Entering **/**/17 in a date field saves as the year 1917

[Jarosław Staniek]

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

Jarosław Staniek  changed:

   What|Removed |Added

 CC||clickoclu...@gmail.com

--- Comment #1 from Jarosław Staniek  ---
(report by clickoclu...@gmail.com)

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

[kexi] [Bug 378481] Entering **/**/17 in a date field saves as the year 1917

[Jarosław Staniek]

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

Jarosław Staniek  changed:

   What|Removed |Added

   Target Milestone|--- |3.0.2
   Priority|NOR |HI
 OS|Linux   |All

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

[kexi] [Bug 378481] New: Entering **/**/17 in a date field saves as the year 1917

[Jarosław Staniek]

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

Bug ID: 378481
   Summary: Entering **/**/17 in a date field saves as the year
1917
   Product: kexi
   Version: 3.1 Alpha
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tables
  Assignee: kexi-b...@kde.org
  Reporter: stan...@kde.org
CC: a...@piggz.co.uk, in...@fables.co.za
  Target Milestone: ---

Entering **/**/17 in a date field saves as the year 1917.

Verify in tables and forms.

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

[kexi] [Bug 378480] Renaming and Saving As queries and forms isn't working properly

[Jarosław Staniek]

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

Jarosław Staniek  changed:

   What|Removed |Added

   Platform|Other   |Compiled Sources

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

[kexi] [Bug 378418] Auto-opening command line options missing in Kexi 3.0

[Jarosław Staniek]

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

--- Comment #1 from Jarosław Staniek  ---
(report by clickoclu...@gmail.com)

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

[kexi] [Bug 378480] Renaming and Saving As queries and forms isn't working properly

[Jarosław Staniek]

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

Jarosław Staniek  changed:

   What|Removed |Added

 CC||clickoclu...@gmail.com

--- Comment #1 from Jarosław Staniek  ---
(report by clickoclu...@gmail.com)

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

[kexi] [Bug 378480] Renaming and Saving As queries and forms isn't working properly

[Jarosław Staniek]

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

Jarosław Staniek  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
   Target Milestone|--- |3.0.2
   Assignee|kexi-b...@kde.org   |stan...@kde.org
 Ever confirmed|0   |1

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

[kexi] [Bug 378418] Auto-opening command line options missing in Kexi 3.0

[Jarosław Staniek]

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

Jarosław Staniek  changed:

   What|Removed |Added

 CC||clickoclu...@gmail.com

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

[kexi] [Bug 378480] New: Renaming and Saving As queries and forms isn't working properly

[Jarosław Staniek]

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

Bug ID: 378480
   Summary: Renaming and Saving As queries and forms isn't working
properly
   Product: kexi
   Version: 3.1 Alpha
  Platform: Other
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: kexi-b...@kde.org
  Reporter: stan...@kde.org
CC: a...@piggz.co.uk, in...@fables.co.za
  Target Milestone: ---

Renames seem to work until you try to open the query/form again then it throws
an error. Closing and opening Kexi reverts back to the original name.

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

[kexi] [Bug 377579] Criteria cannot be saved in Query Designer

[Jarosław Staniek]

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

--- Comment #5 from Jarosław Staniek  ---
Reviews:
https://phabricator.kde.org/D5295
https://phabricator.kde.org/D5294

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

[kdenlive] [Bug 378469] 17.04 - Crash on Exit

[Paul Konecny]

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

Paul Konecny  changed:

   What|Removed |Added

 CC||j...@kdenlive.org

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

[kio-extras] [Bug 372860] MTP not usable : connects, then disconnects, then connects...

[Vlastimil Kriz]

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

Vlastimil Kriz  changed:

   What|Removed |Added

 CC||vlastimil.k...@seznam.cz

--- Comment #1 from Vlastimil Kriz  ---
I have the same problem ...

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

[KScreen] [Bug 354534] kscreen-console MUST NOT use qDebug for output

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/ksc
   ||reen/ab1f2c9a3bc491118b51c2
   ||2b8cfc9a19f1da0116
 Resolution|--- |FIXED

--- Comment #6 from Albert Astals Cid  ---
Git commit ab1f2c9a3bc491118b51c22b8cfc9a19f1da0116 by Albert Astals Cid, on
behalf of Jan-Matthias Braun.
Committed on 05/04/2017 at 21:44.
Pushed by aacid into branch 'master'.

Remove quoting from kscreen-console json-output
Differential Revision: https://phabricator.kde.org/D3552

M  +3-1console/console.cpp

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

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

[Spectacle] [Bug 376387] scaling problem of Spectacle dialog form

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

  Latest Commit|https://commits.kde.org/spe |https://commits.kde.org/spe
   |ctacle/e822b05d85498330758e |ctacle/4d07e74bdbfdceadf9c5
   |0b1ce4601ad809249f7b|05238ab3bc45b1eeb94b

--- Comment #3 from Albert Astals Cid  ---
Git commit 4d07e74bdbfdceadf9c505238ab3bc45b1eeb94b by Albert Astals Cid, on
behalf of Lukas Hetzenecker.
Committed on 05/04/2017 at 21:29.
Pushed by aacid into branch 'Applications/17.04'.

Allow shrinking of dialog
REVIEW: 130059

M  +1-0src/Gui/KSImageWidget.cpp

https://commits.kde.org/spectacle/4d07e74bdbfdceadf9c505238ab3bc45b1eeb94b

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

[frameworks-kwidgetsaddons] [Bug 378276] Impossible to tell whether password field shows plaintext with empty content

[Elvis Angelaccio]

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

--- Comment #9 from Elvis Angelaccio  ---
(In reply to Elvis Angelaccio from comment #8)
> I'm actually wondering if this is a bug in QLineEdit. The clear action is
> always visible (isVisible() == true) even though is not...

Reported upstream: https://bugreports.qt.io/browse/QTBUG-59957

I think we can go with the first approach (always show the button in plaintext
mode) + a temporary workaround for the aforementioned bug. Will upload a patch
soon.

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

[dolphin] [Bug 378470] Dolphin and several other programs crashed while formatting a USB stick with GParted

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 Resolution|--- |BACKTRACE
 Status|UNCONFIRMED |NEEDSINFO
 CC||elvis.angelac...@kde.org

--- Comment #1 from Elvis Angelaccio  ---
Looks like a crash in Solid, but are missing debug symbols so the backtrace is
not useful. Please install debug symbols and post again the backtrace.

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

[kdeplasma-addons] [Bug 378342] Input Method Panel doesn't seem to work

[Weng Xuetian]

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

Weng Xuetian  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
   Version Fixed In||5.10
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/pla
   ||sma-desktop/6e03b6f5465a5df
   ||6135be1795b33f8fd50483ced

--- Comment #10 from Weng Xuetian  ---
Git commit 6e03b6f5465a5df6135be1795b33f8fd50483ced by Weng Xuetian.
Committed on 05/04/2017 at 20:45.
Pushed by xuetianweng into branch 'master'.

kimpanel: add a ibus panel launcher.

Launcher will wait for ibus start and launch the panel then quit.
Launcher is started by dataengine. Also this change make kimpanel's
panel quit when dataengine disappears (applet removable will trigger
it). DBus magic will actually be able to fallback it to the running gtk3
panel.
FIXED-IN: 5.10

M  +1-0applets/kimpanel/backend/CMakeLists.txt
M  +11   -2applets/kimpanel/backend/ibus/CMakeLists.txt
A  +6-0applets/kimpanel/backend/ibus/config-kimpanel.h.cmake
M  +9-2applets/kimpanel/backend/ibus/ibus15/app.cpp
M  +4-2applets/kimpanel/backend/ibus/ibus15/app.h
A  +90   -0applets/kimpanel/backend/ibus/launcher.cpp [License: LGPL
(v2+)]
M  +3-0dataengines/kimpanel/CMakeLists.txt
A  +6-0dataengines/kimpanel/config-kimpanel.h.cmake
M  +3-0dataengines/kimpanel/kimpanelagent.cpp
M  +1-0dataengines/kimpanel/kimpanelagent.h
M  +14   -0dataengines/kimpanel/kimpaneldataengine.cpp
M  +1-0dataengines/kimpanel/org.kde.impanel.xml

https://commits.kde.org/plasma-desktop/6e03b6f5465a5df6135be1795b33f8fd50483ced

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

[kdeplasma-addons] [Bug 378342] Input Method Panel doesn't seem to work

[Weng Xuetian]

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

--- Comment #9 from Weng Xuetian  ---
Ok, seems dbus request name will queue up even if the name is lost. Good to
know that. So it will be able actually fallback to existing running gtk panel.
Though, there's still a small issue need to be fixed on ibus side. But now we
can make the ibus panel to be started by plasmashell.

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

[kdeplasma-addons] [Bug 378479] New: Bad Spanish translation in Application Dashboard

[al-dy]

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

Bug ID: 378479
   Summary: Bad Spanish translation in Application Dashboard
   Product: kdeplasma-addons
   Version: 5.9.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Application Dashboard
  Assignee: h...@kde.org
  Reporter: dopazo.alv...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

Created attachment 104897
  --> https://bugs.kde.org/attachment.cgi?id=104897=edit
Screenshot

"Apps & Docs" is translated like "ón de las aplicaciones" that is
totally wrong, the correct translation is: "Aplicaciones y documentos"

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

[digikam] [Bug 378478] New: Small Improvement of subalbum display in thumbnails view

[Jens]

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

Bug ID: 378478
   Summary: Small Improvement of subalbum display in thumbnails
view
   Product: digikam
   Version: 5.6.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: AlbumsView
  Assignee: digikam-de...@kde.org
  Reporter: jens-bugs.kde@spamfreemail.de
  Target Milestone: ---

Created attachment 104896
  --> https://bugs.kde.org/attachment.cgi?id=104896=edit
screenshot mockup of current album header and collapsed / expanded possible
enhancement

I have two small suggestions for the album view: display of number of images
and removal of (IMHO unnecessary) text, and allowing to collapse the thumbnails
of one album (like in iPhoto). See attached screenshot.
With the left side arrow pointing down, the view is expanded and the album's
thumbnails are visible below. With the arrow pointing right, the view is
collapsed and there are no thumbnails  (and subalbums fo the collapsed album)
visible.

A Ctrl-click (or Shift-click) on the arrow could in addition collapse / expand
*all* albums' thumbnails of the current view. The arrow status (collapsed /
expanded) would need to be saved in the albums' metadata.

This slight UI change has several advantages:
- less strings to translate,
- metadata like date and number of images is easier to find (right-aligned),
- less (vertical) screen space required (important for today's 16:9 displays)
if album name, date and number of images tag fit beside (otherwise the date and
the number of images would need to wrap),
- I can view the contents of several albums at once (e.g. to compare or find
images, or to split/merge albums), even if they are not chronologically beside
each other. This is what I did in iPhoto (it used to have the same view) and
actually my main reason for this suggestion.

I think it would make a nice UI improvement for the albums view.

What do you think?

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

[digikam] [Bug 378475] Digikam crashed after connecting a Camera

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|general |Import

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

[digikam] [Bug 378475] Digikam crashed after connecting a Camera

[bugzilla_noreply]

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

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

   What|Removed |Added

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

--- Comment #1 from caulier.gil...@gmail.com ---
The crash appear when thumbnails are extracted for camera.

I see QtAV called. You have video files in your memory cards. Right ?

I'm not sure if the problem come from the video media. Which kind of video type
mime do you use exactly ?

If this video file are imported on your computer by another way than DK Import
tool, can you see any video thumbnails generated in album icon view ?

Gilles Caulier

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

[tellico] [Bug 378477] Can't see the star icon in the column view and in the entry editor

[bugzilla_noreply]

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

--- Comment #1 from fcremone...@gmail.com ---
i've see that the current of the screen is italian, sorry. Anyway i think that
you can guess that "rating" is translated in "valutazione personale"

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

[tellico] [Bug 378477] New: Can't see the star icon in the column view and in the entry editor

[bugzilla_noreply]

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

Bug ID: 378477
   Summary: Can't see the star icon in the column view and in the
entry editor
   Product: tellico
   Version: 3.0.1
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: ro...@periapsis.org
  Reporter: fcremone...@gmail.com
  Target Milestone: ---

Created attachment 104895
  --> https://bugs.kde.org/attachment.cgi?id=104895=edit
screen of the editor and the entries

I don't know why, but when I upgraded tellico at the 3.0.1 version the rating
star disappeared, even from the editor. Before the upgrade i used the 2.3.9
version and everything was ok. At the moment i'm working the Xubuntu 16.04
release.

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

[elisa] [Bug 378476] New: Dark themes compatibility

[Roman]

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

Bug ID: 378476
   Summary: Dark themes compatibility
   Product: elisa
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: bugw...@zoho.com
  Target Milestone: ---

Created attachment 104894
  --> https://bugs.kde.org/attachment.cgi?id=104894=edit
Dark fonts

Some text remain dark while using dark themes

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

[digikam] [Bug 378475] New: Digikam crashed after connecting a Camera

[Martin]

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

Bug ID: 378475
   Summary: Digikam crashed after connecting a Camera
   Product: digikam
   Version: 5.5.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: martin.ruess...@mailbox.org
  Target Milestone: ---

Application: digikam (5.5.0)

Qt Version: 5.8.0
Frameworks Version: 5.32.0
Operating System: Linux 4.10.6-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
I connected a Camera to my PC and clicked on the import button to import
images. No images on the Camera were shown and Digikam crashed.

-- Backtrace:
Application: digiKam (digikam), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f31bd84f680 (LWP 4668))]

Thread 57 (Thread 0x7f30a2c02700 (LWP 5406)):
#0  0x7f31b395eb63 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f31b9a0c4c6 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f31b9a07bc4 in  () at /usr/lib/libQt5Core.so.5
#3  0x7f31b9a0b6d8 in  () at /usr/lib/libQt5Core.so.5
#4  0x7f31b39582e7 in start_thread () at /usr/lib/libpthread.so.0
#5  0x7f31b8d0754f in clone () at /usr/lib/libc.so.6

Thread 56 (Thread 0x7f30a0ff9700 (LWP 5403)):
#0  0x7f31b395e756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f31b9a0c7cb in QWaitCondition::wait(QReadWriteLock*, unsigned long)
() at /usr/lib/libQt5Core.so.5
#2  0x7f31b5169b7b in QtAV::BlockingQueue::take() () at
/usr/lib/libQtAV.so.1
#3  0x7f31b51d35b8 in QtAV::ExtractThread::run() () at
/usr/lib/libQtAV.so.1
#4  0x7f31b9a0b6d8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f31b39582e7 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f31b8d0754f in clone () at /usr/lib/libc.so.6

Thread 55 (Thread 0x7f30a2401700 (LWP 5402)):
#0  0x7f31b395e756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f31b9a0c7cb in QWaitCondition::wait(QReadWriteLock*, unsigned long)
() at /usr/lib/libQt5Core.so.5
#2  0x7f31b5169b7b in QtAV::BlockingQueue::take() () at
/usr/lib/libQtAV.so.1
#3  0x7f31b51d35b8 in QtAV::ExtractThread::run() () at
/usr/lib/libQtAV.so.1
#4  0x7f31b9a0b6d8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f31b39582e7 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f31b8d0754f in clone () at /usr/lib/libc.so.6

Thread 54 (Thread 0x7f30a37fe700 (LWP 5396)):
#0  0x7f31b8cfd67d in poll () at /usr/lib/libc.so.6
#1  0x7f3188e5fd51 in  () at /usr/lib/libusb-1.0.so.0
#2  0x7f31b39582e7 in start_thread () at /usr/lib/libpthread.so.0
#3  0x7f31b8d0754f in clone () at /usr/lib/libc.so.6

Thread 53 (Thread 0x7f30b3fff700 (LWP 5394)):
#0  0x7f31b395e756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f31b9a0c7cb in QWaitCondition::wait(QReadWriteLock*, unsigned long)
() at /usr/lib/libQt5Core.so.5
#2  0x7f31b5169b7b in QtAV::BlockingQueue::take() () at
/usr/lib/libQtAV.so.1
#3  0x7f31b51d35b8 in QtAV::ExtractThread::run() () at
/usr/lib/libQtAV.so.1
#4  0x7f31b9a0b6d8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f31b39582e7 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f31b8d0754f in clone () at /usr/lib/libc.so.6

Thread 52 (Thread 0x7f30b1023700 (LWP 5393)):
#0  0x7f31b395e756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f31b9a0c7cb in QWaitCondition::wait(QReadWriteLock*, unsigned long)
() at /usr/lib/libQt5Core.so.5
#2  0x7f31b5169b7b in QtAV::BlockingQueue::take() () at
/usr/lib/libQtAV.so.1
#3  0x7f31b51d35b8 in QtAV::ExtractThread::run() () at
/usr/lib/libQtAV.so.1
#4  0x7f31b9a0b6d8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f31b39582e7 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f31b8d0754f in clone () at /usr/lib/libc.so.6

Thread 51 (Thread 0x7f30967f4700 (LWP 5392)):
#0  0x7f31b8d07f5a in timerfd_settime () at /usr/lib/libc.so.6
#1  0x7f3188e58cf3 in  () at /usr/lib/libusb-1.0.so.0
#2  0x7f3188e59b14 in  () at /usr/lib/libusb-1.0.so.0
#3  0x7f3188e5a770 in libusb_handle_events_timeout_completed () at
/usr/lib/libusb-1.0.so.0
#4  0x7f3188e5a8c0 in libusb_handle_events_completed () at
/usr/lib/libusb-1.0.so.0
#5  0x7f3188e5b1d9 in  () at /usr/lib/libusb-1.0.so.0
#6  0x7f3188e5b2dd in  () at /usr/lib/libusb-1.0.so.0
#7  0x7f3188e5b67f in libusb_bulk_transfer () at /usr/lib/libusb-1.0.so.0
#8  0x7f30b3420f91 in  () at /usr/lib/libgphoto2_port/0.12.0/usb1.so
#9  

[digikam] [Bug 370553] Adjust date - not possible to update "digikam timestamp"

[Kristian]

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

--- Comment #10 from Kristian  ---
I still have regular problems with digikam's internal timestamp. I adjusted the
time of a movie file with the TimeAdjustTool and everything seems to be fine
(file modified date, etc.) apart from digikam's internal timestamp. Even after
updating every single timestamp exiftool is showing, digikam's timestamp
refrains from being updated and I have no idea how to update it. 

$ exiftool -time:all -G1 -a *.MOV
 20170402T174944-NikonD7200_matchDateTime.MOV
[System]File Modification Date/Time : 2017:04:02 18:48:41+02:00
[System]File Access Date/Time   : 2017:04:05 21:30:12+02:00
[System]File Inode Change Date/Time : 2017:04:05 21:30:12+02:00
[QuickTime] Create Date : 2017:04:02 18:48:41
[QuickTime] Modify Date : 2017:04:02 18:48:41
[Track1]Track Create Date   : 2017:04:02 18:48:41
[Track1]Track Modify Date   : 2017:04:02 18:48:41
[Track1]Media Create Date   : 2017:04:02 18:48:41
[Track1]Media Modify Date   : 2017:04:02 18:48:41
[Track2]Track Create Date   : 2017:04:02 18:48:41
[Track2]Track Modify Date   : 2017:04:02 18:48:41
[Track2]Media Create Date   : 2017:04:02 18:48:41
[Track2]Media Modify Date   : 2017:04:02 18:48:41
[Nikon] Create Date : 2017:04:02 18:48:41
[Nikon] Date/Time Original  : 2017:04:02 18:48:41
[Nikon] Time Zone   : +01:00
[Nikon] Daylight Savings: No
[Nikon] Date Display Format : D/M/Y
[XMP-exif]  Date/Time Original  : 2017:04:02 18:48:41
[XMP-xmp]   Create Date : 2017:04:02 18:48:41

digikam still displays the old date before adjusting the time be approx. an
hour...

Therefore, the option to update it manually would be nice.

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

[krita] [Bug 349833] with the wacom tablet, the pencils are just unusable lagging. with the mouse its okay

[bugzilla_noreply]

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

eman5...@gmail.com changed:

   What|Removed |Added

 CC||eman5...@gmail.com

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

[frameworks-kcmutils] [Bug 366299] System setting "Energy Saving" window is too large for a standard laptop screen

[RJ]

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

RJ  changed:

   What|Removed |Added

 CC||ogldel...@mail.ru

--- Comment #10 from RJ  ---
Yes same here with 1366x768

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

[plasmashell] [Bug 378474] New: Plasma crashed when restarting Akonadi

[Dennis Schridde]

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

Bug ID: 378474
   Summary: Plasma crashed when restarting Akonadi
   Product: plasmashell
   Version: 5.9.4
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: devuran...@gmx.net
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.9.4)

Qt Version: 5.7.1
Frameworks Version: 5.32.0
Operating System: Linux 4.10.8-gentoo x86_64
Distribution: "Gentoo Base System release 2.3"

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

I was checking some clock settings, restarted Akonadi to see whether I could
get the clock's calendar to display my events, when suddenly Plasma crashed.

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

Thread 15 (Thread 0x7f62e9d56700 (LWP 4803)):
#0  0x7f63f02d828d in read () from /lib64/libc.so.6
#1  0x7f63ebcab770 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f63ebc683c6 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f63ebc68890 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f63ebc689fc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f63f0c0f44b in QEventDispatcherGlib::processEvents
(this=0x7f62e40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7f63f0bc309a in QEventLoop::exec (this=this@entry=0x7f62e9d55d80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#7  0x7f63f0a30584 in QThread::exec (this=) at
thread/qthread.cpp:507
#8  0x7f63f0a346fb in QThreadPrivate::start (arg=0x39a73f0) at
thread/qthread_unix.cpp:368
#9  0x7f63ef8a634c in start_thread () from /lib64/libpthread.so.0
#10 0x7f63f02e539f in clone () from /lib64/libc.so.6

Thread 14 (Thread 0x7f630d26e700 (LWP 15646)):
#0  0x7f63f02dc18d in poll () from /lib64/libc.so.6
#1  0x7f63ebc688ec in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f63ebc689fc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f63f0c0f44b in QEventDispatcherGlib::processEvents
(this=0x7f6308c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f63f0bc309a in QEventLoop::exec (this=this@entry=0x7f630d26dd80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f63f0a30584 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f63f0a346fb in QThreadPrivate::start (arg=0x25fa6f0) at
thread/qthread_unix.cpp:368
#7  0x7f63ef8a634c in start_thread () from /lib64/libpthread.so.0
#8  0x7f63f02e539f in clone () from /lib64/libc.so.6

Thread 13 (Thread 0x7f630e8d6700 (LWP 15329)):
#0  0x7f63f02dc18d in poll () from /lib64/libc.so.6
#1  0x7f63ebc688ec in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f63ebc689fc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f63f0c0f44b in QEventDispatcherGlib::processEvents
(this=0x7f63080008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f63f0bc309a in QEventLoop::exec (this=this@entry=0x7f630e8d5d40,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f63f0a30584 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f63101a089f in KCupsConnection::run() () from
/usr/lib64/libkcupslib.so
#7  0x7f63f0a346fb in QThreadPrivate::start (arg=0x24a1480) at
thread/qthread_unix.cpp:368
#8  0x7f63ef8a634c in start_thread () from /lib64/libpthread.so.0
#9  0x7f63f02e539f in clone () from /lib64/libc.so.6

Thread 12 (Thread 0x7f6330196700 (LWP 13775)):
#0  0x7f63ebcac9d1 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f63ebc687f0 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f63ebc689fc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f63f0c0f44b in QEventDispatcherGlib::processEvents
(this=0x7f63280008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f63f0bc309a in QEventLoop::exec (this=this@entry=0x7f6330195d10,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f63f0a30584 in QThread::exec (this=this@entry=0x135ee60) at
thread/qthread.cpp:507
#6  0x7f63f38f4c76 in QQuickPixmapReader::run (this=0x135ee60) at
util/qquickpixmapcache.cpp:822
#7  0x7f63f0a346fb in QThreadPrivate::start (arg=0x135ee60) at
thread/qthread_unix.cpp:368
#8  0x7f63ef8a634c in start_thread () from /lib64/libpthread.so.0
#9  0x7f63f02e539f in clone () from /lib64/libc.so.6

Thread 11 (Thread 0x7f633b8ab700 (LWP 13767)):
#0  0x7f63ef8abf1f in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7f63478e6fb3 in cnd_wait (mtx=0xef0298, cond=0xef02c0) 

[kate] [Bug 378455] --block doesn't work

[Kåre Särs]

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

Kåre Särs  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #3 from Kåre Särs  ---
I think the problem is that having a GUI applicaton on Windows implicitly means
a virtual & at the end. Adding "| rem" after the command works like removing
the & on Linux (except you don't get stderr output).

--block is for when you have an instance already running and don't want to exit
the new instance until the old instance (that actually opens the provided file)
exits.

On Windows the new instance does not exit, but you don't notice it since the
"wise" shell automatically adds a virtual '2> /dev/null &' to all GUI
applications ;)

Adding "| rem" is a workaround, but I think we would need a patch/volunteer to
dig into the gory details of what special functions to call on windows to
prevent the virtual "...&" but at the same time not always open a
teminal-window.

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

[Akonadi] [Bug 283682] KMail duplicates filtered messages

[bugzilla_noreply]

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

--- Comment #185 from gra...@howlingfrog.com ---
(In reply to Martin Koller from comment #182)

Martin... if that's the case, then this "duplicates" issue would _only_ happen
for messages being auto-filtered, correct?  Instead, if messages were first
picked up and dropped into a folder and then _manually_ filtered, the events
would reorder such that the "trigger the filter, and move the msg" doesn't
happen until after the maildir resource had finished accepting the message.

(just wrapping my brain around it, and wanted to confirm that the above sounds
reasonable)

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

[okular] [Bug 378473] New: Medieval Sharp font does not print bold correctly

[bugzilla_noreply]

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

Bug ID: 378473
   Summary: Medieval Sharp font does not print bold correctly
   Product: okular
   Version: 0.26.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: printing
  Assignee: okular-de...@kde.org
  Reporter: phoeni...@gmail.com
  Target Milestone: ---

I am using to print a PDF from Google Docs for about a year or so. Recently,
headings using Medieval Sharp font do not print correctly, most of the letters
are printed as regular instead of bold - just a few are bold.

PDF looks OK when viewed and prints OK from Evince. I think it needs to be
recent, like month or two, but I cannot correlate the problem to any update.

I can provide the problematic PDF, but I would rather not do that publicly.

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

[kscreenlocker] [Bug 378445] kscreenlocker_greet occasionally freezes in malloc in signal handler

[bugzilla_noreply]

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

--- Comment #4 from r...@alum.mit.edu ---
I've installed the -debuginfo packages.  I'll update the bug the next time this
happens (which again is sporadic).

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

[kdenlive] [Bug 378472] New: suhtdown alone

[bellier]

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

Bug ID: 378472
   Summary: suhtdown alone
   Product: kdenlive
   Version: 15.12.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: bellier.cont...@gmail.com
  Target Milestone: ---

15.12.3
I cannot work, KDE shutdown all the time. Il's the first time it make this.

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

[ksnapshot] [Bug 210916] ksnapshot can lock up the screen when capturing context menu under the "region" mode, unless you use double clicking.

[Blucode]

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

--- Comment #14 from Blucode  ---
Ok I see:
https://www.kde.org/announcements/announce-applications-15.12.0.php

So the message is "forget Ksnapshot, move upward to Spectacle".

Thanks for the tip!

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

[kdevelop] [Bug 376149] KDevelop crash during background parsing code: assertion=assertion@entry=0x7ff1c72a0070 "DelayedTypos.empty() && \"Uncorrected typos!\"", file=file@entry=0x7ff1c729f9e8

[Kevin Funk]

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

--- Comment #12 from Kevin Funk  ---
Sorry, one remark missing: if you use -DCMAKE_BUILD_TYPE=Release or
...=RelWithDebInfo, NDEBUG will be defined.

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

[kwin] [Bug 378452] Escape key not detected by several games in wayland

[Martin Gräßlin]

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

--- Comment #5 from Martin Gräßlin  ---
(In reply to Rajdeep Nanua from comment #4)
> A short press and release.

meh, a long press I would have understood what goes on.

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

[kdevelop] [Bug 376149] KDevelop crash during background parsing code: assertion=assertion@entry=0x7ff1c72a0070 "DelayedTypos.empty() && \"Uncorrected typos!\"", file=file@entry=0x7ff1c729f9e8

[Kevin Funk]

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

--- Comment #11 from Kevin Funk  ---
assert() itself takes NDEBUG into account. In other words, if NDEBUG is defined
when assert.h is included, assert() does nothing.

See: http://en.cppreference.com/w/c/error/assert

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

[Powerdevil] [Bug 378471] New: Energy Saving ignore configuration!

[Rogério Queiroz]

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

Bug ID: 378471
   Summary: Energy Saving ignore configuration!
   Product: Powerdevil
   Version: 5.8.6
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-de...@kde.org
  Reporter: rogerio...@gmail.com
  Target Milestone: ---

Energy Saving, in tab On AC Power, even deselecting the Screen Energy Saving
option, the notebook enters lookScreen, so I have to enter my password again!
It is bad when in presentations with datashow for example.

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

[kwin] [Bug 354115] One of the screens stays blank after energy saving mode

[Rogério Queiroz]

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

Rogério Queiroz  changed:

   What|Removed |Added

 CC||rogerio...@gmail.com

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

[digikam] [Bug 372340] Tagged face areas on portait (vertical) oriented images are mispositioned

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||philsweene...@gmail.com

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

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

[digikam] [Bug 377628] CR2 file face detection misplaced in portrait

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

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

--- Comment #5 from Maik Qualmann  ---


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

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

[neon] [Bug 378454] KMail crashes on launch

[Thomas Dreibholz]

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

--- Comment #2 from Thomas Dreibholz  ---
It seems that some dependencies of Qt and/or KDEPIM are wrong for the Neon
dev/stable distribution:

See https://www.mail-archive.com/kde-bugs-dist@kde.org/msg129087.html

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

[neon] [Bug 378454] KMail crashes on launch

[Thomas Dreibholz]

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

Thomas Dreibholz  changed:

   What|Removed |Added

 CC||dre...@iem.uni-due.de

--- Comment #1 from Thomas Dreibholz  ---
I can confirm the bug for KDE Neon on Ubuntu 16.04 (x86_64):

...
org.kde.akonadi.ETM: Fetch job took  397 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 112
org.kde.akonadi.ETM: first fetched collection: "Lokale mapper"
org.kde.akonadi.ETM: collection: "[Gmail]"
org.kde.akonadi.ETM: collection: "Drafts"
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM: Fetch job took  475 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 7
org.kde.akonadi.ETM: first fetched collection: "Search"
org.kde.akonadi.ETM: Fetch job took  1697 msec
org.kde.akonadi.ETM: was item fetch job: items: 16119
org.kde.akonadi.ETM: Fetch job took  1710 msec
org.kde.akonadi.ETM: was item fetch job: items: 0
org.kde.akonadi.ETM: Fetch job took  1991 msec
org.kde.akonadi.ETM: was item fetch job: items: 22
org.kde.akonadi.ETM: Fetch job took  1962 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 0
kmail: symbol lookup error: /usr/lib/x86_64-linux-gnu/libKF5MessageCore.so.5:
undefined symbol: _ZNK5KMime5Types7Mailbox13prettyAddressEv

$ kmail --version
kmail2 5.4.3
$ apt-show-versions | grep kmail
kmail:amd64/xenial 4:16.12.3+p16.04+git20170310.0516-0 uptodate
$ apt-show-versions | grep libkf5messagecore
libkf5messagecore5:amd64/xenial 4:16.12.3+p16.04+git20170320.0112-0 uptodate

The bug appears since about 2 weeks now. It makes KMail unusable under current
KDE Neon (dev/stable).

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

[digikam] [Bug 372340] Tagged face areas on portait (vertical) oriented images are mispositioned

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||str...@blackdogit.co.uk

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

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

[digikam] [Bug 378456] When previewing faces the thumbnail preview is sometime sideways or not aligned to the face in question

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

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

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


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

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

[frameworks-kwidgetsaddons] [Bug 378276] Impossible to tell whether password field shows plaintext with empty content

[Elvis Angelaccio]

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

--- Comment #8 from Elvis Angelaccio  ---
I'm actually wondering if this is a bug in QLineEdit. The clear action is
always visible (isVisible() == true) even though is not...

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

[kdevelop] [Bug 376149] KDevelop crash during background parsing code: assertion=assertion@entry=0x7ff1c72a0070 "DelayedTypos.empty() && \"Uncorrected typos!\"", file=file@entry=0x7ff1c729f9e8

[Johannes Hirte]

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

Johannes Hirte  changed:

   What|Removed |Added

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

--- Comment #10 from Johannes Hirte  ---
(In reply to Kevin Funk from comment #9)
> Sorry, forget my previous comment. LLVM_ENABLE_ASSERTIONS:BOOL is only
> useful for *enabling* assertions, it won't help for *disabling* them.
> 
> If you want to disable assertions you need
> -DCMAKE_BUILD_TYPE=RelWithDebInfo, or -DCMAKE_BUILD_TYPE=Release. Just *not*
> -DCMAKE_BUILD_TYPE=Debug.

I've double checked this, assertions were disabled all the time. The assert
that fires here is this one:

Sema::~Sema() {
  if (VisContext) FreeVisContext();
  // Kill all the active scopes.
  for (unsigned I = 1, E = FunctionScopes.size(); I != E; ++I)
delete FunctionScopes[I];
  if (FunctionScopes.size() == 1)
delete FunctionScopes[0];

  // Tell the SemaConsumer to forget about us; we're going out of scope.
  if (SemaConsumer *SC = dyn_cast())
SC->ForgetSema();

  // Detach from the external Sema source.
  if (ExternalSemaSource *ExternalSema
= dyn_cast_or_null(Context.getExternalSource()))
ExternalSema->ForgetSema();

  // If Sema's ExternalSource is the multiplexer - we own it.
  if (isMultiplexExternalSource)
delete ExternalSource;

  threadSafety::threadSafetyCleanup(ThreadSafetyDeclCache);

  // Destroys data sharing attributes stack for OpenMP
  DestroyDataSharingAttributesStack();

  assert(DelayedTypos.empty() && "Uncorrected typos!");
}

This is not guarded by NDEBUG and will trigger unconditionally. So again the
question, is this a bug in clang/llvm or is kdevelop miss-using an interface?

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

[ark] [Bug 377648] Ark does not show some folders in RPM

[Elvis Angelaccio]

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

--- Comment #12 from Elvis Angelaccio  ---
(In reply to Fabian Vogt from comment #11)

> Ok: https://github.com/libarchive/libarchive/issues/899

Oh wait, I don't see `/usr/share/mime/multipart/` either. So even though I get
more folders than you, still they are just a subset of the total list of
files...

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

[frameworks-kwidgetsaddons] [Bug 378276] Impossible to tell whether password field shows plaintext with empty content

[Fabian Vogt]

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

--- Comment #7 from Fabian Vogt  ---
(In reply to Elvis Angelaccio from comment #6)
> Ok, it's a bit ugly but I think it's possible to work-around the empty space
> in my previous screenshot. Can you expand on the virtual keyboard argument?
> Why if I'm uisng a virtual keyboard I would want to always see the
> visibility icon in "plaintext" mode?

Not that, but you would not want to reset to hidden status after clearing the
input field.

> About the QML line edit, at least in the lock screen there is no clear
> button. No idea about other usages...

Just checked in plasma-nm, no clear button either.

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

[frameworks-kwidgetsaddons] [Bug 378276] Impossible to tell whether password field shows plaintext with empty content

[Elvis Angelaccio]

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

--- Comment #6 from Elvis Angelaccio  ---
Ok, it's a bit ugly but I think it's possible to work-around the empty space in
my previous screenshot. Can you expand on the virtual keyboard argument? Why if
I'm uisng a virtual keyboard I would want to always see the visibility icon in
"plaintext" mode?

About the QML line edit, at least in the lock screen there is no clear button.
No idea about other usages...

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

[ark] [Bug 377648] Ark does not show some folders in RPM

[Fabian Vogt]

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

Fabian Vogt  changed:

   What|Removed |Added

   See Also||https://github.com/libarchi
   ||ve/libarchive/issues/899

--- Comment #11 from Fabian Vogt  ---
(In reply to Elvis Angelaccio from comment #10)
> (In reply to Fabian Vogt from comment #9)
> > (In reply to Elvis Angelaccio from comment #8)
> > > Yes it's the gnome archiver. I asked you to try because they also use
> > > libarchive for rpm files and that would tell us whether the bug is in ark 
> > > or
> > > in libarchive. (fwiw, if I open it with file-roller it shows all the
> > > folders, as does ark).
> > 
> > Ok, tried it: Same issue. So it's in libarchive and there's nothing ark can
> > do, right?
> 
> Unfortunately yes. Try to report it upstream at
> https://github.com/libarchive/libarchive (and maybe link this report there)

Ok: https://github.com/libarchive/libarchive/issues/899

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

[ark] [Bug 377648] Ark does not show some folders in RPM

[Elvis Angelaccio]

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

--- Comment #10 from Elvis Angelaccio  ---
(In reply to Fabian Vogt from comment #9)
> (In reply to Elvis Angelaccio from comment #8)
> > Yes it's the gnome archiver. I asked you to try because they also use
> > libarchive for rpm files and that would tell us whether the bug is in ark or
> > in libarchive. (fwiw, if I open it with file-roller it shows all the
> > folders, as does ark).
> 
> Ok, tried it: Same issue. So it's in libarchive and there's nothing ark can
> do, right?

Unfortunately yes. Try to report it upstream at
https://github.com/libarchive/libarchive (and maybe link this report there)

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

[ark] [Bug 377648] Ark does not show some folders in RPM

[Fabian Vogt]

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

--- Comment #9 from Fabian Vogt  ---
(In reply to Elvis Angelaccio from comment #8)
> Yes it's the gnome archiver. I asked you to try because they also use
> libarchive for rpm files and that would tell us whether the bug is in ark or
> in libarchive. (fwiw, if I open it with file-roller it shows all the
> folders, as does ark).

Ok, tried it: Same issue. So it's in libarchive and there's nothing ark can do,
right?

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

[frameworks-kwidgetsaddons] [Bug 378276] Impossible to tell whether password field shows plaintext with empty content

[Fabian Vogt]

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

--- Comment #5 from Fabian Vogt  ---
(In reply to Elvis Angelaccio from comment #3)
> Created attachment 104893 [details]
> kdialog with echo-mode button always visible in plaintext mode
> 
> Unfortunately KPasswordDialog uses the clear button, so leaving the
> echo-mode button visible results in wasted space. Is this acceptable?

I would say yes, but that should be coordinated with the fix for bug 378277

(In reply to Elvis Angelaccio from comment #4)
> On the other hand, if we reset the visibility status we get the same level
> of "safety" without this visual glitch.

Yes, but that might be less useful for those with a virtual keyboard who
probably need the functionality the most.

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

[dolphin] [Bug 378470] New: Dolphin and several other programs crashed while formatting a USB stick with GParted

[bugzilla_noreply]

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

Bug ID: 378470
   Summary: Dolphin and several other programs crashed while
formatting a USB stick with GParted
   Product: dolphin
   Version: 16.08.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: danparkes2...@hotmail.com
  Target Milestone: ---

Application: dolphin (16.08.2)

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

-- Information about the crash:
- What I was doing when the application crashed:
Formatting a 16GB USB stick using GParted. Dolphin and several other programs -
including kdeinit or something similar - crashed, although GParted didn't, and
formatted the stick successfully. I now don't know how to check which programs
crashed but there were about four or five bug icons in the tray and my main
panel disappeared altogether for a second.

-- Backtrace:
Application: Dolphin (dolphin), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f94a022f900 (LWP 2532))]

Thread 4 (Thread 0x7f9477b98700 (LWP 2536)):
#0  0x7f949fada49d in poll () at /lib64/libc.so.6
#1  0x7f94947fd314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f94947fd42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f9499d5b32b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f9499d08fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f9499b43f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f9499b489e9 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f9495391744 in start_thread () at /lib64/libpthread.so.0
#8  0x7f949fae2d3d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f9485728700 (LWP 2534)):
#0  0x7f949fad651d in read () at /lib64/libc.so.6
#1  0x7f948fd2b073 in  () at /usr/lib64/tls/libnvidia-tls.so.375.39
#2  0x7f949483d670 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f94947fce49 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f94947fd2a8 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f94947fd42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#6  0x7f9499d5b32b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#7  0x7f9499d08fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#8  0x7f9499b43f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#9  0x7f949a1701d5 in  () at /usr/lib64/libQt5DBus.so.5
#10 0x7f9499b489e9 in  () at /usr/lib64/libQt5Core.so.5
#11 0x7f9495391744 in start_thread () at /lib64/libpthread.so.0
#12 0x7f949fae2d3d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f9487a60700 (LWP 2533)):
#0  0x7f949fada49d in poll () at /lib64/libc.so.6
#1  0x7f94926cc3e2 in  () at /usr/lib64/libxcb.so.1
#2  0x7f94926cdfcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f948a62a839 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f9499b489e9 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f9495391744 in start_thread () at /lib64/libpthread.so.0
#6  0x7f949fae2d3d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f94a022f900 (LWP 2532)):
[KCrash Handler]
#6  0x7f949fa2d8d7 in raise () at /lib64/libc.so.6
#7  0x7f949fa2ecaa in abort () at /lib64/libc.so.6
#8  0x7f9499b3437e in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f949a1a2ae2 in  () at /usr/lib64/libQt5DBus.so.5
#10 0x7f9499d461c4 in  () at /usr/lib64/libQt5Core.so.5
#11 0x7f9499d473cf in QVariant::QVariant(int, void const*) () at
/usr/lib64/libQt5Core.so.5
#12 0x7f9499d17532 in QMetaProperty::read(QObject const*) const () at
/usr/lib64/libQt5Core.so.5
#13 0x7f9499d3408c in QObject::property(char const*) const () at
/usr/lib64/libQt5Core.so.5
#14 0x7f949d65ac8c in  () at /usr/lib64/libKF5Solid.so.5
#15 0x7f949d65aee3 in  () at /usr/lib64/libKF5Solid.so.5
#16 0x7f949d6559f1 in  () at /usr/lib64/libKF5Solid.so.5
#17 0x7f949d66c629 in  () at /usr/lib64/libKF5Solid.so.5
#18 0x7f949d669d45 in  () at /usr/lib64/libKF5Solid.so.5
#19 0x7f949d653a10 in  () at /usr/lib64/libKF5Solid.so.5
#20 0x7f949d61a3f8 in
Solid::Device::asDeviceInterface(Solid::DeviceInterface::Type const&) const ()
at /usr/lib64/libKF5Solid.so.5
#21 0x7f949d8dd852 in  () at /usr/lib64/libKF5Baloo.so.5
#22 0x7f949d8dde5d in  () at /usr/lib64/libKF5Baloo.so.5
#23 0x7f9499d351c3 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#24 0x7f949d61aac2 in Solid::DeviceNotifier::deviceAdded(QString const&) ()
at /usr/lib64/libKF5Solid.so.5
#25 0x7f949d61c86f in  

[kdevelop] [Bug 378419] "Locate current document in project" button in project view not working

[Frank Souza]

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

--- Comment #6 from Frank Souza  ---
I've figure it out: symbolic links. The major part of my php files are sym
links from a base project. Now I don't know if this a bug or expected. That's
why I'll not mark as resolved until someone confirm. Thanks everyone!

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

[frameworks-sonnet] [Bug 377933] Error building under macOS

[Yurii Kolesnykov]

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

--- Comment #4 from Yurii Kolesnykov  ---
>Does it only happen for kf5-sonnet for you?
Yes, as I see now, I had built a lot of kf5 packages in recent.

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

[frameworks-sonnet] [Bug 377933] Error building under macOS

[Kevin Funk]

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

--- Comment #3 from Kevin Funk  ---
Does it only happen for kf5-sonnet for you?

Since this is an issue in a central Qt header:
/usr/local/opt/qt5/include/QtCore/qlist.h:468:13: error: cannot use 'throw'
with exceptions disabled
QT_RETHROW;
^

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

[frameworks-sonnet] [Bug 377933] Error building under macOS

[Kevin Funk]

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

Kevin Funk  changed:

   What|Removed |Added

 CC||rjvber...@gmail.com

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

[frameworks-sonnet] [Bug 377933] Error building under macOS

[Kevin Funk]

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

--- Comment #2 from Kevin Funk  ---
Bug in extra-cmake-modules I suppose.

>From kde-modules/KDECompilerSettings.cmake:
```
...

# TODO: Deal with QT_NO_EXCEPTIONS for non-gnu compilers?
#   This should be defined if and only if exceptions are disabled.
#   qglobal.h has some magic to set it when exceptions are disabled
#   with gcc, but other compilers are unaccounted for.

# Turn off exceptions by default
if(CMAKE_CXX_COMPILER_ID STREQUAL "GNU")
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -fno-exceptions")
elseif(CMAKE_CXX_COMPILER_ID MATCHES "Clang")
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -fno-exceptions")
...
```

This looks suspicious. Sounds like you need to define QT_NO_EXCEPTIONS
yourself?

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

[frameworks-kwidgetsaddons] [Bug 378276] Impossible to tell whether password field shows plaintext with empty content

[Elvis Angelaccio]

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

--- Comment #4 from Elvis Angelaccio  ---
On the other hand, if we reset the visibility status we get the same level of
"safety" without this visual glitch.

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

[valgrind] [Bug 359202] Add musl libc configure/compile

[Ivo Raisr]

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

Ivo Raisr  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 CC||iv...@ivosh.net
 Ever confirmed|0   |1

--- Comment #5 from Ivo Raisr  ---
No objections here.

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

[frameworks-sonnet] [Bug 377933] Error building under macOS

[Yurii Kolesnykov]

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

Yurii Kolesnykov  changed:

   What|Removed |Added

Version|unspecified |5.32.0

--- Comment #1 from Yurii Kolesnykov  ---
Same problem with 5.32 and master
5.32 https://gist.github.com/ea66503e9f0025ff3fee542acd682f70
head https://gist.github.com/920b055910f0d360bcf5d5487f385be1

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

[frameworks-kwidgetsaddons] [Bug 378276] Impossible to tell whether password field shows plaintext with empty content

[Elvis Angelaccio]

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

--- Comment #3 from Elvis Angelaccio  ---
Created attachment 104893
  --> https://bugs.kde.org/attachment.cgi?id=104893=edit
kdialog with echo-mode button always visible in plaintext mode

Unfortunately KPasswordDialog uses the clear button, so leaving the echo-mode
button visible results in wasted space. Is this acceptable?

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

[kmymoney4] [Bug 378435] Crash when open .kmy file

[bugzilla_noreply]

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

--- Comment #3 from tr@gmx.de ---
(gdb) backtrace
#0  0x71f67fdf in raise () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x71f6940a in abort () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x71f60e47 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#3  0x71f60ef2 in __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
#4  0x7fffdbec5d2f in GWEN_Buffer_AppendString () from
/usr/lib/libgwenhywfar.so.60
#5  0x7fffdb803661 in ?? () from /usr/lib/libaqbanking.so.35
#6  0x7fffdc78a2ee in ?? () from /usr/lib/kde4/kmm_kbanking.so
#7  0x76263e2a in onlineJobAdministration::canSendCreditTransfer() ()
from /usr/lib/libkmm_mymoney.so.4
#8  0x55651dc7 in ?? ()
#9  0x55658680 in ?? ()
#10 0x5569dcc5 in ?? ()
#11 0x72f92660 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#12 0x761ea808 in MyMoneyFile::attachStorage(IMyMoneyStorage*) () from
/usr/lib/libkmm_mymoney.so.4
#13 0x556c2378 in ?? ()
#14 0x556841c3 in ?? ()
#15 0x55684f6d in ?? ()
#16 0x5569e02d in ?? ()
#17 0x72f92660 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#18 0x7399b672 in QAction::triggered(bool) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#19 0x7399c9d3 in QAction::activate(QAction::ActionEvent) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#20 0x72f98381 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#21 0x7399ce92 in QAction::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#22 0x74635912 in KAction::event(QEvent*) () from
/usr/lib/libkdeui.so.5
#23 0x739a154c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#24 0x739a852c in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#25 0x747201ba in KApplication::notify(QObject*, QEvent*) () from
/usr/lib/libkdeui.so.5
#26 0x72f7df1d in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#27 0x72f81a16 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#28 0x72fae703 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#29 0x7fffed72a7f7 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x7fffed72aa60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#31 0x7fffed72ab0c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#32 0x72fae854 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#33 0x73a4b5d6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#34 0x72f7c7ef in
QEventLoop::processEvents(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#35 0x72f7cb55 in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#36 0x72f82bd9 in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#37 0x5563a95d in ?? ()
#38 0x55637a82 in ?? ()
#39 0x71f552b1 in __libc_start_main () from
/lib/x86_64-linux-gnu/libc.so.6
#40 0x5563a0ca in _start ()

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

[kdenlive] [Bug 378469] 17.04 - Crash on Exit

[Paul Konecny]

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

Paul Konecny  changed:

   What|Removed |Added

  Component|general |Video Display & Export
 CC||p...@konecny.at
Version|unspecified |git-master
   Platform|unspecified |Compiled Sources
Product|kde |kdenlive

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

[kmymoney4] [Bug 378435] Crash when open .kmy file

[bugzilla_noreply]

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

--- Comment #2 from tr@gmx.de ---
I'm not familiar with gdb but I hope this is what you are need!?  

Starting program: /usr/bin/kmymoney 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
kmymoney(2522)/kdecore (KPluginInfo) KPluginInfo::kcmServices: found 0 offers
for "csvexport"
kmymoney(2522)/kdecore (KPluginInfo) KPluginInfo::kcmServices: found 1 offers
for "Print check"
kmymoney(2522)/kdecore (KPluginInfo) KPluginInfo::kcmServices: found 0 offers
for "National orders for online banking"
kmymoney(2522)/kdecore (KPluginInfo) KPluginInfo::kcmServices: found 0 offers
for "KMyMoney OFX"
kmymoney(2522)/kdecore (KPluginInfo) KPluginInfo::kcmServices: found 1 offers
for "iCalendar"
kmymoney(2522)/kdecore (KPluginInfo) KPluginInfo::kcmServices: found 0 offers
for "SEPA orders for online banking"
kmymoney(2522)/kdecore (KPluginInfo) KPluginInfo::kcmServices: found 0 offers
for "csvimport"
kmymoney(2522)/kdecore (KPluginInfo) KPluginInfo::kcmServices: found 0 offers
for "KBanking"
kmymoney(2522)/kdecore (KPluginInfo) KPluginInfo::kcmServices: found 0 offers
for "Reconciliation report"
kmymoney(2522)/kdecore (KPluginInfo) KPluginInfo::kcmServices: found 0 offers
for "Weboob"
KMyMoney csvexport plugin loaded
KMyMoney printcheck plugin loaded
kmymoney(2522)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
QFSFileEngine::open: No file name specified
onlineTask available "org.kmymoney.creditTransfer.germany" 
onlineTaskConverter available "org.kmymoney.creditTransfer.germany"
("org.kmymoney.creditTransfer.sepa") 
onlineTaskConverter available "org.kmymoney.creditTransfer.sepa"
("org.kmymoney.creditTransfer.germany") 
KMyMoney ofximport plugin loaded
KMyMoney iCalendar plugin loaded
onlineTask available "org.kmymoney.creditTransfer.sepa" 
KMyMoney csvimport plugin loaded
KMyMoney kbanking plugin loaded
KMyMoney reconciliation report plugin loaded
[New Thread 0x7fffd53df700 (LWP 2526)]
[New Thread 0x7fffc700 (LWP 2527)]
kmymoney(2522) KSambaSharePrivate::findSmbConf: KSambaShare: Could not find
smb.conf! 
[Thread 0x7fffd53df700 (LWP 2526) exited]
reading file
start parsing file
startDocument
reading accounts
reading transactions
reading securities
reading currencies
reading prices
reading reports
endDocument
kmymoney: buffer.c:1017: GWEN_Buffer_AppendString: Zusicherung »buffer« nicht
erfüllt.

Thread 1 "kmymoney" received signal SIGABRT, Aborted.
0x71f67fdf in raise () from /lib/x86_64-linux-gnu/libc.so.6

I use debian testing and updated with aptitude so the depending packages should
be updated too. libaqbanking 5.6.12-1+1b; libgwenhywfar-data 4.15.3-5

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

[kde] [Bug 378469] New: 17.04 - Crash on Exit

[Paul Konecny]

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

Bug ID: 378469
   Summary: 17.04 - Crash on Exit
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: p...@konecny.at
  Target Milestone: ---

Application: kdenlive (17.03.80)
 (Compiled from sources)
Qt Version: 5.8.0
Frameworks Version: 5.32.0
Operating System: Linux 4.10.6-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
Kdenlive always crashes on close. 
Branch 17.04 up until commit 80e0b44f18fe9def3620b189eeb43e96a26698b7

The crash can be reproduced every time.

-- Backtrace:
Application: Kdenlive (kdenlive), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff88a100800 (LWP 20719))]

Thread 13 (Thread 0x7ff822ffd700 (LWP 20789)):
#0  0x7ff882c914e5 in  () at /usr/lib/libQt5Core.so.5
#1  0x7ff879e66c8d in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7ff879e676cb in  () at /usr/lib/libglib-2.0.so.0
#3  0x7ff879e678bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7ff882c9206b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7ff882c3b89a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7ff882a5da73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7ff882a626d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7ff88008f2e7 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7ff88206254f in clone () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7ff823fff700 (LWP 20787)):
#0  0x7ff879eace49 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7ff879e67326 in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#2  0x7ff879e67810 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7ff879e678bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7ff882c9206b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7ff882c3b89a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7ff882a5da73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7ff882a626d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7ff88008f2e7 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7ff88206254f in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7ff83270c700 (LWP 20734)):
#0  0x7ff88205867d in poll () at /usr/lib/libc.so.6
#1  0x7ff879e677a6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7ff879e678bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7ff882c9206b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7ff882c3b89a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7ff882a5da73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7ff88468e025 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7ff882a626d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7ff88008f2e7 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7ff88206254f in clone () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7ff8333ef700 (LWP 20731)):
#0  0x7ff880095b63 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7ff882a634c6 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7ff882a5ebc4 in  () at /usr/lib/libQt5Core.so.5
#3  0x7ff882a626d8 in  () at /usr/lib/libQt5Core.so.5
#4  0x7ff88008f2e7 in start_thread () at /usr/lib/libpthread.so.0
#5  0x7ff88206254f in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7ff8343f0700 (LWP 20730)):
#0  0x7ff88205867d in poll () at /usr/lib/libc.so.6
#1  0x7ff879e677a6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7ff879e678bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7ff882c9206b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7ff882c3b89a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7ff882a5da73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7ff88468e025 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7ff882a626d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7ff88008f2e7 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7ff88206254f in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7ff840589700 (LWP 20729)):
#0  0x7ff88205867d in poll () at /usr/lib/libc.so.6
#1  0x7ff8471abd51 in  () at /usr/lib/libusb-1.0.so.0
#2  0x7ff88008f2e7 in start_thread () at /usr/lib/libpthread.so.0
#3  0x7ff88206254f in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7ff86031d700 (LWP 20727)):
#0  0x7ff88205867d in poll () at 

[ark] [Bug 377648] Ark does not show some folders in RPM

[Elvis Angelaccio]

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

--- Comment #8 from Elvis Angelaccio  ---
Yes it's the gnome archiver. I asked you to try because they also use
libarchive for rpm files and that would tell us whether the bug is in ark or in
libarchive. (fwiw, if I open it with file-roller it shows all the folders, as
does ark).

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

[ark] [Bug 377648] Ark does not show some folders in RPM

[Fabian Vogt]

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

--- Comment #7 from Fabian Vogt  ---
(In reply to Elvis Angelaccio from comment #6)
> What if you open the archive with file-roller?

What is that? The gnome app? I do not have that installed here and I don't want
to.

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

[ark] [Bug 377648] Ark does not show some folders in RPM

[Elvis Angelaccio]

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

--- Comment #6 from Elvis Angelaccio  ---
What if you open the archive with file-roller?

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

[krita] [Bug 368952] Full screen does not restore to maximized correctly on Windows

[cheteron]

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

--- Comment #15 from cheteron  ---
https://youtu.be/8sJNQd6oA28

1) Fullscreen - tab-tab
2) fullscreen off - tab-tab

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

[kmail2] [Bug 378280] Add button to insert pre tag

[Laurent Montel]

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

--- Comment #5 from Laurent Montel  ---
it's possible now :)
But yep I will look at how I can do it.

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

[dolphin] [Bug 378462] Crash when copy a pdf's file between two open tabs

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||elvis.angelac...@kde.org
Summary|Crash when copy a pdf's |Crash when copy a pdf's
   |file.   |file between two open tabs

--- Comment #1 from Elvis Angelaccio  ---
Possibly a duplicate of bug 368199, even though the backtrace is different.

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

[digikam] [Bug 353331] can’t limit fuzzy-search to albums

[Mario Frank]

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

Mario Frank  changed:

   What|Removed |Added

 Attachment #104874|0   |1
is obsolete||

--- Comment #18 from Mario Frank  ---
Created attachment 104892
  --> https://bugs.kde.org/attachment.cgi?id=104892=edit
Updated patch for improvements

The new patch adds patches for 
https://bugs.kde.org/show_bug.cgi?id=183425
and
https://bugs.kde.org/show_bug.cgi?id=300565

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

[krita] [Bug 368952] Full screen does not restore to maximized correctly on Windows

[cheteron]

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

--- Comment #14 from cheteron  ---
I always use portable version.

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

[digikam] [Bug 300565] When selecting folders, subfolders are not selected

[Mario Frank]

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

Mario Frank  changed:

   What|Removed |Added

 CC||mario.fr...@uni-potsdam.de

--- Comment #6 from Mario Frank  ---
In https://bugs.kde.org/show_bug.cgi?id=353331 ,
a patch will be submitted that introduces context menus for album and tag
selection where subtrees can be marked explicitly. With the patch, subtrees are
not used automatically. The user can decide himself.

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

[digikam] [Bug 183425] Advanced search by tags : "any tags" option does not work

[Mario Frank]

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

Mario Frank  changed:

   What|Removed |Added

 CC||mario.fr...@uni-potsdam.de

--- Comment #20 from Mario Frank  ---
Created attachment 104891
  --> https://bugs.kde.org/attachment.cgi?id=104891=edit
Draft for applicable operations on chosen tags in extended search

For tags, the user can select if the images to find must be in all the chosen
tags or at least in one.

The patch will be uploaded here: https://bugs.kde.org/show_bug.cgi?id=353331

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

[kwin] [Bug 378452] Escape key not detected by several games in wayland

[Rajdeep Nanua]

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

--- Comment #4 from Rajdeep Nanua  ---
A short press and release.

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