[kdenlive] [Bug 363951] Keeps randomly crashing (segfault) by just using it every couple of minutes

[Wegwerf via KDE Bugzilla]

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

--- Comment #5 from Wegwerf  ---
Roland, thank you for your information.

1)  Agreed. However, there is no reason for masking MLT 6.0.x as this is a rock
solid release. And it has the ugly titler crash finally fixed. But, as you
said, that's of no concern for the moment.

2) The XCB errors usually can be ignored, they are seen on many systems and
seem to stem from Qt. When you run your self-compiled Kdenlive (from build/src)
under gdb control then KCrash should not interfere. This is what I experience
on my Kubuntu 16.04 installation.

What kind of graphics card and drivers do you use? Kdenlive requires OpenGL.
Did you disable movit, the GPU acceleration support in Kdenlive? In case you
should have it enabled, can you please disable it? Also, can you please make
sure that you've set processing threads set to 1 in Kdenlive's configure
dialog?

And what is also strange: I'm on a Kubuntu 16.04 stock installation, but have
compiled my own Kdenlive from (bleeding) git master, as well as MLT, and
ffmpeg. This has proven to be a solid combination independent of any distro
woes. The stock components are Qt5 and KF5, as well as X11 and the graphics
card driver -- which is the open source AMD Radeon driver with an HD 7700/7800.
But unfortunately, you are seeing a lot of crashes on your system.

So this brings me to the last question I can ask: what kind of system do you
have? Did you experience any other odd system behavior that may hint at a
faulty RAM bank or similar? Does other graphics-heavy software, such as
Blender, Natron, GIMP with large images, work correctly? If yes, this then can
probably safely wipe out RAM woes.

To be honest, I'm dazzled...

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

[krita] [Bug 363980] Whenever i open Krita 3.0 it doesn't show anything.

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID
 CC||b...@valdyas.org

--- Comment #2 from Boudewijn Rempt  ---
Hi, this isn't a bug: it's the canvas only mode. Press ctrl-n to get the new
image dialog, create a new image and press tab to restore the dockers and
toolbar. If that doesn't work, remove %APPDATA%\Local\krita.

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

[kdenlive] [Bug 363989] git master: project bin sorts items in reverse order after each new Kdenlive start

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

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

--- Comment #2 from Wegwerf  ---
Works here too now. Thank you very much for fixing this!

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

[kontact] [Bug 364010] New: Kontact crashed on close

[Gabriel Rüeck via KDE Bugzilla]

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

Bug ID: 364010
   Summary: Kontact crashed on close
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: gabr...@rueeck.de

Application: kontact (4.14.10)
KDE Platform Version: 4.14.9
Qt Version: 4.8.6
Operating System: Linux 3.16.7-35-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
I was closing Kontact with the "X" button on the top right of ther window. When
I closed, I had been in the KMail application. Previously, I had also been in
the Akregator application.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fca2f1eb800 (LWP 13509))]

Thread 4 (Thread 0x7fca0fde4700 (LWP 13511)):
#0  0x7fca267ad03f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fca29f53686 in WTF::TCMalloc_PageHeap::scavengerThread() () from
/usr/lib64/libQtWebKit.so.4
#2  0x7fca29f536b9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) ()
from /usr/lib64/libQtWebKit.so.4
#3  0x7fca267a90a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7fca2c73600d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fca0f4c3700 (LWP 13512)):
#0  0x7fca267ad03f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fca29cc5e7d in JSC::BlockAllocator::blockFreeingThreadMain() () from
/usr/lib64/libQtWebKit.so.4
#2  0x7fca29f7b1e6 in WTF::wtfThreadEntryPoint(void*) () from
/usr/lib64/libQtWebKit.so.4
#3  0x7fca267a90a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7fca2c73600d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fc9bc9a9700 (LWP 13562)):
#0  0x7fca2c72dbdd in poll () from /lib64/libc.so.6
#1  0x7fca261ddbe4 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fca261ddcec in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fca2ceb10de in QEventDispatcherGlib::processEvents
(this=0x7fc9b8e0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x7fca2ce82e6f in QEventLoop::processEvents
(this=this@entry=0x7fc9bc9a8de0, flags=...) at kernel/qeventloop.cpp:149
#5  0x7fca2ce83165 in QEventLoop::exec (this=this@entry=0x7fc9bc9a8de0,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7fca2cd800bf in QThread::exec (this=) at
thread/qthread.cpp:538
#7  0x7fca2cd8279f in QThreadPrivate::start (arg=0x1833260) at
thread/qthread_unix.cpp:349
#8  0x7fca267a90a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7fca2c73600d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fca2f1eb800 (LWP 13509)):
[KCrash Handler]
#5  ref (this=0x0) at ../../src/corelib/arch/qatomic_x86_64.h:121
#6  QList (l=..., this=0x7ffc5059dbf0) at ../../src/corelib/tools/qlist.h:122
#7  QItemSelection (this=0x7ffc5059dbf0) at itemviews/qitemselectionmodel.h:231
#8  QItemSelectionModel::selectedIndexes (this=0x3526eb0) at
itemviews/qitemselectionmodel.cpp:1433
#9  0x7fc9c686b8c3 in MailCommon::FolderTreeWidget::selectedCollections()
const () from /usr/lib64/libmailcommon.so.4
#10 0x7fc9c7840f4d in KMMainWidget::updateFolderMenu() () from
/usr/lib64/libkmailprivate.so.4
#11 0x7fc9c792833a in ?? () from /usr/lib64/libkmailprivate.so.4
#12 0x7fca2ce981fa in QMetaObject::activate (sender=0x1bc84b0, m=, local_signal_index=, argv=0x0) at kernel/qobject.cpp:3576
#13 0x7fca2ce9c3b1 in QObject::event (this=0x1bc84b0, e=) at
kernel/qobject.cpp:1193
#14 0x7fca2d89276c in QApplicationPrivate::notify_helper
(this=this@entry=0x14ebf30, receiver=receiver@entry=0x1bc84b0,
e=e@entry=0x7ffc5059e510) at kernel/qapplication.cpp:4565
#15 0x7fca2d898cad in QApplication::notify (this=0x7ffc5059f1c0,
receiver=0x1bc84b0, e=0x7ffc5059e510) at kernel/qapplication.cpp:4351
#16 0x7fca2e5aae0a in KApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libkdeui.so.5
#17 0x7fca2ce842ad in QCoreApplication::notifyInternal
(this=0x7ffc5059f1c0, receiver=0x1bc84b0, event=0x7ffc5059e510) at
kernel/qcoreapplication.cpp:953
#18 0x7fca2ceb3cbc in sendEvent (event=, receiver=) at kernel/qcoreapplication.h:231
#19 QTimerInfoList::activateTimers (this=0x14e4a60) at
kernel/qeventdispatcher_unix.cpp:636
#20 0x7fca2ceb0f01 in timerSourceDispatch (source=) at
kernel/qeventdispatcher_glib.cpp:193
#21 0x7fca261dda04 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#22 0x7fca261ddc48 in ?? () from /usr/lib64/libglib-2.0.so.0
#23 0x7fca261ddcec in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#24 0x7fca2ceb10be in QEventDispatcherGlib::pr

[krita] [Bug 364003] Calligrapha and freehand paint icons are too similar

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

Summary|Freehand Brush Tool next to |Calligrapha and freehand
   |Calligraphy Tool leads to   |paint icons are too similar
   |confusion   |
 CC||b...@valdyas.org
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Boudewijn Rempt  ---
Actually, the layout didn't change -- but we did get new, consistent icons.
These two are a bit on the similar side, though.

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

[kdenlive] [Bug 353251] 1 video 2 audio tracks muted audio 2 kills audio 1

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

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

--- Comment #8 from Wegwerf  ---
Jean-Baptiste, as you mentioned possible add track corruption: with your recent
changes incorporated I still see problems after adding a track using the
"Insert Track" context menu from the track headers.

My project setup: V4, V3, V2, V1, A1, A2

It's probably important that there are audio clips on A1.

Now, when I insert a new audio track (A0) above A1 the following happens:
* A0 gets inserted between V1 and A1 -- as it should be.
* all audio clips from A1 are now shown on A0 -- albeit they will be correctly
saved as belonging to A1, so after reloading the project all is fine.
* I can see that A2 is still there, but on my setup it gets clipped and the
timeline does not show any vertical scrollbar.

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

[kdenlive] [Bug 363813] Problems with buttons on Ubuntu 16.04

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

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

--- Comment #1 from Wegwerf  ---
Robert,

as you are on Ubuntu, but not on Kubuntu, that may be due to the required icon
sets not getting installed. Can you please install also the Breeze icon themes?

On a sidenote, please consider upgrading to Kdenlive 16.04.1; it's available
from the stable ppa, ppa:kdenlive/kdenlive-stable -- I've just checked to be
sure. Please use the testing ppa only if you have good reason to do so. I'm not
even going to mention the git master ppa here for some good reason :)

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

[kdenlive] [Bug 363813] Problems with buttons on Ubuntu 16.04

[Robert Orzanna via KDE Bugzilla]

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

--- Comment #2 from Robert Orzanna  ---
Thank you very much for your help!

Indeed now the buttons are shown after installing kde-runtime which seems to
provide the right icons. 

Moreover I made sure to have installed version 16.04.1.

However, the official website states that users should install testing and not
stable:

https://kdenlive.org/download-ubuntu

Can you confirm this?

Thankfully,

~Robert

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

[ktouch] [Bug 364011] New: Unable to switch from QWERTY, when using a different hardware layout

[Gergely Nagy via KDE Bugzilla]

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

Bug ID: 364011
   Summary: Unable to switch from QWERTY, when using a different
hardware layout
   Product: ktouch
   Version: 2.3.0
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: sebastiangottfr...@web.de
  Reporter: k...@gergo.csillger.hu

I am using an ErgoDox EZ, a programmable keyboard. My OS is set to a QWERTY
layout, but my keyboards sends the keycodes according to the
Dvorak/Capewell-Dvorak layout. That is, if I press the key that's in the Q
position on QWERTY, the keyboard will send the ' key instead.

Since I am experimenting with custom layouts, that even my OS does not have
built-in support for, I do not wish to set my hardware to QWERTY *and* create a
software layout, just so I can use KTouch.

Please make it possible to override the auto-detected keyboard layout, so those
of us with QWERTY OS layout, but a different one in hardware, can still use the
program.

Reproducible: Always

Steps to Reproduce:
1. Plug in any keyboard that has a non-QWERTY hardware layout.
2. Set your OS layout to QWERTY.
3. Launch KTouch.

Actual Results:  
KTouch detects the QWERTY layout, and does not let me switch to a custom one.

Expected Results:  
The software should have let me select the layout I want, the one my hardware
uses, instead of guessing it from the OS layout.

For this use case, the severity is grave, because the program is completely
unusable when I'm forced into QWERTY. All I need is a simple menu that lets me
choose a layout - I already created the layout in ktouch, along with the
lessons.

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

[kwin] [Bug 358369] Plasma crashed after opening an HTML5 video in Chrome

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

 CC||ste...@actuallythere.com

--- Comment #23 from Thomas Lübking  ---
*** Bug 364008 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 364008] Opened Dolphin and clicked on a directory in my home directory. Single click is enabled.

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

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

--- Comment #1 from Thomas Lübking  ---
"kcmshell5 kwindecoration", switch to breeze.

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

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

[kwin] [Bug 356740] Kwin crash if I set brightness while in kodi

[Côme Chilliet via KDE Bugzilla]

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

--- Comment #8 from Côme Chilliet  ---
Ok, so it does not crash anymore when I set brightness while in Kodi, which is
good, but the behaviour is still weird:

Each time I increase or decrease brightness, the plasma taskbar is shown a
brief moment, so when increasing several time it feels as the screen is
flickering, as it shows kodi and plasma desktop several time each in a few
seconds.
I don’t have this problem when increasing or decreasing audio volume, I only
get the KDE volume indicator on top of Kodi (which does not indicate much
anymore as both bar colors are almost the same but I should open a bug ticket
on breeze for this I guess).
I would like the same for brightness, the brightness indicator at the center
only above kodi, no flickering with plasma desktop or taskbar.

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

[kdenlive] [Bug 364012] New: git master: optimization for loading existing preview render chunks may conflict with change clip invalidation

[Wegwerf via KDE Bugzilla]

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

Bug ID: 364012
   Summary: git master: optimization for loading existing preview
render chunks may conflict with change clip
invalidation
   Product: kdenlive
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: wegwerf-1-...@gmx.de

With the most recent git master I now see that after reloading a clip (such as
a slideshow clip) the corresponding timeline parts get properly invalidated.
However, upon clicking the preview render button (automatic rendering is off)
the stale and now invalid chunks get quickly picked up and the affected zone
turns green without properly rerendering it. At the moment, I need to unset
this zone first, then set it again, in order to correctly rerender it.

Reproducible: Always

Steps to Reproduce:
0. Make sure that automatic preview rendering is turned off.
1. Create new project.
2. Add slideshow clip to project (title clip may also work).
3. Place the slideshow clip on the timeline.
4. Render preview for zone of slideshow clip. Wait for rendering to complete.
5. Reload slideslow clip. Affected timeline zone should turn red.
6. Click on preview render button.

Actual Results:  
Affected timeline zone quickly turns green without rerendering the affected
zone.

Expected Results:  
Affected timeline zone should be rerendered instead of reusing the old and
stale preview chunks.

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

[kdenlive] [Bug 364012] git master: optimization for loading existing preview render chunks may conflict with change clip invalidation

[Wegwerf via KDE Bugzilla]

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

--- Comment #1 from Wegwerf  ---
By the way: on the other hand, reloading a project after a full preview render
starts with the old preview rendering zone being red. Kdenlive does not pick up
the existing preview chunks. Could that be because I saved the project after
preview rendering again?

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

[kdenlive] [Bug 364012] git master: optimization for loading existing preview render chunks may conflict with change clip invalidation

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #2 from Jean-Baptiste Mardelle  ---
I will check this problem tonight. Regarding your second comment, currently we
proceed like this on project opening:

We check the project file's last save date/time and compare it with preview
chunks date/time. If a chunk is more recent than the project date, we delete it
(in case user played with the project but decided not to save the changes). So
if you don't save your project after preview rendering is finished, these new
chunks will be deleted.

However in my quick tests, I frequently forgot to save just because of the
timeline preview, so maybe we can find a more clever approach than comparing
dates, something like a hash of the project file so that chunks newer than
project file are not deleted if the project has not changed... will look into
it.

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

[kaffeine] [Bug 363869] It is not possible to stop kaffeine aplication nor possible to kill the kaffeine process.

[David Geiger via KDE Bugzilla]

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

David Geiger  changed:

   What|Removed |Added

 CC||geiger.david68...@gmail.com

--- Comment #5 from David Geiger  ---
Same issue here on Mageia with latest 2.0.1 release from:

http://download.kde.org/stable/kaffeine/2.0.1/src/kaffeine-2.0.1-1.tar.bz2

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

[kaffeine] [Bug 363869] It is not possible to stop kaffeine aplication nor possible to kill the kaffeine process.

[Nicolas L . via KDE Bugzilla]

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

Nicolas L.  changed:

   What|Removed |Added

 CC||k...@nicolaslecureuil.fr

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

[Baloo] [Bug 364013] New: Crash with Virtual Box opening

[Nick via KDE Bugzilla]

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

Bug ID: 364013
   Summary: Crash with Virtual Box opening
   Product: Baloo
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: m...@vhanda.in
  Reporter: nicola.urba...@gmail.com
CC: pinak.ah...@gmail.com

Application: baloo_file (5.15.0)

Qt Version: 5.4.2
Operating System: Linux 4.2.0-36-generic x86_64
Distribution: Ubuntu 15.10

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

- Unusual behavior I noticed:
Virtual Box start, and then appears crash baloo, but all applications seems to
continue running.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135
[Current thread is 1 (Thread 0x7f98bcda5800 (LWP 1455))]

Thread 2 (Thread 0x7f9771f3f700 (LWP 2390)):
[KCrash Handler]
#6  0x7f98bae2d1c7 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:55
#7  0x7f98bae2ee2a in __GI_abort () at abort.c:89
#8  0x7f98b96421b2 in mdb_assert_fail (env=0x897c90,
expr_txt=expr_txt@entry=0x7f98b964e1cf "rc == 0",
func=func@entry=0x7f98b964eac5 <__FUNCTION__.6980> "mdb_page_dirty",
line=line@entry=1945, file=0x7f98b964e1b0 "mdb.c") at mdb.c:1369
#9  0x7f98b96425f5 in mdb_page_dirty (txn=0x96f060, mp=) at
mdb.c:1945
#10 0x7f98b96437cb in mdb_page_alloc (num=num@entry=1,
mp=mp@entry=0x7f9771f3e158, mc=0x7f9771f3e690) at mdb.c:2126
#11 0x7f98b9643a29 in mdb_page_touch (mc=mc@entry=0x7f9771f3e690) at
mdb.c:2244
#12 0x7f98b964563f in mdb_cursor_touch (mc=mc@entry=0x7f9771f3e690) at
mdb.c:6086
#13 0x7f98b964827a in mdb_cursor_put (mc=0x7f9771f3e690,
key=0x7f9771f3ea80, data=0x7f9771f3ea90, flags=) at mdb.c:6221
#14 0x7f98b964ab29 in mdb_put (txn=, dbi=,
key=key@entry=0x7f9771f3ea80, data=data@entry=0x7f9771f3ea90,
flags=flags@entry=0) at mdb.c:8395
#15 0x7f98bbf9951d in Baloo::DocumentDB::put
(this=this@entry=0x7f9771f3eb80, docId=docId@entry=24824047682453545, list=...)
at ../../../src/engine/documentdb.cpp:77
#16 0x7f98bbfb21e0 in Baloo::WriteTransaction::addDocument
(this=0x7f976c001250, doc=...) at ../../../src/engine/writetransaction.cpp:69
#17 0x7f98bbfabb79 in Baloo::Transaction::addDocument
(this=this@entry=0x7f9771f3ec90, doc=...) at
../../../src/engine/transaction.cpp:235
#18 0x0041bcff in Baloo::NewFileIndexer::run (this=0xc48200) at
../../../src/file/newfileindexer.cpp:72
#19 0x7f98bb8eae73 in QThreadPoolThread::run (this=0xa79430) at
thread/qthreadpool.cpp:93
#20 0x7f98bb8ee2be in QThreadPrivate::start (arg=0xa79430) at
thread/qthread_unix.cpp:337
#21 0x7f98ba5606aa in start_thread (arg=0x7f9771f3f700) at
pthread_create.c:333
#22 0x7f98baeff13d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f98bcda5800 (LWP 1455)):
#0  __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135
#1  0x7f98ba562cfd in __GI___pthread_mutex_lock (mutex=0x7f98bcf49040) at
../nptl/pthread_mutex_lock.c:80
#2  0x7f98b96419c2 in mdb_txn_renew0 (txn=txn@entry=0x96f060) at mdb.c:2566
#3  0x7f98b9642c10 in mdb_txn_begin (env=0x897c90, parent=parent@entry=0x0,
flags=flags@entry=0, ret=ret@entry=0x7fff9be58ec8) at mdb.c:2740
#4  0x7f98bbfab4bb in Baloo::Transaction::Transaction (this=0x7fff9be58ec0,
db=..., type=Baloo::Transaction::ReadWrite) at
../../../src/engine/transaction.cpp:54
#5  0x00428f44 in Baloo::MetadataMover::moveFileMetadata
(this=0x8df710, from=..., to=...) at ../../../src/file/metadatamover.cpp:49
#6  0x7f98bbafe617 in QtPrivate::QSlotObjectBase::call (a=0x7fff9be59020,
r=0x7fff9be596a0, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#7  QMetaObject::activate (sender=sender@entry=0x8c92d0,
signalOffset=, local_signal_index=local_signal_index@entry=7,
argv=argv@entry=0x7fff9be59020) at kernel/qobject.cpp:3702
#8  0x7f98bbafef87 in QMetaObject::activate (sender=sender@entry=0x8c92d0,
m=m@entry=0x643c20 ,
local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x7fff9be59020)
at kernel/qobject.cpp:3582
#9  0x004299fa in KInotify::moved (this=this@entry=0x8c92d0, _t1=...,
_t2=...) at ./moc_kinotify.cpp:329
#10 0x0042ba54 in KInotify::slotEvent (this=,
socket=) at ../../../src/file/kinotify.cpp:421
#11 0x7f98bbafe78a in QMetaObject::activate (sender=sender@entry=0x9308b0,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7fff9be59270) at kernel/qobject.cpp:3717
#12 0x7f98bbafef87 in QMetaObject::activate (sender=sender@entry=0x9308b0,
m=m@entry=0x7f98bbd01700 ,
local_signal_in

[kdenlive] [Bug 363813] Problems with buttons on Ubuntu 16.04

[Wegwerf via KDE Bugzilla]

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

--- Comment #3 from Wegwerf  ---
Robert,

glad to hear that your problem is fixed now. As for the website I'll have to
nudge them to update this information. But as the testing-ppa usually only
contains bug fixes but not new features it should be pretty safe for you to use
the testing-ppa instead of the stable-ppa.

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

[kaffeine] [Bug 363869] It is not possible to stop kaffeine aplication nor possible to kill the kaffeine process.

[Burkhard Lueck via KDE Bugzilla]

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

--- Comment #6 from Burkhard Lueck  ---
(In reply to Burkhard Lueck from comment #4)
> Same issue for me
> kaffeine master build from sources as a seperate user starting kaffeine from
> konsole
> 
I have no Digital TV hardware connected to my computer

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

[dolphin] [Bug 364014] New: Dolphin crashed when trying to open smb location

[Yaroslav Sidlovsky via KDE Bugzilla]

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

Bug ID: 364014
   Summary: Dolphin crashed when trying to open smb location
   Product: dolphin
   Version: 15.12.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: zawer...@gmail.com

Dolphin crashes each time I try to access one computer via SMB protocol.
Crash only happens when I access path 'smb://192.168.0.111' and not happens
when I access 'smb://192.168.0.111/C$' path.

Reproducible: Always

Steps to Reproduce:
1. Start Dolphin
2. Change location to "smb://192.168.0.111"
3. Crash!

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

[krita] [Bug 363921] Canvas is darkened and locked from further editing or saving, after leaving/re-entering virtual desktop

[Vlad via KDE Bugzilla]

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

Vlad  changed:

   What|Removed |Added

 CC||crackcroc...@gmail.com

--- Comment #1 from Vlad  ---

Yes, I confirm the same problem on Ubuntu Unity 14.04. The CPU is loaded to
25%, even after the "Force Quit" command. We have to kill the program manually
through the terminal. It really is a critical error.

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

[dolphin] [Bug 364014] Dolphin crashed when trying to open smb location

[Yaroslav Sidlovsky via KDE Bugzilla]

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

--- Comment #1 from Yaroslav Sidlovsky  ---
Created attachment 99389
  --> https://bugs.kde.org/attachment.cgi?id=99389&action=edit
backtrace

Backtrace collected with gdb

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

[kwin] [Bug 356740] Kwin crash if I set brightness while in kodi

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|BACKTRACE   |WORKSFORME

--- Comment #9 from Thomas Lübking  ---
file a bug against powerdevil (though it might be in some frameworks class,
don't know how the nasty brightness indicator is implemented)

The reason will be that the indicator is not override_redirect and does not
refuse focus, so it gets activated and the netwm spec requires fullscreen
windows to shift back to the normal layer when they loose the focus (desired
behavior because otherwise the active window would not get in sight). This
implicitly drops them below panels (and some other windows) as well.

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

[kaffeine] [Bug 363869] It is not possible to stop kaffeine aplication nor possible to kill the kaffeine process.

[David Geiger via KDE Bugzilla]

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

--- Comment #7 from David Geiger  ---
Also another issue with 2.0.1-1 release, kaffeine systray icon is completely
unusable.

have you the same symptom?

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

[konqueror] [Bug 364015] New: Crash at Gamepedia

[via KDE Bugzilla]

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

Bug ID: 364015
   Summary: Crash at Gamepedia
   Product: konqueror
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konq-b...@kde.org
  Reporter: m...@nightrealms.com

Application: konqueror (4.14.18)
KDE Platform Version: 4.14.20
Qt Version: 4.8.7
Operating System: Linux 4.5.5-201.fc23.x86_64 x86_64
Distribution: "Fedora release 23 (Twenty Three)"

-- Information about the crash:
At  http://digordie.gamepedia.com/Copper I was scrolling up and down using the
mouse wheel, then stopped scrolling and moved the cursor to edit a section, but
before I could click anything the browser crashed.

-- Backtrace:
Application: Konqueror (konqueror), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
84T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f73586b2900 (LWP 5536))]

Thread 9 (Thread 0x7f733b0d5700 (LWP 5537)):
#0  0x7f7352c76b1d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f734ecd616c in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f734ecd627c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f7355b28e7e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQtCore.so.4
#4  0x7f7355af7131 in
QEventLoop::processEvents(QFlags) () at
/lib64/libQtCore.so.4
#5  0x7f7355af74a5 in
QEventLoop::exec(QFlags) () at
/lib64/libQtCore.so.4
#6  0x7f73559e6a99 in QThread::exec() () at /lib64/libQtCore.so.4
#7  0x7f73573b673e in KIO::NameLookUpThread::run() () at /lib64/libkio.so.5
#8  0x7f73559e938c in QThreadPrivate::start(void*) () at
/lib64/libQtCore.so.4
#9  0x7f735574760a in start_thread (arg=0x7f733b0d5700) at
pthread_create.c:334
#10 0x7f7352c8259d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7f72ed4ab700 (LWP 5539)):
#0  0x7ffc96fc6967 in  ()
#1  0x7ffc96fc6c65 in clock_gettime ()
#2  0x7f7352c90816 in __GI___clock_gettime (clock_id=1, tp=0x7f72ed4aaa90)
at ../sysdeps/unix/clock_gettime.c:115
#3  0x7f7355a43c35 in qt_gettime() () at /lib64/libQtCore.so.4
#4  0x7f7355b29939 in QTimerInfoList::updateCurrentTime() () at
/lib64/libQtCore.so.4
#5  0x7f7355b28766 in timerSourceCheckHelper(GTimerSource*) () at
/lib64/libQtCore.so.4
#6  0x7f734ecd5bb1 in g_main_context_check () at /lib64/libglib-2.0.so.0
#7  0x7f734ecd6110 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#8  0x7f734ecd627c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#9  0x7f7355b28e7e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQtCore.so.4
#10 0x7f7355af7131 in
QEventLoop::processEvents(QFlags) () at
/lib64/libQtCore.so.4
#11 0x7f7355af74a5 in
QEventLoop::exec(QFlags) () at
/lib64/libQtCore.so.4
#12 0x7f73559e6a99 in QThread::exec() () at /lib64/libQtCore.so.4
#13 0x7f73559e938c in QThreadPrivate::start(void*) () at
/lib64/libQtCore.so.4
#14 0x7f735574760a in start_thread (arg=0x7f72ed4ab700) at
pthread_create.c:334
#15 0x7f7352c8259d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f72ebaa9700 (LWP 5542)):
#0  0x7f735574cb10 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f7338332071 in JSC::BlockAllocator::blockFreeingThreadMain() () at
/lib64/libQtWebKit.so.4
#2  0x7f73386364c6 in WTF::wtfThreadEntryPoint(void*) () at
/lib64/libQtWebKit.so.4
#3  0x7f735574760a in start_thread (arg=0x7f72ebaa9700) at
pthread_create.c:334
#4  0x7f7352c8259d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f72ead34700 (LWP 5551)):
#0  0x7f735574ceb9 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7f73559e98d4 in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQtCore.so.4
#2  0x7f73559dc8a7 in QThreadPoolThread::run() () at /lib64/libQtCore.so.4
#3  0x7f73559e938c in QThreadPrivate::start(void*) () at
/lib64/libQtCore.so.4
#4  0x7f735574760a in start_thread (arg=0x7f72ead34700) at
pthread_create.c:334
#5  0x7f7352c8259d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f72df960700 (LWP 5556)):
#0  0x7f735574ceb9 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7f73559e98d4 in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQtCore.so.4
#2  0x7f73559dc8a7 in QThreadPoolThread::run() () at /lib64/libQtCore.so.4
#3  0x7f73559e938c in QThreadPrivate::start(void*) () at
/lib64/libQtCore.so.4
#4  0x7f735574760a in start_t

[kdenlive] [Bug 363813] Problems with buttons on Ubuntu 16.04

[Robert Orzanna via KDE Bugzilla]

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

--- Comment #4 from Robert Orzanna  ---
That's good to know. 

Thank you so much! :)

Warmly,

~Robert

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

[kdenlive] [Bug 363813] Problems with buttons on Ubuntu 16.04

[Wegwerf via KDE Bugzilla]

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

--- Comment #5 from Wegwerf  ---
Robert, if this is fixed for you now, can you please be so kind as to close
this bug? You'll see the status below the additional comments field; please set
it to RESOLVED FIXED and save the change. Thank you very much!

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

[kaffeine] [Bug 364016] New: Courser does not disappear in full display mode.

[tuxnix via KDE Bugzilla]

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

Bug ID: 364016
   Summary: Courser does not disappear in full display mode.
   Product: kaffeine
   Version: 2.0.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mche...@osg.samsung.com
  Reporter: tux...@web.de

Courser does not disappear in full display mode.
'(That's all)

Reproducible: Always

Steps to Reproduce:
1. Watch a video or a TV-show
2. Do a double-click to have full display mode.

Actual Results:  
You watch video with mouse courser. 
That is not perfect.

Expected Results:  
Courser has to disappear after some seconds without mouse action.
(And courser has to appear again when using mouse.)

Achlinux-Kaffeine 2.0.1-3

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

[kaffeine] [Bug 363869] It is not possible to stop kaffeine aplication nor possible to kill the kaffeine process.

[Mauro Carvalho Chehab via KDE Bugzilla]

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

--- Comment #8 from Mauro Carvalho Chehab  ---
(In reply to Burkhard Lueck from comment #4)
> Sami issue for me
> kaffeine master build from sources as a seperate user starting kaffeine from
> konsole
> 
> Launching with:
> $ kaffeine --dumpdvb
> 06-06-16 08:04:07.854 [Debug   ]
> /home/kdeframeworks/src/frameworks/kxmlgui/src/kactioncollection.cpp#264:
> Registering action  "options_configure_keybinding"  under new name 
> "settings_keys"
> 06-06-16 08:04:07.854 [Debug   ]
> /home/kdeframeworks/src/frameworks/kxmlgui/src/kactioncollection.cpp#264:
> Registering action  "options_configure"  under new name  "settings_kaffeine"
> [020006c8] pulse audio output error: PulseAudio server connection
> failure: Connection refused
> libGL error: failed to open drm device: Permission denied
> libGL error: failed to load driver: i965

Your issue seems to be unrelated to this BZ: both pulseaudio and the DRM driver
are returning permission denied. It seems your issue is actually related to a
bad configuration: your user doesn't seem to have permissions to open
/dev/dri/card0, and pulseaudio is likely running as another user.

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

[krita] [Bug 363977] Krita 3.0 crashes when I use tablet (but in pre-alpha it working fine)

[cheerful_weasel via KDE Bugzilla]

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

cheerful_weasel  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from cheerful_weasel  ---
Thanks, wolthera! It work fine!

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

[plasmashell] [Bug 361952] kicker v5.6.4 still use KF5::ActivitiesExperimentalStats of kactivities-5.16.0 deprecated in v5.21.0

[Ivan Čukić via KDE Bugzilla]

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

--- Comment #9 from Ivan Čukić  ---
@Leslie

You don't have push permissions?

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

[kdeconnect] [Bug 363953] Touchpad input no longer work

[via KDE Bugzilla]

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

niclas.rossber...@gmx.de changed:

   What|Removed |Added

 CC||niclas.rossber...@gmx.de

--- Comment #2 from niclas.rossber...@gmx.de ---
For me it's fixed (had the same issue before)

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

[kdenlive] [Bug 363813] Problems with buttons on Ubuntu 16.04

[Robert Orzanna via KDE Bugzilla]

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

Robert Orzanna  changed:

   What|Removed |Added

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

--- Comment #6 from Robert Orzanna  ---
Done. :-)

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

[kaffeine] [Bug 363869] It is not possible to stop kaffeine aplication nor possible to kill the kaffeine process.

[Mauro Carvalho Chehab via KDE Bugzilla]

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

--- Comment #9 from Mauro Carvalho Chehab  ---
(In reply to David Geiger from comment #7)
> Also another issue with 2.0.1-1 release, kaffeine systray icon is completely
> unusable.
> 
> have you the same symptom?

This is also unrelated to this BZ. The systray icon didn't have any menu. I
just added one that will match the functionality of the "Start" window. It will
also de-minimize the window if it was minimized.

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

[kdialog] [Bug 309861] passive, non-intrusive progress bar

[Dmitry Nezhevenko via KDE Bugzilla]

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

Dmitry Nezhevenko  changed:

   What|Removed |Added

 CC||d...@inhex.net

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

[kaffeine] [Bug 363869] It is not possible to stop kaffeine aplication nor possible to kill the kaffeine process.

[David Geiger via KDE Bugzilla]

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

--- Comment #10 from David Geiger  ---
(In reply to Mauro Carvalho Chehab from comment #9)
> (In reply to David Geiger from comment #7)
> > Also another issue with 2.0.1-1 release, kaffeine systray icon is completely
> > unusable.
> > 
> > have you the same symptom?
> 
> This is also unrelated to this BZ. The systray icon didn't have any menu. I
> just added one that will match the functionality of the "Start" window. It
> will also de-minimize the window if it was minimized.

Yeah sorry I'll open a new one for this issue :)

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

[trojita] [Bug 360689] Switch to SVG icons from Breeze

[Jan Kundrát via KDE Bugzilla]

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

Jan Kundrát  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/troj
   ||ita/0cc3ac8294a3060cb2e5e92
   ||8602e7081d0ab23a9

--- Comment #1 from Jan Kundrát  ---
Git commit 0cc3ac8294a3060cb2e5e928602e7081d0ab23a9 by Jan Kundrát.
Committed on 02/06/2016 at 13:26.
Pushed by gerrit into branch 'master'.

SVG Breeze icons

This is a great opportunity to, well, change the UI to something which
looks modern. Using a reasonable icon scheme and especially the choice
of its default shape is a nice topic for bikeshedding, so I'm simply
going to use that piece which I get on my laptop by default anyway.
Change-Id: I74a0e36d89fde0dcfb798a0718c8dd256811c2aa

M  +4-4src/Gui/ComposeWidget.cpp
M  +1-1src/Gui/EmbeddedWebView.cpp
M  +2-2src/Gui/OneEnvelopeAddress.cpp
M  +1-1src/Gui/Window.cpp
M  +4-4src/Imap/Model/PrettyMsgListModel.cpp
M  +1-16   src/UiUtils/IconLoader.cpp
M  +77   -43   src/icons.qrc
D  +---src/icons/application-exit.png
A  +3-0src/icons/application-exit.svg
D  +---src/icons/arrow-left.png
A  +16   -0src/icons/arrow-left.svg
D  +---src/icons/arrow-right.png
A  +16   -0src/icons/arrow-right.svg
A  +1-0src/icons/breeze/folder-bookmark.svg
T  +1-153  src/icons/breeze/mail-forward.svg
T  +1-204  src/icons/breeze/mail-reply-all.svg
T  +1-196  src/icons/breeze/mail-reply-list.svg
T  +1-199  src/icons/breeze/mail-reply-sender.svg
A  +17   -0src/icons/colorneg.svg
D  +---src/icons/configure-shortcuts.png
A  +15   -0src/icons/configure-shortcuts.svg
D  +---src/icons/configure.png
A  +16   -0src/icons/configure.svg
D  +---src/icons/contact-known.png
A  +14   -0src/icons/contact-known.svg
D  +---src/icons/contact-unknown.png
A  +14   -0src/icons/contact-unknown.svg
A  +16   -0src/icons/dialog-cancel.svg
A  +8-0src/icons/dialog-close.svg
D  +---src/icons/dialog-password.png
A  +35   -0src/icons/dialog-password.svg
D  +---src/icons/document-edit.png
A  +15   -0src/icons/document-edit.svg
A  +15   -0src/icons/document-open-recent.svg
A  +15   -0src/icons/document-save-all.svg
A  +15   -0src/icons/document-save-as.svg
D  +---src/icons/document-save.png
A  +15   -0src/icons/document-save.svg
A  +15   -0src/icons/download.svg
A  +15   -0src/icons/edit-copy.svg
D  +---src/icons/edit-find-mail.png
A  +15   -0src/icons/edit-find-mail.svg
A  +15   -0src/icons/edit-find.svg
A  +15   -0src/icons/edit-rename.svg
A  +16   -0src/icons/edit-select-all.svg
A  +14   -0src/icons/emblem-encrypted-unlocked.svg
A  +14   -0src/icons/emblem-error.svg
A  +19   -0src/icons/emblem-important.svg
A  +21   -0src/icons/emblem-information.svg
A  +13   -0src/icons/emblem-success.svg
A  +10   -0src/icons/emblem-warning.svg
D  +---src/icons/folder-bookmark.png
A  +7-0src/icons/folder-bookmark.svg
D  +---src/icons/folder-grey.png
A  +7-0src/icons/folder-grey.svg
D  +---src/icons/folder-open.png
A  +14   -0src/icons/folder-open.svg
D  +---src/icons/folder-xt-sync.png
D  +---src/icons/folder.png
A  +13   -0src/icons/folder.svg
A  +16   -0src/icons/format-justify-fill.svg
A  +16   -0src/icons/format-justify-right.svg
A  +16   -0src/icons/go-down.svg
A  +16   -0src/icons/go-jump.svg
A  +16   -0src/icons/go-previous.svg
A  +16   -0src/icons/go-up.svg
D  +---src/icons/imap-search-details.png
A  +16   -0src/icons/insert-image.svg
D  +---src/icons/list-remove.png
A  +5-0src/icons/list-remove.svg
D  +---src/icons/mail-attachment.png
A  +16   -0src/icons/mail-attachment.svg
D  +---src/icons/mail-flagged.png
A  +17   -0src/icons/mail-flagged.svg
D  +---src/icons/mail-folder-inbox.png
A  +13   -0src/icons/mail-folder-inbox.svg
D  +---src/icons/mail-forward.png
C  +0-0src/icons/mail-forward.svg [from:
src/icons/breeze/mail-forward.svg - 100% similarity]
A  +16   -0src/icons/mail-forwarded-replied.svg
D  +---src/icons/mail-forwarded.png
A  +16   -0src/icons/mail-forwarded.svg
A  +20   -0src/icons/mail-mark-junk.svg
A  +16   -0src/icons/mail-mark-notjunk.svg
D  +---src/icons/mail-mark-read.png
A  +16   -0src/icons/mail-mark-read.svg
A  +16   -0src/icons/mail-mark-unread-new.svg
A  +16   -0src/icons/mail-mark-unread.svg
D  +---src/icons/mail-read.png
D  +---src/icons/ma

[kaffeine] [Bug 364017] New: recording schedule with qdbus get disabled tv-records

[tuxnix via KDE Bugzilla]

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

Bug ID: 364017
   Summary: recording schedule with qdbus get disabled tv-records
   Product: kaffeine
   Version: 2.0.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mche...@osg.samsung.com
  Reporter: tux...@web.de

As I see you improved tv recording.
Kaffeine's sqlite.db has get two fields more in TABLE RecordingSchedule now
(Priority and Disabled)
I'm using a TV-Browser ruby script to schedule recordings. 
(http://wiki.tvbrowser.org/index.php/CapturePlugin_-_Kaffeine 
Ruby-Script kaffeine-tvbrowser-qdebus.rb)
This script uses qdebus to write in kaffeine-sqlite.db.
ret = system(%Q)
This all went well in last kaffeine version. But now (vers. 2.0.1) it happens
that not all but most schedulings were set to "disabled" and will not do the
recordings.

I tried to modify the script to give the Priority and Disabled fields a "100"
and "0" which is necessary to set the record to "enabled" but with qdbus it is
not allowed to set more than these five fields above.
It would not be so hard to use an other method in the TV-browser script to do
that, but I thought I should tell you this behaviour, because  your
implementation should work with qdbus too.
Android KDE-Connect App is using qdbus and In future a nativ plasma-mobil App
will use qdbus too to work as a remote control.

I thought it could be a solution to set "100" in Priority and "0" in Disabled
fields as default in sqlite.db. But I'm not an expert on programming at all.

Greatings
TuxNix











Reproducible: Sometimes

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

[kaffeine] [Bug 364018] New: systray icon is completely unusable, nothing happens when clicking on the icon

[David Geiger via KDE Bugzilla]

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

Bug ID: 364018
   Summary: systray icon is completely unusable, nothing happens
when clicking on the icon
   Product: kaffeine
   Version: 2.0.1
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mche...@osg.samsung.com
  Reporter: geiger.david68...@gmail.com

I encountered an issue with latest 2.0.1-1 release, kaffeine systray icon is
completely unusable.

If I click on nothing happens, it does not "Start" the window and does not
de-minimize the window if it was minimized.



Reproducible: Always

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

[Powerdevil] [Bug 364019] New: Screen is flickering when setting brightness while in Kodi

[Côme Chilliet via KDE Bugzilla]

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

Bug ID: 364019
   Summary: Screen is flickering when setting brightness while in
Kodi
   Product: Powerdevil
   Version: 5.6.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-de...@kde.org
  Reporter: c...@chilliet.eu

Hello,

Following https://bugs.kde.org/show_bug.cgi?id=356740 , when I’m in Kodi and I
increase/decrease brighness the screen flickers because the taskbar show up
briefly.
I got no problem when increasing/decreasing audio volume.
On the other bug this was said:
«The reason will be that the indicator is not override_redirect and does not
refuse focus, so it gets activated and the netwm spec requires fullscreen
windows to shift back to the normal layer when they loose the focus (desired
behavior because otherwise the active window would not get in sight). This
implicitly drops them below panels (and some other windows) as well.»

Reproducible: Always

Steps to Reproduce:
1. Open Kodi (or most likely any fullscreen app)
2. Increase or decrease brightness


Actual Results:  
The taskbar show up, sometimes other windows/indicators as well, for a brief
moment.
When increasing several times it flickers between this and kodi.

Expected Results:  
Only the brightness indicator above Kodi, no flickering and no taskbar.

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

[kwalletmanager] [Bug 363532] "Allow Always" does not work

[via KDE Bugzilla]

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

fetzt_d...@vollbio.de changed:

   What|Removed |Added

 CC||fetzt_d...@vollbio.de

--- Comment #3 from fetzt_d...@vollbio.de ---
I can absolutely confirm this bug for kubuntu 15.10 and it is still persisting
in kubuntu 16.04.

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

[digikam] [Bug 364009] Cannot use batch processing to resize images

[via KDE Bugzilla]

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

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

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||5.0.0
 CC||caulier.gil...@gmail.com
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from caulier.gil...@gmail.com ---
The resize tool from kipi plugins have been removed with new 5.0.0 release
(currently in beta7).

You must use Batch Queue Manager from digiKam core instead, which has some
limitation currently. See files relevant from bugzilla for details :

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

The new 5.0.0 Windows installer for testing is available at this url :

https://drive.google.com/open?id=0B7yq-xFihT0_SzhxVzF1RDhPbFE

Gilles Caulier

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

[kaffeine] [Bug 363869] When Kaffeine is started on Plasma menu, It doesn't stop when the main window is closed

[Mauro Carvalho Chehab via KDE Bugzilla]

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

Mauro Carvalho Chehab  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
Summary|It is not possible to stop  |When Kaffeine is started on
   |kaffeine aplication nor |Plasma menu, It doesn't
   |possible to kill the|stop when the main window
   |kaffeine process.   |is closed

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

[frameworks-kio] [Bug 363991] Drag and drop does not work in folder view

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

   Assignee|h...@kde.org|fa...@kde.org
 CC||kdelibs-b...@kde.org
Product|plasmashell |frameworks-kio
Version|master  |5.22.0
   Target Milestone|1.0 |---
  Component|Folder  |general

--- Comment #4 from Kai Uwe Broulik  ---
Right, I can also reproduce with Dolphin. Either a bug in KIO or the desktop:/
kio slave. Re-assigning.

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

[kmymoney4] [Bug 349033] option to invert transaction amounts during import

[allan via KDE Bugzilla]

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

--- Comment #3 from allan  ---
Pending a proper solution, it might save a little effort when importing to
select the present amount column as Debit, and some other column as Credit. 
Then, when importing, you are given the option to accept either the debit or
credit column amount, for each transaction.  That's a bit of a fag, but it
might be easier.  The credit amount would need to be edited after import.

Allan

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

[krita] [Bug 363921] Canvas is darkened and locked from further editing or saving, after leaving/re-entering virtual desktop

[Dmitry Kazakov via KDE Bugzilla]

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

Dmitry Kazakov  changed:

   What|Removed |Added

 CC||dimul...@gmail.com

--- Comment #2 from Dmitry Kazakov  ---
Hi!

I'm using Ubuntu 16.04 with Unity and I have absolutely no crash or hangup with
switching the desktops. Could you please generate a backtrace of what Krita
does when it hangs up on your computer? Here is a manual how to do that:

http://nonaynever.ru/kwiki/krita/BugWritingGuidelines#Hangup_Bug

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

[klipper] [Bug 339978] Klipper shows two image-look-like icons that do nothing

[Sudhir Khanger via KDE Bugzilla]

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

Sudhir Khanger  changed:

   What|Removed |Added

 CC||sud...@sudhirkhanger.com

--- Comment #8 from Sudhir Khanger  ---
There's at least 3 places where this bug is being tracked (as far as I can
tell). Unfortunately none of them seems to move forward.

https://bugs.chromium.org/p/chromium/issues/detail?id=428646
https://bugs.chromium.org/p/chromium/issues/detail?id=424111
https://bugs.chromium.org/p/chromium/issues/detail?id=442253

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

[klipper] [Bug 364020] New: Clicking on Clipboard Manager item closes itself and opens Status & Notification tray widget.

[Sudhir Khanger via KDE Bugzilla]

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

Bug ID: 364020
   Summary: Clicking on Clipboard Manager item closes itself and
opens Status & Notification tray widget.
   Product: klipper
   Version: 5.6.4
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: plasma-widget
  Assignee: mgraess...@kde.org
  Reporter: sud...@sudhirkhanger.com

As the title says, when I click on an item in clipboard manager it closes
itself and opens Status & Notifications tray widget.

Reproducible: Always

Steps to Reproduce:
1. Click on any item in clipboard manager widget
2.
3.

Actual Results:  
closes itself and opens status and notification widget

Expected Results:  
don't close clipboard manager widget

Plasma 5.6.4
Frameworks 5.22
Qt 5.6
Fedora 23

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

[kate] [Bug 156330] [PATCH] Fix plugin loading in kate sessions

[William Ap Brandino via KDE Bugzilla]

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

William Ap Brandino  changed:

   What|Removed |Added

 CC||william.brandino@telecontro
   ||l.com.br

--- Comment #61 from William Ap Brandino  
---
This is not solved. Occur with frequence when changes sessions.
Ubuntu 16.04 - Version 15.12.3

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

[cantor] [Bug 354772] Cantor: hardcoded include of luajit-2.0/lua.hpp

[Lucas Hermann Negri via KDE Bugzilla]

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

--- Comment #2 from Lucas Hermann Negri  ---
Hi,

Mea culpa. After years (and a change in the mantainer), LuaJIT bumped its
version number. I will fix this.

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

[trojita] [Bug 364021] New: Sending mails hangs at 50 %

[Tobias Leupold via KDE Bugzilla]

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

Bug ID: 364021
   Summary: Sending mails hangs at 50 %
   Product: trojita
   Version: 0.6
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: SMTP
  Assignee: trojita-b...@kde.org
  Reporter: tobias.leup...@web.de

Since some time (a few weeks), I can't send mails anymore with Trojita.
Probably, this is problem with my mail provider GMX, because it happens both
with version 0.5 and 0.6, but I don't know how to debug it …

When sending a mail, it's added to the "Sent" IMAP folder, but the sending
process bar hangs at 50 % and nothing happens. The mail is not actually sent,
just added to the "Sent" folder. So I think the IMAP stuff still works, but the
SMTP stuff doesn't.

Reading the IMAP protocol, it only says:

15:33:05.459 Network Session User's preference changed: NETWORK_ONLINE
15:33:05.459 Network Session Switched to network configuration enp3s0
(Ethernet, 3278187404)
15:33:05.459 Network Session Opening network session
15:33:05.459 Network Session Session is open (configuration enp3s0), online
state: online
15:33:57.965 Submission STATE_INIT
15:33:57.971 Submission STATE_BUILDING_MESSAGE
15:33:57.979 Submission STATE_SAVING
15:33:58.052 Submission STATE_SUBMITTING

But, as said, nothing happens, the progress bar stays at 50 % forever. Same
thing on two different machines, one using x86 and one amd_64, but both trying
to send mails via GMX.

I would really like to debug this further if someone told me how ;-)

Reproducible: Always

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

[plasma-nm] [Bug 362729] Cannot connect to OpenConnect VPN with username/password

[Jan Grulich via KDE Bugzilla]

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

Jan Grulich  changed:

   What|Removed |Added

 CC||jgrul...@redhat.com

--- Comment #1 from Jan Grulich  ---
I'm not able to reproduce this issue. I tried to setup an ocserver with plain
user/password authentication and it works just fine. I guess that what you see
in the log could be the reason why it doesn't work for you and I think that the
problem is in the server you are trying to connect to.

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

[plasma-nm] [Bug 355050] Will not connect to openconnect vpn if CN in untrusted certificate does not match the host name

[Jan Grulich via KDE Bugzilla]

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

--- Comment #4 from Jan Grulich  ---
Is this still reproducible with Plasma 5.5.1 or newer?

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

[krita] [Bug 363921] Canvas is darkened and locked from further editing or saving, after leaving/re-entering virtual desktop

[Vlad via KDE Bugzilla]

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

--- Comment #3 from Vlad  ---
Привет,  Дмитрий.
 Вот бэктрейс при уже повисшем приложении. Запущен appimage через gdb.
(gdb) run
The program being debugged has been started already.
Start it from the beginning? (y or n) y
/tmp/.mount_20wnsC/usr/bin/krita: Нет такого файла или каталога.
(gdb)
(gdb)
(gdb)
(gdb) exit
Undefined command: "exit".  Try "help".
(gdb) Quit
(gdb)
[1]+  Остановлено  gdb '/home/ero/Документы/Program/Krita/krita.appimage'
ero@echo:~/Документы/Program/Krita$
ero@echo:~/Документы/Program/Krita$
ero@echo:~/Документы/Program/Krita$
ero@echo:~/Документы/Program/Krita$ gdb
'/home/ero/Документы/Program/Krita/krita.appimage'
GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /home/ero/Документы/Program/Krita/krita.appimage...(no
debugging symbols found)...done.
(gdb) run
Starting program: /home/ero/Документы/Program/Krita/krita.appimage
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
process 10227 is executing new program: /tmp/.mount_fJcTI3/AppRun
process 10227 is executing new program: /tmp/.mount_fJcTI3/usr/bin/krita
warning: Could not load shared library symbols for 55 libraries, e.g.
./lib/libkritaui.so.15.
Use the "info sharedlibrary" command to see the complete listing.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
QCoreApplication::arguments: Please instantiate the QApplication object
first
krita.lib.pigment: Compiled for arch: ::Vc::AVXImpl
krita.lib.pigment: Features supported:
krita.lib.pigment:  "SSE2" --- yes
krita.lib.pigment:  "SSSE3" --- yes
krita.lib.pigment:  "SSE4.1" --- yes
krita.lib.pigment:  "AVX " --- yes
warning: Could not load shared library symbols for 3 libraries, e.g.
./lib/libfreetype.so.6.
Use the "info sharedlibrary" command to see the complete listing.
Do you need "set solib-search-path" or "set sysroot"?
[New Thread 0x7fffeb17d700 (LWP 10242)]
[New Thread 0x7fffea103700 (LWP 10243)]
OpenGL Info
  Vendor:  NVIDIA Corporation
  Renderer:  GeForce GTX 750/PCIe/SSE2
  Version:  4.5.0 NVIDIA 352.63
  Shading language:  4.50 NVIDIA
  Requested format:  QSurfaceFormat(version 3.0, options QFlags(0x4),
depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize
-1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior 2,
swapInterval 0, profile  2)
  Current format:QSurfaceFormat(version 4.5, options QFlags(0x4),
depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8,
alphaBufferSize 0, stencilBufferSize 8, samples -1, swapBehavior 2,
swapInterval 0, profile  2)
krita has opengl true
Setting XDG_DATA_DIRS
"/tmp/.mount_fJcTI3/usr/bin/../share:./share/:/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/"
Available translations QSet("lv", "ug", "hr", "uk", "hu", "en_US", "mai",
"ia", "mk", "ca@valencia", "uz", "nds", "mr", "ms", "is", "el", "vi", "it",
"af", "eo", "nb", "es", "et", "eu", "ne", "ro", "ja", "ar", "ast", "nl",
"ru", "nn", "fa", "hne", "wa", "fi", "be", "bg", "se", "fr", "oc", "sk",
"sl", "pt_BR", "fy", "br", "bs", "en_GB", "sq", "zh_CN", "sv", "ga", "kk",
"km", "ca", "ko", "ta", "xh", "zh_TW", "gl", "tg", "th", "pa", "cs", "tr",
"pl", "cy", "he", "pt", "da", "hi", "de", "lt", "uz@cyrillic")
Available domain translations QSet("lv", "ug", "hr", "uk", "hu", "en_US",
"mai", "ia", "mk", "ca@valencia", "uz", "nds", "mr", "ms", "is", "el",
"vi", "it", "af", "eo", "nb", "es", "et", "eu", "ne", "ro", "ja", "ar",
"ast", "nl", "ru", "nn", "fa", "hne", "wa", "fi", "be", "bg", "se", "fr",
"oc", "sk", "sl", "pt_BR", "fy", "br", "bs", "en_GB", "sq", "zh_CN", "sv",
"ga", "kk", "km", "ca", "ko", "ta", "xh", "zh_TW", "gl", "tg", "th", "pa",
"cs", "tr", "pl", "cy", "he", "pt", "da", "hi", "de", "lt", "uz@cyrillic")
Override language: ""
KoJsonTrader will load its plugins from
"/tmp/.mount_fJcTI3/usr/lib/kritaplugins"
warning: Could not load shared library symbols for ./lib/liblcms2.so.2.
Do you need "set solib-search-path" or "set sysroot"?
warning: Could not load shared library symbols for
./lib/libkritalibpaintop.so.15.
Do you need "

[krita] [Bug 364022] New: Tool options don't load on startup

[via KDE Bugzilla]

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

Bug ID: 364022
   Summary: Tool options don't load on startup
   Product: krita
   Version: 3.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Dockers
  Assignee: krita-bugs-n...@kde.org
  Reporter: brummerk...@gmail.com

When i start up krita the default brush is selected, but there are no tool
options for it until i select another tool, and then re-select the brush tool
(B).
I was really confused for a while, since i was watching a video on the
smoothing options and i couldn't find it on my krita.

Reproducible: Always

Steps to Reproduce:
1. Start krita
2. Make a new file
3. Click the tool options docker (my default config has it enabled in a docker
with layers/brush presets)

Actual Results:  
Nothing is visible below "Tool Options", no matter what you click in the
window, until you select another tool

Expected Results:  
Smoothing options should be visible on startup

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

[systemsettings] [Bug 363947] kde connect: Could not mount device.

[Mark Unger via KDE Bugzilla]

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

Mark Unger  changed:

   What|Removed |Added

 CC||mrk.un...@gmail.com

--- Comment #2 from Mark Unger  ---
I have the same issue:
- Samsung Galaxy Note II
- KDE Frameworks 5.22.0 
- KDE Plasma Version: 5.6.4
- Qt 5.6.0
- Manjaro Operating System 4.6.1

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

[krita] [Bug 363965] Krita crashes when touching pen to tablet using Adesso CyberTablet M14

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Boudewijn Rempt  ---
No, it's the full version, latest developer builds, so you're not missing
anything. We'll be releasing the official 3.0.1 with more bug fixes end of this
month, in the meantime we're fixing bugs and making development builds.

Depending on how many duplicates of this issue we get, I might move that up to
end of this week, though. I'm amazed at how many variants of this buggy tablet
with its buggy driver have been sold. There's at least half a dozen brands that
repack it.

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

[krita] [Bug 364023] Some brush presets cannot be added to favorites.

[via KDE Bugzilla]

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

brummerk...@gmail.com changed:

   What|Removed |Added

 CC||brummerk...@gmail.com

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

[krita] [Bug 364023] New: Some brush presets cannot be added to favorites.

[via KDE Bugzilla]

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

Bug ID: 364023
   Summary: Some brush presets cannot be added to favorites.
   Product: krita
   Version: 3.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: brummerk...@gmail.com

Some brushes can't be added to a custom brush tag.

Reproducible: Always

Steps to Reproduce:
1. Select freehand brush tool
2. Open up "choose brush preset"
3. Select the tag "all" at the top
4. Right click on clone tool
5. Assign to a tag, like the existing Favorite tag or a new, empty tag
6. select that tag at the top

Actual Results:  
The assigned (clone stamp) tool is not visible in either the brush presets tag
menu nor the pop-up right click menu with the tags.

Expected Results:  
The brush should be added to the desired menu.

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

[krita] [Bug 364024] New: Bind Brush Ratio modifier to a tablet sensor

[Kobayen via KDE Bugzilla]

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

Bug ID: 364024
   Summary: Bind Brush Ratio modifier to a tablet sensor
   Product: krita
   Version: 3.0
  Platform: Other
OS: other
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: koba...@gmail.com

This is a feature I've seen in Photoshop since ever, which is conspicuously
lacking in Krita; the ability to modify a brush's horizontal-to-vertical ratio
with tablet input, be it pressure or (more commonly) tilt angle.

The objective is to squash a brush as you apply pressure or tilt the pen,
giving a certain calligraphy to the stroke. While I am aware Ratio is a
variable of Auto brushes, I assume this feature would also work on Texture
brushes if possible.

Reproducible: Always

Steps to Reproduce:
1. Poke around the Brush Engine settings
2. Google
3. Profit?


Expected Results:  
To have found said option either among the Auto Brush Tip options, or (as I
suppose where it will be) among the Flow group of the brush settings.

Win 8.1, Tablet Wacom PTK-640 (Intuos 4 Medium)

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

[krita] [Bug 364024] Bind Brush Ratio modifier to a tablet sensor

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
 CC||b...@valdyas.org

--- Comment #1 from Boudewijn Rempt  ---
Thanks!

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

[plasmashell] [Bug 364025] New: When renaming a file, it moves to the top left corner on the desktop

[via KDE Bugzilla]

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

Bug ID: 364025
   Summary: When renaming a file, it moves to the top left corner
on the desktop
   Product: plasmashell
   Version: 5.5.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Desktop Containment
  Assignee: se...@kde.org
  Reporter: leh...@tutanota.com

Reproducible: Always

Steps to Reproduce:
Rename a file.

Actual Results:  
File moves to the top left.

Expected Results:  
File should stay in place.

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

[krita] [Bug 363921] Canvas is darkened and locked from further editing or saving, after leaving/re-entering virtual desktop

[Vlad via KDE Bugzilla]

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

--- Comment #4 from Vlad  ---
вот также полный бектрейс момента после переключения вирт. рабочего стола и
последующей попытке сохранить файл, когда появляется окно с сообщением, что
надо подождать когда закончится обработка изображения
Thread 11 (Thread 0x7fffc9ffb700 (LWP 10684)):
#0  0x710ef404 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/x86_64-linux-gnu/libpthread.so.0
#1  0x003df4caae6b in ?? ()
#2  0x in ?? ()

Thread 5 (Thread 0x7fffd0ab4700 (LWP 10678)):
#0  0x710ef404 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/x86_64-linux-gnu/libpthread.so.0
#1  0x003df4caae6b in ?? ()
#2  0x in ?? ()

Thread 4 (Thread 0x7fffd12b5700 (LWP 10677)):
#0  0x710ef404 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/x86_64-linux-gnu/libpthread.so.0
#1  0x003df4caae6b in ?? ()
#2  0x in ?? ()

Thread 3 (Thread 0x7fffea103700 (LWP 10674)):
#0  0x7245afdd in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x70a17fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x70a180ec in g_main_context_iteration ()
---Type  to continue, or q  to quit---
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x003df4eda7c3 in ?? ()
#4  0x7fffdc003054 in ?? ()
#5  0x7fffea102dd0 in ?? ()
#6  0x0024 in ?? ()
#7  0x7fffdc002fe0 in ?? ()
#8  0x in ?? ()

Thread 2 (Thread 0x7fffeb17d700 (LWP 10673)):
#0  0x7245afdd in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x71711b72 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7171364f in xcb_wait_for_event ()
   from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fffeb1c98f1 in ?? ()
#4  0x in ?? ()

Thread 1 (Thread 0x77fab7c0 (LWP 10658)):
#0  0x7245afdd in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x70a17fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x70a180ec in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x003df4eda76b in ?? ()
#4  0x15b92984 in ?? ()
---Type  to continue, or q  to quit---
#5  0x7fffb8d0 in ?? ()
#6  0x0064 in ?? ()
#7  0x15b92910 in ?? ()
#8  0x0040 in ?? ()
#9  0x003df4e86043 in ?? ()
#10 0x7fffb8d0 in ?? ()
#11 0x00a67680 in ?? ()
#12 0x0010 in ?? ()
#13 0x0cf6d260 in ?? ()
#14 0x7fffb8d0 in ?? ()
#15 0x0001 in ?? ()
#16 0x0080 in ?? ()
#17 0x723f06c0 in malloc () from /lib/x86_64-linux-gnu/libc.so.6
#18 0x72caddad in operator new(unsigned long) ()
   from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#19 0x0cf6d260 in ?? ()
#20 0x7fffb8d0 in ?? ()
#21 0x0001 in ?? ()
#22 0x0080 in ?? ()
#23 0x003df9f48f2d in ?? ()
#24 0x0d9968f0 in ?? ()
#25 0x765de140 in ?? ()
#26 0x003df53ad7f0 in ?? ()
---Type  to continue, or q  to quit---
#27 0x0001 in ?? ()
#28 0x in ?? ()
(gdb)




2016-06-06 19:05 GMT+05:00 Влад Ку :

> Привет,  Дмитрий.
>  Вот бэктрейс при уже повисшем приложении. Запущен appimage через gdb.
> (gdb) run
> The program being debugged has been started already.
> Start it from the beginning? (y or n) y
> /tmp/.mount_20wnsC/usr/bin/krita: Нет такого файла или каталога.
> (gdb)
> (gdb)
> (gdb)
> (gdb) exit
> Undefined command: "exit".  Try "help".
> (gdb) Quit
> (gdb)
> [1]+  Остановлено  gdb '/home/ero/Документы/Program/Krita/krita.appimage'
> ero@echo:~/Документы/Program/Krita$
> ero@echo:~/Документы/Program/Krita$
> ero@echo:~/Документы/Program/Krita$
> ero@echo:~/Документы/Program/Krita$ gdb
> '/home/ero/Документы/Program/Krita/krita.appimage'
> GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1
> Copyright (C) 2014 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <
> http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> .
> Find the GDB manual and other documentation resources online at:
> .
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from
> /home/ero/Документы/Program/Krita/krita.appimage...(no debugging symbols
> found)...done.
> (gdb) run
> Starting program: /home/ero/Документы/Program/Krita/krita.appimage
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> process 10227 is executing new program: /tmp/.mount_fJcTI3/AppRun
> process 10

[kwin] [Bug 358369] Plasma crashed after opening an HTML5 video in Chrome

[Steve Torrence via KDE Bugzilla]

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

Steve Torrence  changed:

   What|Removed |Added

 CC|storre...@cirm.ca.gov   |

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

[krita] [Bug 364027] New: Recorded actions don't play well with wrapping mode

[via KDE Bugzilla]

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

Bug ID: 364027
   Summary: Recorded actions don't play well with wrapping mode
   Product: krita
   Version: 3.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: brummerk...@gmail.com

The recorded actions don't take wrapping mode into account; if they're an
accurate reproduction of user input, logic follows that they'd behave properly
with wrapping mode, as long as it is turned on when playing the action.
I figured there is some core component of the wrapping mode that's not
implemented, since it doesn't support color picking either.

Reproducible: Always

Steps to Reproduce:
1. Make a new file
2. Turn wrap mode on (W)
3. Start recording
4. Make a stroke that extends past the edge of the document, looping around
5. Save recording
6. Undo all your changes or make a new project, turn wrap mode on
7. play your recording

Actual Results:  
The stroke doesn't loop around, it only extends to where it leaves the canvas.

Expected Results:  
I'd expect to get the same results as i get when i make the initial stroke.

This feature is pretty important for me.
It may be very niche, but i work with tiling textures that are a result of
photogrammetry, and krita is the only tool so far that even remotely supports
such a workflow.

I have a 3d scan of an object that i use to produce 2-4 texture maps (diffuse,
height, normal, etc.), which i have to tile via recorded actions, so that the
same operations (clone stamp, etc) are applied to all of them, producing
minimal difference between the structurally identical texture maps.

Now, the recorded actions don't seem to support the seamless mode, which is one
of the two possible tools to tile an image easily.
The other, less optimal solution would be offsetting by (width& height)/2, but
the recording engine doesn't seem to record "Offset Image".

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

[trojita] [Bug 364021] Sending mails hangs at 50 %

[Jan Kundrát via KDE Bugzilla]

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

Jan Kundrát  changed:

   What|Removed |Added

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

--- Comment #1 from Jan Kundrát  ---
SMTP submission prints out stuff to stderr, so please:

1) ensure Trojita is not running,
2) start Trojita from console,
3) try sending e-mail as usual,
4) attach the log from console here,
5) reopen.

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

[kde] [Bug 364026] New: Crash when closing dolphin window

[via KDE Bugzilla]

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

Bug ID: 364026
   Summary: Crash when closing dolphin window
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: kyri...@alumni.princeton.edu

Application: kdeinit5 (15.12.3)

Qt Version: 5.6.0
Frameworks Version: 5.22.0
Operating System: Linux 4.5.5-201.fc23.x86_64 x86_64
Distribution: "Fedora release 23 (Twenty Three)"

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

I closed a dolphin window displaying the contents of a blu-ray disk by clicking
on the "x" on the top right corner.

The crash can be reproduced every time.

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

Thread 2 (Thread 0x7fe93b8e8700 (LWP 4319)):
#0  0x7fe96077170d in read () at /lib64/libc.so.6
#1  0x7fe95b538f45 in  () at /lib64/libnvidia-tls.so.340.96
#2  0x7fe95ee4d390 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#3  0x7fe95ee09c64 in g_main_context_check () at /lib64/libglib-2.0.so.0
#4  0x7fe95ee0a110 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#5  0x7fe95ee0a27c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#6  0x7fe9615b0a4b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#7  0x7fe9615594ca in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#8  0x7fe961382f34 in QThread::exec() () at /lib64/libQt5Core.so.5
#9  0x7fe9633744b5 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#10 0x7fe961387d48 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#11 0x7fe95ffbe60a in start_thread () at /lib64/libpthread.so.0
#12 0x7fe96078159d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fe9632b98c0 (LWP 4317)):
[KCrash Handler]
#5  0x7fe9606b3a28 in raise () at /lib64/libc.so.6
#6  0x7fe9606b562a in abort () at /lib64/libc.so.6
#7  0x7fe9606f6d7a in  () at /lib64/libc.so.6
#8  0x7fe9606ff1ca in _int_free () at /lib64/libc.so.6
#9  0x7fe96070272c in free () at /lib64/libc.so.6
#10 0x7fe96158516c in QMetaCallEvent::~QMetaCallEvent() () at
/lib64/libQt5Core.so.5
#11 0x7fe9615851c9 in QMetaCallEvent::~QMetaCallEvent() () at
/lib64/libQt5Core.so.5
#12 0x7fe96155dd3f in QCoreApplication::removePostedEvents(QObject*, int)
() at /lib64/libQt5Core.so.5
#13 0x7fe96158759a in QObjectPrivate::~QObjectPrivate() () at
/lib64/libQt5Core.so.5
#14 0x7fe961587749 in QObjectPrivate::~QObjectPrivate() () at
/lib64/libQt5Core.so.5
#15 0x7fe96158f60c in QObject::~QObject() () at /lib64/libQt5Core.so.5
#16 0x7fe9440e2859 in QXcbConnection::~QXcbConnection() () at
/lib64/libQt5XcbQpa.so.5
#17 0x7fe9440e4076 in QXcbIntegration::~QXcbIntegration() () at
/lib64/libQt5XcbQpa.so.5
#18 0x7fe9440e4179 in QXcbIntegration::~QXcbIntegration() () at
/lib64/libQt5XcbQpa.so.5
#19 0x7fe96189ef47 in QGuiApplicationPrivate::~QGuiApplicationPrivate() ()
at /lib64/libQt5Gui.so.5
#20 0x7fe961e8bd19 in QApplicationPrivate::~QApplicationPrivate() () at
/lib64/libQt5Widgets.so.5
#21 0x7fe96158f60c in QObject::~QObject() () at /lib64/libQt5Core.so.5
#22 0x7fe96155d1b2 in QCoreApplication::~QCoreApplication() () at
/lib64/libQt5Core.so.5
#23 0x7fe961e8d694 in QApplication::~QApplication() () at
/lib64/libQt5Widgets.so.5
#24 0x7fe94fec0d66 in kdemain () at /usr/lib64/libkdeinit5_dolphin.so
#25 0x55580c26eaaa in launch(int, char const*, char const*, char const*,
int, char const*, bool, char const*, bool, char const*) ()
#26 0x55580c26ff9e in handle_launcher_request(int, char const*) [clone
.isra.25] ()
#27 0x55580c2704cb in handle_requests(int) ()
#28 0x55580c268f5a in main ()

Reported using DrKonqi

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

[kscreenlocker] [Bug 181554] Screen keyboard when screen is locked

[matthias sweertvaegher via KDE Bugzilla]

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

matthias sweertvaegher  changed:

   What|Removed |Added

 CC||matthias.sweertvaegher@gmai
   ||l.com

--- Comment #6 from matthias sweertvaegher  
---
i have a virtual machine only accessible through RDP but after some time,
keyboard input stops working. Having a button on the lock screen to pop up a
virtual keyboard would help a lot..

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

[kdevelop] [Bug 364028] New: Large KDevelop project fails to open after upgrade

[via KDE Bugzilla]

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

Bug ID: 364028
   Summary: Large KDevelop project fails to open after upgrade
   Product: kdevelop
   Version: 4.90.91
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: aschm...@graphtek.com

Application: kdevelop (4.90.91)

Qt Version: 5.6.0
Frameworks Version: 5.22.0
Operating System: Linux 4.5.5-300.fc24.x86_64 x86_64
Distribution: "Fedora release 24 (Twenty Four)"

-- Information about the crash:
Other projects seem to have little problem, but my largest project crashes
kdevelop every time.

The interface appers with open documents from the previous session (4) and the
folder pane. However, it crashes before I can do anything useful, after about 4
seconds.

Previous version: 4.90.91 (self-compiled - worked).
Current version: 4.90.91.5 (Fedora 24 Beta - Distribution version).

The crash can be reproduced every time.

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

Thread 16 (Thread 0x7fafba7fc700 (LWP 18220)):
#0  0x7fb04af82bc0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fb04ca9a8a3 in JSC::GCThread::gcThreadMain() () at
/lib64/libQt5WebKit.so.5
#2  0x7fb04cdd6934 in WTF::wtfThreadEntryPoint(void*) () at
/lib64/libQt5WebKit.so.5
#3  0x7fb04af7d5ba in start_thread () at /lib64/libpthread.so.0
#4  0x7fb0514ab7cd in clone () at /lib64/libc.so.6

Thread 15 (Thread 0x7fafbaffd700 (LWP 18219)):
#0  0x7fb04af82bc0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fb04ca9a8a3 in JSC::GCThread::gcThreadMain() () at
/lib64/libQt5WebKit.so.5
#2  0x7fb04cdd6934 in WTF::wtfThreadEntryPoint(void*) () at
/lib64/libQt5WebKit.so.5
#3  0x7fb04af7d5ba in start_thread () at /lib64/libpthread.so.0
#4  0x7fb0514ab7cd in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7fafbb7fe700 (LWP 18218)):
#0  0x7fb04af82bc0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fb04ca9a8a3 in JSC::GCThread::gcThreadMain() () at
/lib64/libQt5WebKit.so.5
#2  0x7fb04cdd6934 in WTF::wtfThreadEntryPoint(void*) () at
/lib64/libQt5WebKit.so.5
#3  0x7fb04af7d5ba in start_thread () at /lib64/libpthread.so.0
#4  0x7fb0514ab7cd in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7fafbbfff700 (LWP 18217)):
#0  0x7fb04af82bc0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fb04ca99751 in JSC::BlockAllocator::blockFreeingThreadMain() () at
/lib64/libQt5WebKit.so.5
#2  0x7fb04cdd6934 in WTF::wtfThreadEntryPoint(void*) () at
/lib64/libQt5WebKit.so.5
#3  0x7fb04af7d5ba in start_thread () at /lib64/libpthread.so.0
#4  0x7fb0514ab7cd in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7fafd4d94700 (LWP 18216)):
#0  0x7fb0520b800b in QMutex::lock() () at /lib64/libQt5Core.so.5
#1  0x7fb0522edd2f in postEventSourcePrepare(_GSource*, int*) () at
/lib64/libQt5Core.so.5
#2  0x7fb048f29f7d in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#3  0x7fb048f2a96b in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#4  0x7fb048f2ab5c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#5  0x7fb0522ee69b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#6  0x7fb0522958ca in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#7  0x7fb0520bb3f3 in QThread::exec() () at /lib64/libQt5Core.so.5
#8  0x7fb0520c043f in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#9  0x7fb04af7d5ba in start_thread () at /lib64/libpthread.so.0
#10 0x7fb0514ab7cd in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7fb00187d700 (LWP 18215)):
#0  0x7fb04af82bc0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fb04cda5c3b in WTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQt5WebKit.so.5
#2  0x7fb04cda5c79 in  () at /lib64/libQt5WebKit.so.5
#3  0x7fb04af7d5ba in start_thread () at /lib64/libpthread.so.0
#4  0x7fb0514ab7cd in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7fafedfe4700 (LWP 15251)):
#0  0x7fb04af82bc0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fb0520c133b in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7fb04e8e2850 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#3  0x7fb04e8e6ed8 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#4  0x7fb04e8e1a73 in
ThreadWeaver::Weaver::applyForWork(ThreadWea

[kdenlive] [Bug 363734] Incorrect frame rate conversion

[Marcus Sundman via KDE Bugzilla]

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

--- Comment #3 from Marcus Sundman  ---
As I wrote, each frame in the video displays the timecode when that frame
starts. The video is VFR. The 1st frame is 1000ms long, the 2nd frame (which
starts at 00:01.000) is 993ms long, the 3rd frame (which starts at 00:01.993)
is 986ms long, etc.

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

[kdenlive] [Bug 363734] Incorrect frame rate conversion

[Marcus Sundman via KDE Bugzilla]

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

--- Comment #4 from Marcus Sundman  ---
Oh, and the issue is present in both the monitor and the final output.

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

[kdenlive] [Bug 363734] Incorrect frame rate conversion

[Marcus Sundman via KDE Bugzilla]

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

Marcus Sundman  changed:

   What|Removed |Added

Version|15.12.2 |16.04.0

--- Comment #5 from Marcus Sundman  ---
And it's there both in 15.12 and 16.04

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

[trojita] [Bug 364021] Sending mails hangs at 50 %

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #2 from Thomas Lübking  ---
Common fails:

nb. that *web.de* like gmail.com recently requires you to allow acces via smtp
(the defaults seemed to have been added randomly...)

For gmx, ensure to use the full mail address as login (tobias.leup...@gmx.de)
and smtp.gmx.de:465
Most importantly do not mix TLDs, ie. smtp.gmx.net won't work for *.de logins
et vv.

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

[dolphin] [Bug 364029] New: rename preview should at least compare size and date

[Manuel López-Ibáñez via KDE Bugzilla]

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

Bug ID: 364029
   Summary: rename preview should at least compare size and date
   Product: dolphin
   Version: 15.12.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: lopeziba...@gmail.com

When overwriting files that cannot be previewed, the "File Already Exists"
dialog shows just the names of the files. It could at least show the sizes and
dates (perhaps also the types as detected by 'file'?).  Note that even if the
files have an icon, the preview shows nothing (and thus, the dialog is
oversized). See attached screenshot.

Reproducible: Always

Steps to Reproduce:
1. touch ~/Desktop/bar.foo
2. touch ~/Downloads/bar.foo
3. Use dolphin to copy  ~/Downloads/bar.foo into ~/Desktop

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

[korganizer] [Bug 363875] holidays setting in korganizer always set back to none

[Wolfgang Bauer via KDE Bugzilla]

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

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||wba...@tmo.at

--- Comment #2 from Wolfgang Bauer  ---
Similar problem here in openSUSE (with KDE Applications 16.04.1/Korganizer
5.2.1 and Qt 5.6.0).

The setting does stick (longer than a minute), but there are no holidays shown
at all.
And after quitting and restarting Korganizer, it is back to "(None)", so it
doesn't seem to be saved either.

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

[dolphin] [Bug 364029] rename preview should at least compare size and date

[Manuel López-Ibáñez via KDE Bugzilla]

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

--- Comment #1 from Manuel López-Ibáñez  ---
Created attachment 99392
  --> https://bugs.kde.org/attachment.cgi?id=99392&action=edit
screenshot

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

[Akonadi] [Bug 294215] Maildir resource doesn't see subfolders.

[Simon Andric via KDE Bugzilla]

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[kdeconnect] [Bug 362684] "Send file via KDE Connect service" does not appear on file context menu despite being enabled in dolphin

[seawolf via KDE Bugzilla]

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

seawolf  changed:

   What|Removed |Added

 CC||sea.w...@alice.it

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

[kdenlive] [Bug 363951] Keeps randomly crashing (segfault) by just using it every couple of minutes

[via KDE Bugzilla]

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

--- Comment #6 from rol...@rptd.ch ---
GPU is a Radeon HD 7970 with Catalyst (
https://packages.gentoo.org/packages/x11-drivers/ati-drivers ).

Processing threads is already set to 1. What about concurrent threads?

Looking at the USE flags I would say OpenGL is already disabled:
kde-apps/kdenlive-15.12.3:5::gentoo  USE="handbook -debug -gles2 -v4l" 

Where is "moveit"? I can not find it in the configuration dialog.

Otherwise the RAM is certainly not the problem. I'm doing game-deving so the
machine is regularly stressed GPU/RAM wise.

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

[kmail2] [Bug 362710] Message list view does not show any text (invisible sender, subject, date etc)

[Wolfgang Bauer via KDE Bugzilla]

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

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||wba...@tmo.at

--- Comment #11 from Wolfgang Bauer  ---
I experienced the same problem here.

I was able to "fix" it by choosing a different theme in View->Message
List->Theme and then switching back to the original one.
As I do not have the problem any more now, it would seem to me that somehow
that setting got corrupted/imported incorrectly by the updated version...

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

[krita] [Bug 363769] Exporting to file format such as .png and .bmp appends extra period to filename

[Zafio via KDE Bugzilla]

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

Zafio  changed:

   What|Removed |Added

 CC||j...@zafio.com

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

[kdenlive] [Bug 363951] Keeps randomly crashing (segfault) by just using it every couple of minutes

[Wegwerf via KDE Bugzilla]

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

--- Comment #7 from Wegwerf  ---
OpenGL must be *enabled*, as Kdenlive relies on it for display. Movit is the
experimental GPU accel support, it's fine to have it off -- it's something
about use GPU acceleration or the like; I was just asking to ensure that this
is not caused by movit.

Concurrent threads can (and should) be set to a higher value, depending on your
system. Only processing threads=1 is important for now as otherwise the
timeline playhead won't respond correctly. Also just to be on the safe side
here.

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

[KBibTeX] [Bug 364030] New: String delimiters option not obeyed

[Fred Labrosse via KDE Bugzilla]

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

Bug ID: 364030
   Summary: String delimiters option not obeyed
   Product: KBibTeX
   Version: 0.6
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: Loading/saving files
  Assignee: fisc...@unix-ag.uni-kl.de
  Reporter: f...@aber.ac.uk

It used to be the case that I could set string delimiters to be quotes rather
than curly braces.  In fact, there is an option for that on the file settings
panel (why this is not accessible from the settings menu is a mystery to me). 
However, even if I set that to be "...", the delimiters of my file are changed
to {...}.

Reproducible: Always

Steps to Reproduce:
1. Open a file where string delimiters are quotes.
2. Check the option is set to be quotes.
3. Save the file.

Actual Results:  
The delimiters are now brackets.

Expected Results:  
The delimiters should be quotes.

In general, an application that opens a text file and saves it differently
without the user having done anything to the file is a bad idea.  I consider
this as similar to losing data.  Indeed, this implies that change tracking
(such as svn) will create a complete new file, when in fact the data is the
same.

This used to work.

Linked to that, other options on the panel are not remembered.  For example, I
have un-ticked the protect casing option (I do that myself if needed) and it
comes back the next time I open kbibtex.

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

[KBibTeX] [Bug 364030] String delimiters option not obeyed

[Fred Labrosse via KDE Bugzilla]

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

Fred Labrosse  changed:

   What|Removed |Added

 CC||f...@aber.ac.uk

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

[krita] [Bug 362869] Shortcuts not working after Configure Krita

[Zafio via KDE Bugzilla]

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

Zafio  changed:

   What|Removed |Added

 CC||j...@zafio.com

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

[krita] [Bug 364031] New: [Regression] Feather selection is too weak

[Spencer Brown via KDE Bugzilla]

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

Bug ID: 364031
   Summary: [Regression] Feather selection is too weak
   Product: krita
   Version: 3.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: sbrown...@gmail.com

Feather selection blurs the current selection. Its keyboard shortcut is
Shift+F6.

In 2.9 if you put in a radius of 100 you would get a nice, smooth, long blurred
transition. In 3.0 even if you put in a large number you only get a small
amount of feathering.

Reproducible: Always

Steps to Reproduce:
1. Make a selection.
2. Press Shift+F6 to feather it. Put a large number in the parameter field.
3. Paint across the border and note the small transition area.

Actual Results:  
The transition is much smaller than the number I put in.

Expected Results:  
The transition should be the same size as the number I put in.

I'm using the 3.0 release appimage on Ubuntu 16.04.

In the meantime I'm using a big soft eraser brush to get the large transitions
that I need for my work.

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

[plasmashell] [Bug 364032] New: Se cierra la barra KDE

[Sergio via KDE Bugzilla]

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

Bug ID: 364032
   Summary: Se cierra la barra KDE
   Product: plasmashell
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: silp1...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-22-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Al cambiar de red, se cierra la barra de inicio y me sale un error.

The crash can be reproduced every time.

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

Thread 17 (Thread 0x7f6a421ff700 (LWP 7620)):
#0  0x7f6a5092ee8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6a549f3c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f6a549f58d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f6a4497f629 in QXcbEventReader::run (this=0x2529a90) at
qxcbconnection.cpp:1253
#4  0x7f6a5102484e in QThreadPrivate::start (arg=0x2529a90) at
thread/qthread_unix.cpp:331
#5  0x7f6a501116fa in start_thread (arg=0x7f6a421ff700) at
pthread_create.c:333
#6  0x7f6a5093ab5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 16 (Thread 0x7f6a3b3ea700 (LWP 7624)):
#0  0x7f6a5092ee8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6a4d6c431c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6a4d6c442c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6a5125ba9b in QEventDispatcherGlib::processEvents
(this=0x7f6a340008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f6a51202dea in QEventLoop::exec (this=this@entry=0x7f6a3b3e9ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f6a5101f8a4 in QThread::exec (this=this@entry=0x26004f0) at
thread/qthread.cpp:503
#6  0x7f6a538c73c5 in QQmlThreadPrivate::run (this=0x26004f0) at
qml/ftw/qqmlthread.cpp:141
#7  0x7f6a5102484e in QThreadPrivate::start (arg=0x26004f0) at
thread/qthread_unix.cpp:331
#8  0x7f6a501116fa in start_thread (arg=0x7f6a3b3ea700) at
pthread_create.c:333
#9  0x7f6a5093ab5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 15 (Thread 0x7f6a2eb67700 (LWP 7625)):
#0  0x7f6a5092ee8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6a4d6c431c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6a4d6c442c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6a5125ba9b in QEventDispatcherGlib::processEvents
(this=0x7f6a280008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f6a51202dea in QEventLoop::exec (this=this@entry=0x7f6a2eb66ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f6a5101f8a4 in QThread::exec (this=this@entry=0x29b4a20) at
thread/qthread.cpp:503
#6  0x7f6a538c73c5 in QQmlThreadPrivate::run (this=0x29b4a20) at
qml/ftw/qqmlthread.cpp:141
#7  0x7f6a5102484e in QThreadPrivate::start (arg=0x29b4a20) at
thread/qthread_unix.cpp:331
#8  0x7f6a501116fa in start_thread (arg=0x7f6a2eb67700) at
pthread_create.c:333
#9  0x7f6a5093ab5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 14 (Thread 0x7f6a2cc7c700 (LWP 7626)):
#0  0x7f6a5092a9cd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6a4d7076c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6a4d6c3e04 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6a4d6c42c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f6a4d6c442c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f6a5125ba9b in QEventDispatcherGlib::processEvents
(this=0x7f6a28c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#6  0x7f6a51202dea in QEventLoop::exec (this=this@entry=0x7f6a2cc7bce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#7  0x7f6a5101f8a4 in QThread::exec (this=this@entry=0x2b681d0) at
thread/qthread.cpp:503
#8  0x7f6a538c73c5 in QQmlThreadPrivate::run (this=0x2b681d0) at
qml/ftw/qqmlthread.cpp:141
#9  0x7f6a5102484e in QThreadPrivate::start (arg=0x2b681d0) at
thread/qthread_unix.cpp:331
#10 0x7f6a501116fa in start_thread (arg=0x7f6a2cc7c700) at
pthread_create.c:333
#11 0x7f6a5093ab5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7f6a271c4700 (LWP 7627)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at

[kdeconnect] [Bug 363953] Touchpad input no longer work

[Albert Vaca via KDE Bugzilla]

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

Albert Vaca  changed:

   What|Removed |Added

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

--- Comment #3 from Albert Vaca  ---
I'm closing this bug, please reopen if still present.

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

[kaffeine] [Bug 363869] When Kaffeine is started on Plasma menu, It doesn't stop when the main window is closed

[Mauro Carvalho Chehab via KDE Bugzilla]

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

Mauro Carvalho Chehab  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||http://commits.kde.org/kaff
   ||eine/a8c0d4f81fad1777835d5d
   ||bd29b98824c60204cc
 Resolution|--- |FIXED

--- Comment #11 from Mauro Carvalho Chehab  ---
Git commit a8c0d4f81fad1777835d5dbd29b98824c60204cc by Mauro Carvalho Chehab.
Committed on 06/06/2016 at 17:25.
Pushed by mauroc into branch 'master'.

mainwindow: be sure to finish Kaffeine when the main window closes

Somehow, sometimes closing the main window is not exiting Kaffeine.

Fix that, by hooking the close() signal.

Signed-off-by: Mauro Carvalho Chehab 

M  +10   -0src/mainwindow.cpp
M  +1-0src/mainwindow.h

http://commits.kde.org/kaffeine/a8c0d4f81fad1777835d5dbd29b98824c60204cc

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

[trojita] [Bug 364021] Sending mails hangs at 50 %

[Tobias Leupold via KDE Bugzilla]

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

Tobias Leupold  changed:

   What|Removed |Added

 CC||tobias.leup...@web.de

--- Comment #3 from Tobias Leupold  ---
I thought port 465 was outdated and clients should use port 587? Just saying,
with KMail, I use mail.gmx.net:587 with my @gmx.de address and it works just
fine …

So here's what the console said:

With mail.gmx.net:587 and STARTTLS (which used to work just fine until
recently), I get:

SMTP ** connectToHost
SMTP <<< 220 gmx.com (mrgmx102) Nemesis ESMTP Service ready
SMTP >>> "EHLO localhost\r\n"
SMTP <<< 250-gmx.com Hello localhost [87.171.206.252]
SMTP <<< 250-SIZE 69920427
SMTP <<< 250-AUTH LOGIN PLAIN
SMTP <<< 250 STARTTLS
SMTP >>> STARTTLS
SMTP <<< 220 OK
SMTP ** startClientEncruption
SMTP >>> "EHLO localhost\r\n"
SMTP <<< 250-gmx.com Hello localhost [87.171.206.252]
SMTP <<< 250-SIZE 69920427
SMTP <<< 250 AUTH LOGIN PLAIN
SMTP >>> AUTH PLAIN

and then, it hangs.

With mail.gmx.net:465, I can't even connect when using STARTTLS: only:

SMTP ** connectToHost

And a message "The remote host closed the connection".

With both mail.gmx.net:465 and mail.gmx.de:465 and TLS instead of STARTTLS, I
get:

SMTP ** connectToHostEncrypted
SMTP >>> "EHLO localhost\r\n"
SMTP <<< 220 gmx.com (mrgmx102) Nemesis ESMTP Service ready
SMTP <<< 250-gmx.com Hello localhost [87.171.206.252]
SMTP <<< 250-SIZE 69920427
SMTP <<< 250 AUTH LOGIN PLAIN
SMTP >>> AUTH PLAIN

And it always hangs as described. So probably, the AUTH PLAIN step is what
causes the trouble?

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

[dolphin] [Bug 364029] rename preview should at least compare size and date

[Rog131 via KDE Bugzilla]

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

Rog131  changed:

   What|Removed |Added

 CC||samrog...@hotmail.com

--- Comment #2 from Rog131  ---
(In reply to Manuel López-Ibáñez from comment #0)
> When overwriting files that cannot be previewed, the "File Already Exists"
> dialog shows just the names of the files. It could at least show the sizes
> and dates (perhaps also the types as detected by 'file'?).  Note that even
> if the files have an icon, the preview shows nothing (and thus, the dialog
> is oversized). See attached screenshot.
> 
> Reproducible: Always
> 
> Steps to Reproduce:
> 1. touch ~/Desktop/bar.foo
> 2. touch ~/Downloads/bar.foo
> 3. Use dolphin to copy  ~/Downloads/bar.foo into ~/Desktop

The Dolphin 16.04.1 with the KDE Frameworks 5.22.0 is showing preview/icon,
date and size information when trying to overwite: 
http://i.imgur.com/bTJr9Q4.png

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

[kaffeine] [Bug 364018] systray icon is completely unusable, nothing happens when clicking on the icon

[Mauro Carvalho Chehab via KDE Bugzilla]

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

Mauro Carvalho Chehab  changed:

   What|Removed |Added

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

--- Comment #1 from Mauro Carvalho Chehab  ---
Fixed upstream. I added a menu with the 5 items that are at the main screen,
plus "quit". Using any of the items will restore the windows, if minimized.
changesets:

http://quickgit.kde.org/?p=kaffeine.git&a=commitdiff&h=f019c4ff39e11bd4d16ba406c40f3fa42c7680e2

http://quickgit.kde.org/?p=kaffeine.git&a=commitdiff&h=927c8d4f1c51a0cf8b4761c37a4c0c74868a9e9d

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

[kaffeine] [Bug 343987] kaffeine is not able to play over SMB network

[Mauro Carvalho Chehab via KDE Bugzilla]

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

Mauro Carvalho Chehab  changed:

   What|Removed |Added

Summary|kaffeine is not able to |kaffeine is not able to
   |play over network   |play over SMB network

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

[dolphin] [Bug 364029] rename preview should at least compare size and date

[Rog131 via KDE Bugzilla]

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

--- Comment #3 from Rog131  ---
I think that the problem was fixed with the:
https://bugs.kde.org/show_bug.cgi?id=356278 ->
https://quickgit.kde.org/?p=kio.git&a=commit&h=83578134b3ddb090248e6db1a699d9bdf7428fe0

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

[dolphin] [Bug 364029] rename preview should at least compare size and date

[Manuel López-Ibáñez via KDE Bugzilla]

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

Manuel López-Ibáñez  changed:

   What|Removed |Added

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

--- Comment #4 from Manuel López-Ibáñez  ---
That's awesome! I can wait until Kubuntu updates or backports.

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

[frameworks-kio] [Bug 361917] KRunner window blocks Kate session selection window

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

   Version Fixed In||5.7.0
  Latest Commit||http://commits.kde.org/plas
   ||ma-workspace/83eacf74ce6aba
   ||414a697747f3f2ac195e4e340b
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #7 from Kai Uwe Broulik  ---
Git commit 83eacf74ce6aba414a697747f3f2ac195e4e340b by Kai Uwe Broulik.
Committed on 06/06/2016 at 17:52.
Pushed by broulik into branch 'master'.

[Service Runner] Don't use KRun::runService

It blocks KRunner while the application is loading and in some cases
(like Kate's session selection dialog) might never return.
FIXED-IN: 5.7.0

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

M  +1-1runners/services/servicerunner.cpp

http://commits.kde.org/plasma-workspace/83eacf74ce6aba414a697747f3f2ac195e4e340b

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

[kdenlive] [Bug 348148] video speed adjustment changes clip truncation

[Michal Bocek via KDE Bugzilla]

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

Michal Bocek  changed:

   What|Removed |Added

 CC||mbo...@redhat.com

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

[krita] [Bug 352499] Crashed when I started using the brush

[Markus L via KDE Bugzilla]

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

--- Comment #17 from Markus L  ---
Well, i found solution to my problem, Krita crashing with Trust tablet.
Installing Linux to another harddisk.
Krita 3.0 works perfectly on Linux (Mint) using Trust graphic tablet. :)

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

[trojita] [Bug 364021] qwwsmtp prefers AUTH PLAIN, gmx announces PLAIN but actually only supports LOGIN. BOING.

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
Summary|Sending mails hangs at 50 % |qwwsmtp prefers AUTH PLAIN,
   ||gmx announces PLAIN but
   ||actually only supports
   ||LOGIN. BOING.
 Ever confirmed|0   |1
 Status|NEEDSINFO   |CONFIRMED

--- Comment #4 from Thomas Lübking  ---
smtps is more robust than starttls (at least in the gmx.net case, because if
anything goes wrong they fell back to the unencrypted variant which was oc.
blocked ... ;-)

465 is smtps, so starttls will naturally fail.

That said, it fails. The server will timeout and afterwards you'll get:

SMTP <<< 334 421 gmx.com Service closing transmission channel - command timeout
SMTP <<< [authentication data]

Nuking AuthPlain in qwwsmtpclient.cpp (ie. enforcing LOGIN) works like a charm.
PLAIN authentication on gmail works like a charm.

=> gmx broke PLAIN authentication and it's unfortunately preferred by qwwsmtp.

Since LOGIN is announced first, kmail will likely just use that (for the order)
Seems to have been a problem on kmail around 2005 as well:
https://bugs.kde.org/show_bug.cgi?id=67797#c70


=> I guess it would be required to either allow config of the preferred
authentication or prefer the announced order (what could be just as much
troublesome) or walk them on each timeout (what's oc. outmost crap, sending a
mail could easily last 10 minutes - every time!)

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