[krita] [Bug 372689] New: Crashing when I attempt to export a specific file.

[Martha Peck]

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

Bug ID: 372689
   Summary: Crashing when I attempt to export a specific file.
   Product: krita
   Version: 3.0
  Platform: Other
OS: OS X
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: martha.l.p...@gmail.com
  Target Milestone: ---

Created attachment 102326
  --> https://bugs.kde.org/attachment.cgi?id=102326=edit
The file that crashes

Whenever I attempt to save this specific file (attached) as anything other then
.kra, the program crashes instantly. I'm on macOS 10.12.1 and krita 3.0.93. On
a mid 2012 MacBook Pro. I've tried restarting the program and restarting the
computer itself. I've also tried both saving and exporting as a few different
file types (.jpeg, .png, and .psd) with the same results. 

Other files preform normally.

Thanks for the help, y'all!

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

[plasmashell] [Bug 372688] New: Plasma crashed trying to set up an Lync account

[Ismael Castiñeira Álvarez]

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

Bug ID: 372688
   Summary: Plasma crashed trying to set up an Lync account
   Product: plasmashell
   Version: 5.8.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: isma.ca...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.3)

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

-- Information about the crash:
- What I was doing when the application crashed:
Setting up a Lync account for the chat system.
- Custom settings of the application:
It never asked for login details, just added an empty account. Plasma crashed
trying to open that account's settings.

The crash can be reproduced sometimes.

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

Thread 11 (Thread 0x7ff7b5dfa700 (LWP 1494)):
#0  0x7ff8814c6f19 in syscall () at /usr/lib/libc.so.6
#1  0x7ff87c7d003a in g_cond_wait_until () at /usr/lib/libglib-2.0.so.0
#2  0x7ff87c75ee89 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7ff87c75f4ac in g_async_queue_timeout_pop () at
/usr/lib/libglib-2.0.so.0
#4  0x7ff87c7b2b9d in  () at /usr/lib/libglib-2.0.so.0
#5  0x7ff87c7b20d5 in  () at /usr/lib/libglib-2.0.so.0
#6  0x7ff880cc5454 in start_thread () at /usr/lib/libpthread.so.0
#7  0x7ff8814cb7df in clone () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7ff7aebc4700 (LWP 1461)):
#0  0x7ff8814c248d in poll () at /usr/lib/libc.so.6
#1  0x7ff87c78a786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7ff87c78ab12 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0
#3  0x7ff7bdf4e316 in  () at /usr/lib/libgio-2.0.so.0
#4  0x7ff87c7b20d5 in  () at /usr/lib/libglib-2.0.so.0
#5  0x7ff880cc5454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7ff8814cb7df in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7ff7b3eef700 (LWP 1460)):
#0  0x7ff8814be4ed in read () at /usr/lib/libc.so.6
#1  0x7ff87c7cea10 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7ff87c78a235 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7ff87c78a724 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7ff87c78a89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7ff87c78a8e1 in  () at /usr/lib/libglib-2.0.so.0
#6  0x7ff87c7b20d5 in  () at /usr/lib/libglib-2.0.so.0
#7  0x7ff880cc5454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7ff8814cb7df in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7ff7c63c6700 (LWP 1253)):
#0  0x7ff8814c248d in poll () at /usr/lib/libc.so.6
#1  0x7ff87c78a786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7ff87c78a89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7ff881de472b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7ff881d8e23a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7ff881bb10f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7ff7c88f20a7 in KCupsConnection::run() () at /usr/lib/libkcupslib.so
#7  0x7ff881bb5d78 in  () at /usr/lib/libQt5Core.so.5
#8  0x7ff880cc5454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7ff8814cb7df in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7ff7d1ba5700 (LWP 1092)):
#0  0x7ff8814c248d in poll () at /usr/lib/libc.so.6
#1  0x7ff87c78a786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7ff87c78a89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7ff881de472b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7ff881d8e23a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7ff881bb10f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7ff885ab0856 in  () at /usr/lib/libQt5Quick.so.5
#7  0x7ff881bb5d78 in  () at /usr/lib/libQt5Core.so.5
#8  0x7ff880cc5454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7ff8814cb7df in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7ff8621ff700 (LWP 1065)):
#0  0x7ff880ccb10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7ff88754cac4 in  () at /usr/lib/libQt5Script.so.5
#2  0x7ff88754cb09 in  () at /usr/lib/libQt5Script.so.5
#3  0x7ff880cc5454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7ff8814cb7df in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7ff863fff700 (LWP 1037)):
#0  0x7ff87c7cfdd4 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7ff87c789c7c in g_main_context_prepare () at

[kdm] [Bug 372687] New: User picture not showing up on login screen

[Bapusaheb Patil]

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

Bug ID: 372687
   Summary: User picture not showing up on login screen
   Product: kdm
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdm-bugs-n...@kde.org
  Reporter: bapoo1...@gmail.com
  Target Milestone: ---

When I boot up KDE Neon, my user profile picture is supposed to show up on the
login screen where I enter my password to login. But instead of showing a
custom picture of myself, which I selected from my library, it shows a
semi-transparent black avatar (the default one). 
I am currently running KDE Neon 5.8.3 User Edition.
I was previously running Kubuntu 16.10 and I didn't have this issue before, my
picture showed up perfectly fine on the login screen after bootup.

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

[kdevelop] [Bug 372686] New: KDevelop random crash during edit

[Cem Kalyoncu]

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

Bug ID: 372686
   Summary: KDevelop random crash during edit
   Product: kdevelop
   Version: 5.0.2
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: cemkalyo...@gmail.com
  Target Milestone: ---

Application: kdevelop (5.0.2)

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

-- Information about the crash:
KDevelop crashes while editing random parts of my project. It is a relatively
large custom CMake project. Crash occurs even while editing comments. You may
access the project in question at
https://bitbucket.org/darkgazeorg/gorgon-game-engine/branch/4.x-dev

The crash can be reproduced sometimes.

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

Thread 34 (Thread 0x7f95ad7fa700 (LWP 6157)):
#0  0x7f966ee1fbd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f966e8e9bc4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQt5Script.so.5
#2  0x7f966e8e9c09 in  () at /lib64/libQt5Script.so.5
#3  0x7f966ee1a5ca in start_thread () at /lib64/libpthread.so.0
#4  0x7f9675bcd0ed in clone () at /lib64/libc.so.6

Thread 33 (Thread 0x7f958f7fe700 (LWP 6145)):
#0  0x7f9675bc156d in poll () at /lib64/libc.so.6
#1  0x7f966c537a06 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f966c537b1c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f96769c724b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f96769765ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f96767d5343 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f9673db03cf in KDevelop::CompletionWorkerThread::run() () at
/lib64/libKDevPlatformLanguage.so.10
#7  0x7f96767d999a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f966ee1a5ca in start_thread () at /lib64/libpthread.so.0
#9  0x7f9675bcd0ed in clone () at /lib64/libc.so.6

Thread 32 (Thread 0x7f95ae7fc700 (LWP 6140)):
#0  0x7f966ee1fbd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f96767da01a in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f9672c608c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#3  0x7f9672c64a78 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#4  0x7f9672c5fa3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#5  0x7f9672c64ad2 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#6  0x7f9672c5fa3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#7  0x7f9672c62909 in ThreadWeaver::Thread::run() () at
/lib64/libKF5ThreadWeaver.so.5
#8  0x7f96767d999a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#9  0x7f966ee1a5ca in start_thread () at /lib64/libpthread.so.0
#10 0x7f9675bcd0ed in clone () at /lib64/libc.so.6

Thread 31 (Thread 0x7f95aeffd700 (LWP 6139)):
#0  0x7f966ee1fbd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f96767da01a in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f9672c608c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#3  0x7f9672c64a78 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#4  0x7f9672c5fa3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#5  0x7f9672c64ad2 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#6  0x7f9672c5fa3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#7  0x7f9672c64ad2 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#8  0x7f9672c5fa3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#9  0x7f9672c64ad2 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#10 

[kate] [Bug 351443] kate ask about file reload (changed outside) when exiting

[Oliver Sander]

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

Oliver Sander  changed:

   What|Removed |Added

 CC||oliver.san...@tu-dresden.de

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

[Oxygen] [Bug 372685] New: Oxygen theme style configuration icon out of place

[Marax Faraii]

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

Bug ID: 372685
   Summary: Oxygen theme style configuration icon out of place
   Product: Oxygen
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: style
  Assignee: hugo.pereira.da.co...@gmail.com
  Reporter: maraxfar...@gmail.com
  Target Milestone: ---

Created attachment 102325
  --> https://bugs.kde.org/attachment.cgi?id=102325=edit
Image showing the configuration icon

Apologies if this is the wrong place of filing this so please move it to
appropriate location.

Now, to the bug. Best way to describe it is in the title as well as attached
screenshot.

In the window decoration menu there are configuration icons above all the
various styles, except for oxygen. 
If the window is maximized the icon is visible but when it's not the icon
doesn't show at all.

Plasma version: 5.8.3
Kde Frameworks: 5.28.0
QT version: 5.6.2

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

[krita] [Bug 372677] Perspective transform loses entire layer content for full document layers

[Andy Statia]

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

--- Comment #2 from Andy Statia  ---
(In reply to elkmug from comment #1)
> I can reproduce this bug with Krita 3.0.93 on Win 7 64bit,
> but the described fix doesn't work for me.
> 
> Alternate workaround:
> Do steps 1-5 normally
> 6. Re position the whole transform, a small amount, WITHOUT touching the
> handles
> 7. Then use the handles to adjust as desired
> 8. Press Enter to apply the transform

For step 6 here, repositioning isn't needed, just getting to see the handles
with the scale transform (first one), then press Enter to accept it.  It should
apply the transform and the handles disappear.  Then click the layer again to
bring back the handles, choose the perspective mode, then try dragging a
handle.  At this point it should work.  This is demonstrated at 1:14 in the
YouTube video.  You can listen in the audio for the Enter key being pressed to
apply the transform.

What was done in the video at 1:14 is:

1. Transform tool selected
2. Click middle of layer (this causes the handles to display)
3. Scale transform mode is active (first transform mode)
4. Press Enter, transform is applied and handles vanish
5. Switch to perspective transform (second transform mode)
6. Click middle of layer (this causes the handles to display)
7. Drag top-left handle
8. Layer transforms in perspective properly

In your steps, I think you are just missing the "Enter" press to apply the
transform at least once before trying to use the perspective transform.  At
least one transform process must be applied before the perspective mode will
work.

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

[digikam] [Bug 372312] database upgrade v7 to v8 failed

[bugzilla_noreply]

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

e.longuem...@laposte.net changed:

   What|Removed |Added

 CC||e.longuem...@laposte.net

--- Comment #6 from e.longuem...@laposte.net ---
Hello,

You should maybe first write data from Digikam previous version to XMP files
using maintenance tools and then import them in updated Digikam.

That's the way I do it to get datas from Digikam 3.5 + mysql to digikam 5.3 +
mysql.

Eric

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

[digikam] [Bug 372684] New: No thumbnail shows for files larger than 2MB

[Rick]

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

Bug ID: 372684
   Summary: No thumbnail shows for files larger than 2MB
   Product: digikam
   Version: 5.3.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Thumbnails
  Assignee: digikam-de...@kde.org
  Reporter: r...@hallocks.us
  Target Milestone: ---

I just installed DigiKam 5.3.0 on Ubuntu 16.10. and copied my folders from my
old computer (let DigiKam make a new db).  Some pics don't show up in the the
thumbnail view. The count is correct in the albums tree, but only some or none
show up in the thumbnail view, they all show up in the Table view.
A quick sampling suggests any jpg files > 2MB are not showing up. 
"Thumbnail generation fails on large files" says to change "kcontrol->kde
components->file manager->Previes & Metadata (tab)->Maximum file size", but I
don't have that on Ubuntu!

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

[KScreen] [Bug 372632] The window does not fit on the screen

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #3 from Christoph Feck  ---


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

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

[KScreen] [Bug 354227] kcm_kscreen is too high

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||dev.dorr...@gmail.com

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

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

[digikam] [Bug 372683] Attempt to set a screen on a child window and DBusMenuExporterPrivate::fillLayoutItem No id for action

[bugzilla_noreply]

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

e.longuem...@laposte.net changed:

   What|Removed |Added

   Platform|Other   |Ubuntu Packages
Summary|void|Attempt to set a screen on
   |QWindowPrivate::setTopLevel |a child window and
   |Screen(QScreen*, bool) (|DBusMenuExporterPrivate::fi
   |QScreen(0x1285d40) ):   |llLayoutItem No id for
   |Attempt to set a screen on  |action
   |a child window  |

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

[karbon] [Bug 353816] garbage values in feConvolveMatrix kernel when size increased

[Anthony]

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

Anthony  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
 CC||bvb...@abv.bg

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

[karbon] [Bug 353816] garbage values in feConvolveMatrix kernel when size increased

[Anthony]

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

--- Comment #2 from Anthony  ---
Git commit 9d8146e05b96ba8245816a06e087f1cc88af2a2e by Anthony Fieroni.
Committed on 20/11/2016 at 04:13.
Pushed by anthonyfieroni into branch 'master'.

[shapefiltereffects] Update ControlMatrixEffect kernel accordingly to its
order.
+ Ability to save kernel changes

REVIEW: 129435

Signed-off-by: Anthony Fieroni 

M  +17   -0plugins/shapefiltereffects/ConvolveMatrixEffectConfigWidget.cpp

http://commits.kde.org/calligra/9d8146e05b96ba8245816a06e087f1cc88af2a2e

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

[digikam] [Bug 372683] New: void QWindowPrivate::setTopLevelScreen(QScreen*, bool) ( QScreen(0x1285d40) ): Attempt to set a screen on a child window

[bugzilla_noreply]

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

Bug ID: 372683
   Summary: void QWindowPrivate::setTopLevelScreen(QScreen*, bool)
( QScreen(0x1285d40) ): Attempt to set a screen on a
child window
   Product: digikam
   Version: 5.3.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: e.longuem...@laposte.net
  Target Milestone: ---

Hello,

I'm testing migration from my Digikam 3.5.0 setup to 5.3.0 (from Philips ppa)
and Ubuntu 16.04.

On my notebook I see some of those messages on Digikam  :

0x42e3670 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) (
QScreen(0x1285d40) ): Attempt to set a screen on a child window.

void DBusMenuExporterPrivate::fillLayoutItem(DBusMenuLayoutItem*, QMenu*, int,
int, const QStringList&): No id for action

No crash, but I can't find similar ones except foor Kate :
https://bugs.kde.org/show_bug.cgi?id=368903

I use standard Desktop Ubuntu with Unity.

Thanks,

Eric

PS : all have been right for mysql shared database

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

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

[Igor Zhuravlov]

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

Igor Zhuravlov  changed:

   What|Removed |Added

 CC|zhuravlov...@ya.ru  |

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

[kio] [Bug 367731] Dolphin does not show audio cd content

[Dr . Chapatin]

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

--- Comment #9 from Dr. Chapatin  ---
Installed kde apps 16.12 beta on Arch from kde_unstable repository... dolphin
does not show files from audio cd yet.

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

[Discover] [Bug 367526] Discover is not able to discover NO SEARCH RESULTS !!

[Cris]

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

--- Comment #3 from Cris  ---
I have this same issue  on my system I just installed a week ago. I have to
close Discover Software Center sometimes to get it to update installed apps and
search doesn't show results on any existing searches. I tried Chrome and
Firefox for example and no results appear. Any recommendations?

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

[Discover] [Bug 367526] Discover is not able to discover NO SEARCH RESULTS !!

[Cris]

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

Cris  changed:

   What|Removed |Added

 CC||crisllano...@gmail.com

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

[konsole] [Bug 212145] set TERM to support 256 colors

[Rex Dieter]

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

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@math.unl.edu

--- Comment #5 from Rex Dieter  ---
For what it's worth, fedora has defaulted to using xterm-256color for a few
releases, see also:
http://pkgs.fedoraproject.org/cgit/rpms/konsole5.git/tree/konsole-xterm-256color.patch

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

[plasmashell] [Bug 372391] f25 plasma "networks" and "instant messaging" icons are invisible.

[Rex Dieter]

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

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@math.unl.edu

--- Comment #4 from Rex Dieter  ---
The fedora theme is an exact copy of breeze + customized/fedora wallpaper

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

[plasmashell] [Bug 372682] New: Desktop crashed.

[Matthew]

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

Bug ID: 372682
   Summary: Desktop crashed.
   Product: plasmashell
   Version: 5.8.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: matthew.marshal...@yahoo.co.uk
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.3)

Qt Version: 5.7.0
Frameworks Version: 5.28.0
Operating System: Linux 4.4.31-2-MANJARO x86_64
Distribution: "Manjaro Linux"

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

Closing two Vivaldi windows and dragging a tab to a new window.

- Unusual behavior I noticed:

Plasma crashed, with the desktop and taskbar going black. On recovery icons
were missing for a while and an error window was displayed saying desktop.so
was non-functional.

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

Thread 17 (Thread 0x7fe0e700 (LWP 27083)):
#0  0x7fe212a474f0 in pa_fdsem_before_poll () at
/usr/lib/pulseaudio/libpulsecommon-9.0.so
#1  0x7fe212a5f0b7 in  () at /usr/lib/pulseaudio/libpulsecommon-9.0.so
#2  0x7fe2130cfb9c in pa_mainloop_dispatch () at /usr/lib/libpulse.so.0
#3  0x7fe2130cff9c in pa_mainloop_iterate () at /usr/lib/libpulse.so.0
#4  0x7fe2130d0040 in pa_mainloop_run () at /usr/lib/libpulse.so.0
#5  0x7fe2130de069 in  () at /usr/lib/libpulse.so.0
#6  0x7fe212a6eed8 in  () at /usr/lib/pulseaudio/libpulsecommon-9.0.so
#7  0x7fe21d9c1454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7fe21e1c77df in clone () at /usr/lib/libc.so.6

Thread 16 (Thread 0x7fe1057f8700 (LWP 17691)):
#0  0x7fe21d9c710f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe21e8b2c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe22281e395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe22281ec8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe21e8b1d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe21d9c1454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe21e1c77df in clone () at /usr/lib/libc.so.6

Thread 15 (Thread 0x7fe107ffd700 (LWP 13806)):
#0  0x7fe21d9c710f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe21e8b2c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe22281e395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe22281ec8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe21e8b1d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe21d9c1454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe21e1c77df in clone () at /usr/lib/libc.so.6

Thread 14 (Thread 0x7fe137ffe700 (LWP 13740)):
#0  0x7fe21d9c710f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe21e8b2c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe22281e395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe22281ec8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe21e8b1d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe21d9c1454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe21e1c77df in clone () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7fe1431c2700 (LWP 7776)):
#0  0x7fe21d9c710f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe21e8b2c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe22281e395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe22281ec8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe21e8b1d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe21d9c1454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe21e1c77df in clone () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7fe143fff700 (LWP 2360)):
#0  0x7fe21d9c710f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe21e8b2c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe22281e395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe22281ec8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe21e8b1d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe21d9c1454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe21e1c77df in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7fe148cb2700 (LWP 1548)):
#0  0x7fe21d9c710f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe21e8b2c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe22281e395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe22281ec8a in  () at 

[krita] [Bug 372677] Perspective transform loses entire layer content for full document layers

[bugzilla_noreply]

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

elk...@yahoo.com changed:

   What|Removed |Added

 CC||elk...@yahoo.com

--- Comment #1 from elk...@yahoo.com ---
I can reproduce this bug with Krita 3.0.93 on Win 7 64bit,
but the described fix doesn't work for me.

Alternate workaround:
Do steps 1-5 normally
6. Re position the whole transform, a small amount, WITHOUT touching the
handles
7. Then use the handles to adjust as desired
8. Press Enter to apply the transform

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[PhillB]

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

--- Comment #246 from PhillB  ---
Hi Michael,

I'd like to preface all comments with: I'm not an xorg.conf expert.

Having said that, it seems that your xorg.conf is not appropriate for a 3
screen layout. The layout clause only mentions sceenn0.

In my opinion you have to add screen1 and screen2 to the layout section so that
it (the layout section) is used. Because there is no mention of those screens I
suspect the X server will rely on a dynamic configuration (which will be wrong)
and your xorg.conf is being ignored.

Add screen1 and screen2 (and create screen1 and screen2 sections) to the layout
section and give them hard coordinates in the monitor section (see man page for
the "option" needed). Also add "primary" the appropriate monitor section.

The middle screen (screen0) cannot be located at 0,0 if you have screen1 on the
left and screen2 on the right (assumption on my part). Remember that the
coordinates are for the top left corner of the screen, and 0,0 is the top left
of the extended virtual screen. So if the monitors were all the same height
monitor0 might be at 1024,0 for example.

Hope this helps.

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

[frameworks-ki18n] [Bug 372681] New: Message with plural forms is not translated if only translation of plural form differs from msgid

[Lasse Liehu]

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

Bug ID: 372681
   Summary: Message with plural forms is not translated if only
translation of plural form differs from msgid
   Product: frameworks-ki18n
   Version: 5.28.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: caslav.i...@gmx.net
  Reporter: lasse.li...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

The following string from Finnish screenlocker_kcm.po is not translated
(msgid_plural is shown in the UI):
#. +> trunk5 stable5
#: kcm.cpp:55
msgctxt "Spinbox suffix. Short for minutes"
msgid " min"
msgid_plural " mins"
msgstr[0] " min"
msgstr[1] " min"

In this case msgstr[0] equals msgid but msgstr[1] differs from msgid_plural. If
msgstr[0] is changed to not equal msgid then the string is translated.

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

[systemsettings] [Bug 372520] non qt apps dont adopt colors

[jon]

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

--- Comment #4 from jon  ---
additional information: gtk apps inherit colors when using breeze or breeze
dark, but other color schemes dont

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

[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget

[CnZhx]

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

--- Comment #17 from CnZhx  ---
In addition to Comment 15  by 
Sebastian Kuhne, I found that if I did NOT select tasklist/to-do list of my
Google account within "Select Calendars" in "PIM Events Plugin" in "Digital
Clock Settings" page, plasmashell would NOT consume high memory and NOT crash.

In the previous Comment 10, I did not notice this.

Could anyone check on this results to confirm whether this problem is only with
the task list in Google calendar?

I am not sure if this "improvement" brought by the recent updated Plasma
Framework 5.28 or not. I am using openSUSE Tumbleweed 20161118 with KDE Plasma
5.8.3.

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

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

[dajomu]

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

Bug ID: 372680
   Summary: Cannot delete files from NAS
   Product: digikam
   Version: 5.3.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: AlbumsView
  Assignee: digikam-de...@kde.org
  Reporter: dajo...@gmail.com
  Target Milestone: ---

I am not able to delete photos stored on a NAS even though I can delete them
using file browser. I am using Ubuntu 16.10 and have mounted the NAS from the
fstab like this - //192.168.10.107/photo  /media/photos  cifs 
username=username,password=password,iocharset=utf8,sec=ntlm,users  0  0

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

[plasmashell] [Bug 353983] Turning off compositing breaks Plasma panel rendering

[bugzilla_noreply]

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

martc...@gmx.net changed:

   What|Removed |Added

 CC||martc...@gmx.net

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

[neon] [Bug 372283] digikam built without widget application style support

[Piotr Keplicz]

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

Piotr Keplicz  changed:

   What|Removed |Added

  Component|AdvancedRename  |Packages User Edition
Product|digikam |neon
 Status|RESOLVED|UNCONFIRMED
 Resolution|INVALID |---

--- Comment #3 from Piotr Keplicz  ---
According to bug 372284, Digikam isn't going to change the defaults. Please
change the CMake options in Neon packages.

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

[digikam] [Bug 372568] Krita (.kra) thumbnails are not showed

[Rafael]

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

--- Comment #4 from Rafael  ---
Hi Gilles

I tried the appimage, and sadly it shows nothing for KRA files (an empty
square) without any image content (canvas size) information. 

(In reply to caulier.gilles from comment #3)
> Well, i suspect a packaging problem.
> 
> To confirm try to use current development digiKam AppImage bundle for Linux
> available here :
> 
> https://drive.google.com/open?id=0BzeiVr-byqt5Y0tIRWVWelRJenM
> 
> Gilles Caulier

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

[plasmashell] [Bug 372651] Plasma crash after update

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
   Priority|NOR |LO
 Ever confirmed|0   |1

--- Comment #1 from David Edmundson  ---
That means we're hitting:
KPLUGININFO_ISVALID_ASSERTION

and we're using metadata object for an invalid metatadata. 
Grep shows the only direct calls to KPluginInfo::version are in ThemePrivate.

We're not handling a theme being removed (even if temporarily) at runtime.

It's a bug in our code, but it's pretty obscure.

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

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

[bugzilla_noreply]

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

Bug ID: 372679
   Summary: Crash when creating new document
   Product: krita
   Version: 3.0.1.1
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: OpenGL Canvas
  Assignee: krita-bugs-n...@kde.org
  Reporter: jeanlucpont...@gmail.com
  Target Milestone: ---

Fresh install. App crashes every time I try to create a new document from
template. Installed today and worked fine until I de-selected Open GL, then
re-selected (without restarting). The next time I opened it, and tried to
create a new document, it crashed. I have been unable to open it since. 

Also crashes now when trying to open an existing document. 

Tried reinstalling over existing, no luck.

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

[konsole] [Bug 212145] set TERM to support 256 colors

[Egmont Koblinger]

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

--- Comment #4 from Egmont Koblinger  ---
Coming from bug 371919: I'm strongly in favor of switching the default to
xterm-256color. It's a cool and useful feature, I see no reason to hold it back
from users.

In vte (gnome-terminal and friends) we've made this change 1.5 years ago (in
vte-0.40). A few people complained on askubuntu and friends that their vim
color scheme changed and they prefered the old one, they are happy with the
solution that they revert to TERM=xterm. We haven't heard about anything more
serious issue than this.

Most people are probably just silently happy to have more colors available out
of the box.

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

[konsole] [Bug 212145] set TERM to support 256 colors

[Egmont Koblinger]

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

Egmont Koblinger  changed:

   What|Removed |Added

 CC||egm...@gmail.com

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

[konsole] [Bug 371919] export COLORTERM=truecolor

[Egmont Koblinger]

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

--- Comment #6 from Egmont Koblinger  ---
Just occurred to me: _if_ terminfo's maintainer wasn't so much against true
colors, support would I guess be added in a way that the existing "tput colors"
reported 16 million. That is, it wouldn't have the concept of two orthogonal
features, rather than just one parameter set to 8, 16, 88, 256 or 16M. In other
words, I think it would make 256-color support a prerequisite for 16M.

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

[konsole] [Bug 371919] export COLORTERM=truecolor

[Egmont Koblinger]

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

Egmont Koblinger  changed:

   What|Removed |Added

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

--- Comment #5 from Egmont Koblinger  ---
Thanks for your patch! Reopening for some more discussion:

Your patch just made me realize that konsole doesn't even advertise 256-color
support (TERM is set to xterm rather than xterm-256color).

With this patch, it still doesn't advertise support for the pretty widespread
256-color feature, yet it advertises the less common true colors. This doesn't
make too much sense to me. S-lang also seems to obey these pieces of
information, and refuses to use the 256-color palette, yet allows true colors.

Strictly speaking, these are two orthogonal features, and theoretically there
could exist a terminal emulator that supports RGB but not the 256-color palette
(although I'd be really surprised if it turned out that there
exists/existed/will ever exist one). So one can kinda defend this behavior, we
could leave konsole as-is, and I could modify the Midnight Commander patch
accordingly.

In practice, since the true color feature is getting more and more popular
because 256 colors is not enough for some people, I'd say it's more practical
to think about it as the true color being something that might be implemented,
but only after you've got the 256-color palette anyways. MC's current
implementation also does this, it has a sanity check for 256-color support
according to terminfo before allowing true colors subject to COLORTERM, and
it's expected that if a skin definition mentions the usage of true colors then
256-colors are allowed too.

So the question is: Which direction do you think is the better?

Have you already considered, or could you please consider switching the default
to xterm-256color? That would simplify this situation a lot, actually we could
just ignore this problem. Has this perhaps been already discussed and rejected
for a reason? I found bug 212145 which seems to got forgotten, maybe time to
revive? (Just FYI: gnome-terminal changed the default to xterm-256color in
vte-0.40, released in March 2015.)

Thanks!

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

[frameworks-ktexteditor] [Bug 372629] [OS X] line height too low issue(s)

[Dominik Haumann]

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

--- Comment #12 from Dominik Haumann  ---
What about this in ::updateFontHeight?

-m_fontHeight = qMax(1, qFloor(height));
+m_fontHeight = qMax(1, qCeil(height));

Is this better?

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

[digikam] [Bug 372640] Can't drag any image file from digikam to GIMP

[Rafael]

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

--- Comment #7 from Rafael  ---
Apparentely, is not a GIMP issue

"XDND - Drag-and-Drop Protocol for the X Window System. XDND defines a standard
for drag and drop on X11. It is implemented by GTK+.
See also XDND specification. "

from https://wiki.gimp.org/wiki/Glossary

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

[kmail2] [Bug 372678] kmail not opening link

[Bob Miller]

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

--- Comment #2 from Bob Miller  ---
Another URL kmail will not open that used to work.

https://click-notification.capitalone.com/f/a/D6vccLFHBms6dQoXcdCxxA~~/AQA~/RgRZzBJWP0EIAKvWZ04VxXZXBmNhcG9uZVgEAEIKAAJWjelXR7nnQVIUcm1pbGxlcjYxa0BnbWFpbC5jb21QCzEwMDQ2X0VNTF8xUQQERIpodHRwOi8vbWkuY2FwaXRhbG9uZS5jb20vcC9jcC9mMjljNmJkNWM0OWMzYmFiL2M_QWNjb3VudEVuZGluZ0luPTQzMDkmdXJsPWh0dHAlM0ElMkYlMkZtaS5jYXBpdGFsb25lLmNvbSUyRnAlMkZycCUyRjlkMDIwMWFiMTgyYmM3MzElMkZ1cmxHZXsiaXNEcmFmdCI6ImZhbHNlIiwiYmluZGluZyI6InNlcnZpY2luZyIsImFsZXJ0VHJhY2tpbmdJZCI6IjQwMDAwMDAwMzY5ODcwMTQ4NCIsImFsZXJ0VHlwZSI6Ik9TUkVOSCJ9Ew~~

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

[kmail2] [Bug 372678] kmail not opening link

[Bob Miller]

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

--- Comment #1 from Bob Miller  ---
The links do open in other e-mail clients like thunderbird.

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

[kmail2] [Bug 372678] New: kmail not opening link

[Bob Miller]

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

Bug ID: 372678
   Summary: kmail not opening link
   Product: kmail2
   Version: 5.3.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: misc
  Assignee: kdepim-b...@kde.org
  Reporter: rmiller...@gmail.com
  Target Milestone: ---

kmail opens some links, but not others. Began about 2-3 weeks ago (early Nov
2016). Links fail to open regardless of which web browser is default (konq,
firefox, chrome).

Some links that kmail will not open. Older versions worked OK.
https://www.tep.com/
http://www.tep.com/doc/customer/tep-bill-back.pdf

Links that kmail will open
https://connect.secure.wellsfargo.com/auth/login/present?origin=cob=jukePassword=document=CONS
http://www.rentcafe.com/t/tec?ref=MTM0OTY1ODQ3-G3KKDv%2BL0p8%3D,NTc4NzM%3D-2jHqVXdhvms%3D

I cannot find any pattern between http vice https, long vice short, etc. URLs
as to what kmail will and will not open.

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

[kde-windows] [Bug 366596] Some KDE applications processes remain as background (zombie) processes after closing

[Jasem Mutlaq]

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

--- Comment #12 from Jasem Mutlaq  ---
I just emerged with Qt 5.8 and the bug is still there!! I first tried to emerge
KStars and upon exist, kstars.exe still remains in the background. Then I
emerged kate, and the exact same problem!

I thought this was fixed in Qt 5.8?!!

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

[konsole] [Bug 371919] export COLORTERM=truecolor

[Kurt Hindenburg]

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

Kurt Hindenburg  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kons
   ||ole/8c7f165ed6fe1b72e5dfecd
   ||1ab24deaddedf9fd6
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from Kurt Hindenburg  ---
Git commit 8c7f165ed6fe1b72e5dfecd1ab24deaddedf9fd6 by Kurt Hindenburg.
Committed on 19/11/2016 at 19:39.
Pushed by hindenburg into branch 'master'.

Add COLORTERM=truecolor to the environment

M  +1-1src/Profile.cpp

http://commits.kde.org/konsole/8c7f165ed6fe1b72e5dfecd1ab24deaddedf9fd6

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

[okular] [Bug 363298] Allow users to define custom stamp to use with the review functions.

[Robert Cabane]

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

--- Comment #4 from Robert Cabane  ---
As of Okular 0.24, it's really possible to create personal stamps, see here :
https://wiki.ubuntuusers.de/Okular/
However, the exported PDF file doesn't show the personal stamps with any other
viewer as Okular (tested with Evince and the pdf viewers included in FireFox or
Chrome).

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

[okular] [Bug 159007] Personal gallery od stamps

[Robert Cabane]

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

Robert Cabane  changed:

   What|Removed |Added

 CC||rcab...@free.fr

--- Comment #9 from Robert Cabane  ---
(In reply to kdebug from comment #8)
> There is a way now to add a custom image (svg, png) to a stamp (description
> here -> http://wiki.ubuntuusers.de/Okular)
> With "Save as.." it is even possible to write annotations down to the
> PDF-file. 
> 
> Unfortunately, those notifications are not shown by common PDF Viewers 
> (Adobe Reader, PDF-Master,...) Neither it is possible to print them to a new
> PDf File (which seems to work just for text-annotations)
I agree. Just the same with Okular 0.24 (under OpenSuSE) : the stamp is really
included in the exported PDF file (whose size grows), but in a special manner,
which isn't compatible with Adobe Reader.
Hopefully one will find how to fix that ...

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

[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU

[Oscar Fuentes]

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

--- Comment #4 from Oscar Fuentes  ---
Mine is an ATI HD6450 (also R600) using the radeon non-propietary driver.

No problems with VLC.

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

[frameworks-ktexteditor] [Bug 372629] [OS X] line height too low issue(s)

[RJVB]

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

--- Comment #11 from RJVB  ---
What other OSes have you tried?

I guess it must have something to do with the font engine, an observation that
I think is supported by the fact that the adjustment isn't required when I use
the Freetype font engine on OS X.

Sadly the Freetype font engine isn't really ready for prime time on OS X; it
doesn't appear to use FontConfig for one, and it requires the use of a
commandline argument without any way the make it the default as far as I have
seen.

To what extent do you intervene in the standard Qt text rendering mechanisms,
iow to what extent could this be considered a Qt bug?

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

[digikam] [Bug 370428] Tool-Tip Text is Unreadable In File and digiKam Properties

[bugzilla_noreply]

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

--- Comment #3 from hardy.pub...@gmail.com ---
Thanks for the hint. I was only using Default but I just tried all the themes.
Most are unreadable, some are partially readable, and 3 are OK. So for now,
I'll just use one I can read.

Not Readable. White font on light background.
  Default
  Black Body
  DarkRoom
  High Key
  White Balance

Difficult To Read. Light gray font on light background.
  SunsetColor
  GrayCard

Readable. Dark gray font on light background.
  LowKey
  ShadeOfGray
  ColorContrast

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

[krita] [Bug 372677] New: Perspective transform loses entire layer content for full document layers

[Andy Statia]

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

Bug ID: 372677
   Summary: Perspective transform loses entire layer content for
full document layers
   Product: krita
   Version: 3.1 Beta
  Platform: Windows CE
OS: Windows CE
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: transform
  Assignee: krita-bugs-n...@kde.org
  Reporter: asta...@neverdot.com
  Target Milestone: ---

When using the perspective transform tool on a full page document layer, the
layer content vanishes when a handle is dragged.  If one presses Enter to
accept the transform, it gets stuck at 33%.  It can be worked around by first
using a normal scaling transform, apply it (no size change needed), then use
the perspective transform, which then works.

1. Create a new document
2. Fill the layer with a colour and paint on the top layer a bit
3. Select the transform tool
4. Switch to the perspective transform mode
5. Click on the layer to see the handles
6. Drag one of the corner handles
7. The layer will now vanish, along with the handles and outline
8. Press Enter to accept the transform
9. Note that the transformation progress on the layer gets stuck at 33%

Workaround:
Steps 1-3 normally
4. Select the scale transform
5. Click the layer to see the handles
6. Press Enter to apply this transform (no handles need to be moved)
7. Switch to the perspective transform
8. Click the layer to see the handles
9. Drag the handles and transform in perspective as expected
10. Press Enter to apply the transform, it will complete properly.

A video demonstration of this bug can be found here:

https://www.youtube.com/watch?v=HVJrdqR-6M4

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

[i18n] [Bug 372675] several kde-l10n 16.12 beta packages fail to build

[Antonio Rojas]

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

Antonio Rojas  changed:

   What|Removed |Added

  Component|general |es
   Assignee|aa...@kde.org   |kde-l10n...@kde.org

--- Comment #2 from Antonio Rojas  ---
Sorry, my mistake when looking at the output. en_GB works fine also here, yes.

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

[i18n] [Bug 372675] several kde-l10n 16.12 beta packages fail to build

[Albert Astals Cid]

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

--- Comment #1 from Albert Astals Cid  ---
en-GB works fine here https://paste.kde.org/pqyini5xn

es fails with this error, yes

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

[digikam] [Bug 372312] database upgrade v7 to v8 failed

[boospy]

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

--- Comment #5 from boospy  ---
Migration to SQLite is also not possible. The idea was first migrate to sqlite
and then back to mysql.

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

[cantor] [Bug 372676] New: julia backend doesn't build

[Antonio Rojas]

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

Bug ID: 372676
   Summary: julia backend doesn't build
   Product: cantor
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: fil...@kde.org
  Reporter: aro...@archlinux.org
CC: alexanderrie...@gmail.com
  Target Milestone: ---

The julia backend fails to build in 16.12 beta with the error

[ 77%] Building CXX object
src/backends/julia/tests/CMakeFiles/testjulia.dir/testjulia.cpp.o
In file included from
/build/cantor/src/cantor-16.11.80/src/backends/julia/tests/testjulia.cpp:20:0:
/build/cantor/src/cantor-16.11.80/src/backends/julia/tests/testjulia.h:22:25:
fatal error: backendtest.h: No such file or directory
 #include 
 ^
compilation terminated.

Also, please make building tests conditional on the BUILD_TESTING cmake
variable.

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

[krita] [Bug 372646] Unable to pan after picking color from reference image until canvas is clicked once first

[Andy Statia]

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

--- Comment #5 from Andy Statia  ---
Awesome!  I recorded a video of the replication as well in case it is useful.

https://www.youtube.com/watch?v=pfk94vmyrK8

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

[i18n] [Bug 372675] New: several kde-l10n 16.12 beta packages fail to build

[Antonio Rojas]

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

Bug ID: 372675
   Summary: several kde-l10n 16.12 beta packages fail to build
   Product: i18n
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aa...@kde.org
  Reporter: aro...@archlinux.org
  Target Milestone: ---

At least en-GB and es fail at cmake with the error:

CMake Error at /usr/lib64/cmake/KF5DocTools/KF5DocToolsMacros.cmake:156
(add_custom_target):
  add_custom_target cannot create target
  "5-es-docs-pim-kleopatra-index-cache-bz2" because another target with the
  same name already exists.  The existing target is a custom target created
  in source directory
  "/build/kde-l10n/src/kde-l10n-es-16.11.80/5/es/docs/pim/kleopatra".  See
  documentation for policy CMP0002 for more details.
Call Stack (most recent call first):
  5/es/docs/pim/kleopatra/CMakeLists.txt:3 (kdoctools_create_handbook)


CMake Error at /usr/lib64/cmake/KF5DocTools/KF5DocToolsMacros.cmake:156
(add_custom_target):
  add_custom_target cannot create target
  "5-es-docs-pim-kwatchgnupg-index-cache-bz2" because another target with the
  same name already exists.  The existing target is a custom target created
  in source directory
  "/build/kde-l10n/src/kde-l10n-es-16.11.80/5/es/docs/pim/kwatchgnupg".  See
  documentation for policy CMP0002 for more details.
Call Stack (most recent call first):
  5/es/docs/pim/kwatchgnupg/CMakeLists.txt:3 (kdoctools_create_handbook)


-- Configuring incomplete, errors occurred!

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

[kwin] [Bug 372663] KWin crashes when using a Qt4 application

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---
As a workaround use the default breeze window decoration.

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

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

[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

 CC||teu...@gmail.com

--- Comment #62 from Martin Gräßlin  ---
*** Bug 372663 has been marked as a duplicate of this bug. ***

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

[digikam] [Bug 372312] database upgrade v7 to v8 failed

[boospy]

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

boospy  changed:

   What|Removed |Added

 CC||li...@osit.cc

--- Comment #4 from boospy  ---
Affected too. Kubuntu 16.04 with ppa

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

[kwin] [Bug 372669] Chrome scroll bar snaps back when ending scroll bar drag with cursor outside the window

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---
Please try again with XWayland 1.19. I consider it as likely to be fixed there.

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

[digikam] [Bug 370428] Tool-Tip Text is Unreadable In File and digiKam Properties

[bugzilla_noreply]

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

--- Comment #2 from caulier.gil...@gmail.com ---
Which color scheme theme do you use in Settings menu ?

Gilles Caulier

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

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

[bugzilla_noreply]

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

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

   What|Removed |Added

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

--- Comment #1 from caulier.gil...@gmail.com ---
Can you share some picture processed with Picassa to investigate. Sound like
face tags are miss-interpreted in metadata parser while importing.

Gilles Caulier

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

[digikam] [Bug 123097] SCAN : ignore some directories in digiKam [patch]

[bugzilla_noreply]

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

--- Comment #34 from caulier.gil...@gmail.com ---
Jan,

Any progress to complete the patch before 5.4.0 release planed in December ?

Gilles Caulier

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

[digikam] [Bug 372284] digikam disables application style support by default

[bugzilla_noreply]

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

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

   What|Removed |Added

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

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

[digikam] [Bug 372369] Digikam crashes when executing BatchQueueManager

[bugzilla_noreply]

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

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

   What|Removed |Added

 Resolution|--- |BACKTRACE
 Status|UNCONFIRMED |RESOLVED

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

[digikam] [Bug 372369] Digikam crashes when executing BatchQueueManager

[bugzilla_noreply]

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

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

   What|Removed |Added

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

--- Comment #1 from caulier.gil...@gmail.com ---
We need more information to investigate, as console trace with DebugView for
ex, or where is source code DK stop, through MS Visual C++.

See instructions here :

https://www.digikam.org/contrib

Gilles Caulier

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

[digikam] [Bug 372284] digikam disables application style support by default

[bugzilla_noreply]

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

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

   What|Removed |Added

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

--- Comment #1 from caulier.gil...@gmail.com ---
And what's the problem. Switch the flag to on in this case...

Gilles Caulier

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

[kipiplugins] [Bug 334045] MediaWiki option not available in Export menu when plugin activated.

[bugzilla_noreply]

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

--- Comment #6 from caulier.gil...@gmail.com ---
Can you reproduce the problem use last digiKam Linux AppImage bundle ?

https://drive.google.com/open?id=0BzeiVr-byqt5Y0tIRWVWelRJenM

Typically I cannot here. Mediawiki tool still here.

Gilles Caulier

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

[digikam] [Bug 372427] Some pictures do not display

[bugzilla_noreply]

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

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

   What|Removed |Added

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

--- Comment #4 from caulier.gil...@gmail.com ---
The database can be re-constructed from scratch safety if you store all DK
information in image files metadata.

In all case, make a backup of database.

Gilles Caulier

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

[digikam] [Bug 372481] Face tag assignment with copy/paste

[bugzilla_noreply]

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

--- Comment #4 from caulier.gil...@gmail.com ---
Stephano,

Did you try with current development AppImage bundle for Linux ?

Gilles Caulier

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

[dolphin] [Bug 372673] Small mouse scrolling step

[Mihai Sorin Dobrescu]

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

Mihai Sorin Dobrescu  changed:

   What|Removed |Added

 CC||msdobre...@gmail.com

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

[dolphin] [Bug 372674] New: Refresh action selects items in the folders panel

[Mihai Sorin Dobrescu]

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

Bug ID: 372674
   Summary: Refresh action selects items in the folders panel
   Product: dolphin
   Version: 16.08.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: panels: folders
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: msdobre...@gmail.com
  Target Milestone: ---

After selecting an item in the folders panel (the view to the right), after
changing the selection and refreshing, the items between the two positions are
selected.

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

[dolphin] [Bug 372674] Refresh action selects items in the folders panel

[Mihai Sorin Dobrescu]

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

Mihai Sorin Dobrescu  changed:

   What|Removed |Added

 CC||msdobre...@gmail.com

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

[digikam] [Bug 372568] Krita (.kra) thumbnails are not showed

[bugzilla_noreply]

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

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

   What|Removed |Added

Version|5.5.0   |5.3.0

--- Comment #3 from caulier.gil...@gmail.com ---
Well, i suspect a packaging problem.

To confirm try to use current development digiKam AppImage bundle for Linux
available here :

https://drive.google.com/open?id=0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[digikam] [Bug 372672] File Renaming Options sidebar is missing

[bugzilla_noreply]

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

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

   What|Removed |Added

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

--- Comment #1 from caulier.gil...@gmail.com ---
No problem using digiKam AppImage bundle for Linux.

Try with current development version available here :

https://drive.google.com/open?id=0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[dolphin] [Bug 372673] New: Small mouse scrolling step

[Mihai Sorin Dobrescu]

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

Bug ID: 372673
   Summary: Small mouse scrolling step
   Product: dolphin
   Version: 16.08.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: panels: folders
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: msdobre...@gmail.com
  Target Milestone: ---

The vertical scrolling using the mouse wheel is slow. It happens on two
separate installations. KDE is set as default to scroll 3 lines at a time. It
seems it needs two full scroll gestures (meaning moving the mouse wheel
scrolling from its front to the back, on the entire length of its visible part)
in order to scroll a line of text. This is common to all the panels except to
the files and folders view.

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

[digikam] [Bug 372672] New: File Renaming Options sidebar is missing

[John]

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

Bug ID: 372672
   Summary: File Renaming Options sidebar is missing
   Product: digikam
   Version: 5.1.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Import-Rename
  Assignee: digikam-de...@kde.org
  Reporter: jrussell...@yahoo.com.sg
  Target Milestone: ---

The File Renaming Options sidebar is missing on Digikam5.

Build 4:5.1.0-wily~ppa1 on Ubuntu 15.10 x64

I've installed and re-installed this version several times on two machines with
the same results. Digikam 4.14.0 has the sidebar.

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

[kalzium] [Bug 372671] New: solver doesn't build with ocaml 4.04

[Antonio Rojas]

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

Bug ID: 372671
   Summary: solver doesn't build with ocaml 4.04
   Product: kalzium
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kalz...@kde.org
  Reporter: aro...@archlinux.org
  Target Milestone: ---

The solver fails to build with ocaml 4.04:

[ 49%] Generating solver.o
cd /build/kalzium/src/build/src && /usr/bin/ocamlopt -output-obj -o
/build/kalzium/src/build/src/solver.o /usr/lib/ocaml/facile/facile.cmxa
/build/kalzium/src/build/src/chemset.cmx
/build/kalzium/src/build/src/parser.cmx /build/kalzium/src/build/src/lexer.cmx
/build/kalzium/src/build/src/datastruct.cmx
/build/kalzium/src/build/src/chem.cmx /build/kalzium/src/build/src/calc.cmx
[ 50%] Generating modwrap.o
cd /build/kalzium/src/build/src && /usr/bin/ocamlopt -I /usr/lib/ocaml/facile
-c /build/kalzium/src/kalzium-16.11.80/src/solver/modwrap.c -o
/build/kalzium/src/build/src/modwrap.o
Options -c and -o are incompatible when compiling C files
make[2]: *** [src/CMakeFiles/kalzium.dir/build.make:105: src/modwrap.o] Error 2
make[2]: Leaving directory '/build/kalzium/src/build'
make[1]: *** [CMakeFiles/Makefile2:302: src/CMakeFiles/kalzium.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs

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

[kwin] [Bug 371494] Support color temperature adjustments in Wayland (like Redshift in X11 or f.lux)

[Roman Gilg]

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

Roman Gilg  changed:

   What|Removed |Added

 CC||subd...@gmail.com

--- Comment #1 from Roman Gilg  ---
Can confirm. Tried your steps to reproduce. Eyes hurt.

I would even go a little bit further: On X you need to install an additional
plasmoid. I would like to have this feature per default in Plasma, because it's
per default on Android and even activated there.

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

[calligrawords] [Bug 372670] New: crash when try to open file

[bugzilla_noreply]

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

Bug ID: 372670
   Summary: crash when try to open file
   Product: calligrawords
   Version: 2.9.11
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: calligra-words-bugs-n...@kde.org
  Reporter: don-redhat-...@isis.cs3-inc.com
  Target Milestone: ---

Application: calligrawords (2.9.11)
KDE Platform Version: 4.14.25
Qt Version: 4.8.7
Operating System: Linux 4.8.6-201.fc24.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:
file - open
I can supply the file
How much more info do I need to supply in order to get the report accepted?

-- Backtrace:
Application: Calligra Words (calligrawords), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f583751f940 (LWP 18021))]

Thread 2 (Thread 0x7f580d8f0700 (LWP 18037)):
#0  0x7f5830eb556d in poll () from /lib64/libc.so.6
#1  0x7f582bd8da06 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f582bd8db1c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f5831e0c47e in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQtCore.so.4
#4  0x7f5831dda7bf in
QEventLoop::processEvents(QFlags) () from
/lib64/libQtCore.so.4
#5  0x7f5831ddab25 in
QEventLoop::exec(QFlags) () from
/lib64/libQtCore.so.4
#6  0x7f5831cc9af9 in QThread::exec() () from /lib64/libQtCore.so.4
#7  0x7f5831dba613 in QInotifyFileSystemWatcherEngine::run() () from
/lib64/libQtCore.so.4
#8  0x7f5831ccc3ca in QThreadPrivate::start(void*) () from
/lib64/libQtCore.so.4
#9  0x7f5831a2f5ca in start_thread () from /lib64/libpthread.so.0
#10 0x7f5830ec10ed in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f583751f940 (LWP 18021)):
[KCrash Handler]
#6  0x7f5832f7692c in QTextLine::y() const () from /lib64/libQtGui.so.4
#7  0x7f58308ede02 in KoTextDocumentLayout::positionAnchorTextRanges(int,
int, QTextDocument const*) () from /lib64/libkotextlayout.so.14
#8  0x7f58308d6683 in KoTextLayoutArea::layoutBlock(FrameIterator*) () from
/lib64/libkotextlayout.so.14
#9  0x7f58308d90cb in KoTextLayoutArea::layout(FrameIterator*) () from
/lib64/libkotextlayout.so.14
#10 0x7f58308ebded in KoTextLayoutRootArea::layoutRoot(FrameIterator*) ()
from /lib64/libkotextlayout.so.14
#11 0x7f58308ef15d in KoTextDocumentLayout::doLayout() () from
/lib64/libkotextlayout.so.14
#12 0x7f58308ef7e8 in KoTextDocumentLayout::layout() () from
/lib64/libkotextlayout.so.14
#13 0x7f5831df5db1 in QObject::event(QEvent*) () from /lib64/libQtCore.so.4
#14 0x7f5832d07edc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQtGui.so.4
#15 0x7f5832d0eddc in QApplication::notify(QObject*, QEvent*) () from
/lib64/libQtGui.so.4
#16 0x7f5836f41df5 in KoApplication::notify(QObject*, QEvent*) () from
/lib64/libkomain.so.14
#17 0x7f5831ddbeed in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /lib64/libQtCore.so.4
#18 0x7f5831ddf556 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQtCore.so.4
#19 0x7f5831e0c2ee in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQtCore.so.4
#20 0x7f582bd8d6ba in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#21 0x7f582bd8da70 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#22 0x7f582bd8db1c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#23 0x7f5831e0c45e in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQtCore.so.4
#24 0x7f5832db05b6 in
QGuiEventDispatcherGlib::processEvents(QFlags)
() from /lib64/libQtGui.so.4
#25 0x7f5831ddf89f in
QCoreApplication::processEvents(QFlags) () from
/lib64/libQtCore.so.4
#26 0x7f5834e0ad4f in KoProgressUpdater::update() () from
/lib64/libkowidgetutils.so.14
#27 0x7f5831df0090 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from /lib64/libQtCore.so.4
#28 0x7f5831df0090 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from /lib64/libQtCore.so.4
#29 0x7f5834e0c251 in KoUpdater::sigProgress(int) () from
/lib64/libkowidgetutils.so.14
#30 0x7f5834e0c2e7 in KoUpdater::setProgress(int) () from
/lib64/libkowidgetutils.so.14
#31 0x7f5836f4dcbb in KoDocument::openFile() () from /lib64/libkomain.so.14
#32 0x7f5836f56cf9 in KoDocument::openUrlInternal(KUrl const&) () from
/lib64/libkomain.so.14
#33 0x7f5836f57128 in KoDocument::openUrl(KUrl const&) () from
/lib64/libkomain.so.14
#34 0x7f5836f6139c in KoMainWindow::openDocumentInternal(KUrl const&,
KoPart*, KoDocument*) () from /lib64/libkomain.so.14
#35 

[ark] [Bug 368530] [clizip] Unable to open the file after rename it

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/ark/
   ||aacfc786ddb0098dc6fdda4a89e
   ||6f9133a542507
   Version Fixed In||16.12.0
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #5 from Elvis Angelaccio  ---
Git commit aacfc786ddb0098dc6fdda4a89e6f9133a542507 by Elvis Angelaccio.
Committed on 19/11/2016 at 16:32.
Pushed by elvisangelaccio into branch 'Applications/16.12'.

clizip: fix renaming files in the root

Renaming files in the root folder was broken with clizip. Test case was
also missing.
FIXED-IN: 16.12.0

M  +7-0autotests/kerfuffle/movetest.cpp
M  +4-3plugins/clizipplugin/cliplugin.cpp

http://commits.kde.org/ark/aacfc786ddb0098dc6fdda4a89e6f9133a542507

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

[frameworks-ktexteditor] [Bug 372629] [OS X] line height too low issue(s)

[Christoph Cullmann]

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

--- Comment #10 from Christoph Cullmann  ---
Hmm, any idea why we need that adjust? Seems strange, given no problem on other
operating systems.

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

[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU

[José JORGE]

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

--- Comment #3 from José JORGE  ---
(In reply to knossos456 from comment #2)
> Have you same problem with VLC (because newest Kaffeine is based on VLC
> core) ?
> For me and ATI 5450, all is OK (VLC and Kaffeine) for VDPAU and ubuntu 16.04
> ( under 3% cpu usage
> Please post your graphical card model

It is an ATI HD3200 (R600 GPU integrated in the motherbord). I have no problems
when using directly VLC.

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

[krita] [Bug 372646] Unable to pan after picking color from reference image until canvas is clicked once first

[Alexey Putz]

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

--- Comment #4 from Alexey Putz  ---
Thanks for your comment, I was able to reproduce this bug. 

1. Open the reference image toolbar.(Settings - Dockers - Reference images)
2. Open an image at the toolbar.
3. Open an image in primary document window.
4. Use color picking tool at the reference image.
5. Quickly slide the cursor back on the primary document window image.
6. Bag occurs. While pressing hotkey for Pan the pan mode is not activated, the
cursor stays in the color picking mode representation.


Note: If cursor slided very smooth over the bound between the reference image
area and main document window the bug doesn't occur.



Krita version 3.0.93

Kubuntu 16.10
KDE Plasma Version : 5.7.5
KDE Frameworks Version : 5.26.0
Qt Version : 5.6.1
Kernel Version : 4.8.0-22-generic
OS Type: 64-bit

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

[kaffeine] [Bug 371190] Kaffeine 2.0.4 doesn't scan DVB-S

[knossos456]

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

knossos456  changed:

   What|Removed |Added

 CC||knossos...@gmail.com

--- Comment #2 from knossos456  ---
Same here with lowest C/N and V2.05
was ok with v1.22, perhaps AGC problem ?

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

[kaffeine] [Bug 371579] Kaffeine 2.0.5 unresponsive on certain DVB-S channels

[knossos456]

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

knossos456  changed:

   What|Removed |Added

 CC||knossos...@gmail.com

--- Comment #1 from knossos456  ---
Same problem here.
Seems to be a AGC problem, I have problems with lowests C/N and v 2.05 , was ok
with 1.22

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

[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU

[knossos456]

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

knossos456  changed:

   What|Removed |Added

 CC||knossos...@gmail.com

--- Comment #2 from knossos456  ---
Have you same problem with VLC (because newest Kaffeine is based on VLC core) ?
For me and ATI 5450, all is OK (VLC and Kaffeine) for VDPAU and ubuntu 16.04 (
under 3% cpu usage
Please post your graphical card model

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

[kwin] [Bug 372669] New: Chrome scroll bar snaps back when ending scroll bar drag with cursor outside the window

[Kai Uwe Broulik]

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

Bug ID: 372669
   Summary: Chrome scroll bar snaps back when ending scroll bar
drag with cursor outside the window
   Product: kwin
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@privat.broulik.de
  Target Milestone: ---

(Besides the fact that scrollbar snapback breaks Fitts' law in spectacular ways
and no toolkit on Linux besides Aura does it)

When you drag the scroll bar in a Chrome window (xwayland) and release the
mouse button with the mouse outside the Chrome window whilst keeping the mouse
close enough so it doesn't snap back, it will snap back to the previous scroll
position nonetheless after you released the mouse.

1.) Open Chrome in a Wayland session and open some website
2.) Resize the window so there's a vertical scrollbar and make the window
non-maximized (or add a top panel)
3.) Press and hold the scroll bar with the mouse
4.) Now scroll in any direction
5.) Move the mouse outside the Chrome window but keep it close enough so Chrome
doesn't already automatically snap back
6.) Release mouse button

If the mouse hovers another X window (doesn't need to be a Chrome window, can
be any Xwayland client, just stack it behind the Chrome window) then releasing
the mouse while over that window won't snap it back.

It seems that the mouse release event doesn't get proper coordinates because X
only gets the mouse position while inside an X client? Or don't we even set the
X cursor back to 0,0 to ensure hover effects and what not reset?

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

[krita] [Bug 372537] Animation export fails when using .msi version

[Scott Petrovic]

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

--- Comment #4 from Scott Petrovic  ---
Git commit 5ea2b338f91875d216d7fbd1ec30b345c0bd5a5e by Scott Petrovic, on
behalf of Boudewijn Rempt.
Committed on 19/11/2016 at 15:23.
Pushed by scottpetrovic into branch 'petrovic/impex-brush-editor-ui'.

Refactor the filename requester and filedialog

The messing with relative paths to the default folder meant that
the user never could be sure which path we were going to save to.

Rendering to GIF still fails, though, but I need more brain to
figure out why.
Related: bug 372572

M  +2-2libs/ui/KisMainWindow.cpp
M  +9-10   libs/widgets/kis_file_name_requester.cpp
M  +3-5libs/widgetutils/KoFileDialog.cpp
M  +1-1libs/widgetutils/KoFileDialog.h
M  +3-1plugins/extensions/animationrenderer/DlgAnimationRenderer.cpp
M  +2-2plugins/impex/video/video_saver.cpp

http://commits.kde.org/krita/5ea2b338f91875d216d7fbd1ec30b345c0bd5a5e

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

[konsole] [Bug 372441] Konsole Desktop file missing StartupWMClass

[Aniketh]

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

--- Comment #9 from Aniketh  ---
If its good to go. Then merge it in behave of me. Thanks in advance :)

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

[konsole] [Bug 372441] Konsole Desktop file missing StartupWMClass

[Kurt Hindenburg]

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

--- Comment #8 from Kurt Hindenburg  ---
Thanks, I don't see any difference under Plasma - I'll check under gnome

WM_CLASS(STRING) = "konsole", "konsole"

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

[kdenlive] [Bug 372668] New: Render a clip results in a black video with any of the available file formats.

[bugzilla_noreply]

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

Bug ID: 372668
   Summary: Render a clip results in a black video with any of the
available file formats.
   Product: kdenlive
   Version: 16.08.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: walter.buetiko...@livenet.ch
  Target Milestone: ---

Choose a clip on the timeline; made my choices on the render Dialog for video
output. Started render process.
In any cases it always resulted in a black video with no sound.

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

[krita] [Bug 372646] Unable to pan after picking color from reference image until canvas is clicked once first

[Andy Statia]

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

--- Comment #3 from Andy Statia  ---
In your replication steps, I don't see where you opened a reference image to
choose a colour from.  If I do the steps as noted by you, it also works for me.
 The issue only arises if you pick a colour from the image in the reference
image panel, not from the current document.


(In reply to Alexey Putz from comment #2)
> Hello. 
> I tried it and I didn't reproduce the bug.
> I used Krita from page : 
> 
> https://krita.org/en/item/krita-3-1-beta-4-released/
> 
> Krita version 3.0.93
> 
> 1. Opened an image.
> 2. Used the pick color tool, color was successfully picked.
> 3. Used pan shortcut (space), the icon of colorpicker was successfully
> changed to the icon of pan (hand).
> 4. Navigated with pan without need to click before pan.
> 5. Used ctrl+r shortcut, the icon changed successfully, selected a
> rectangular area.
> 6. Used Pan with shortcut space. 
> 
> 
> Kubuntu 16.10
> KDE Plasma Version : 5.7.5
> KDE Frameworks Version : 5.26.0
> Qt Version : 5.6.1
> Kernel Version : 4.8.0-22-generic
> OS Type: 64-bit

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

[krita] [Bug 372110] On creating a new view in a new window, the tool options disappear in the first window

[Scott Petrovic]

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

Scott Petrovic  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/krit |http://commits.kde.org/krit
   |a/89727e94b616d08666c94c6d5 |a/7760309b39fadc791dcb5e590
   |2f5f0b3a3641404 |5a9464d7971c3f3

--- Comment #3 from Scott Petrovic  ---
Git commit 7760309b39fadc791dcb5e5905a9464d7971c3f3 by Scott Petrovic, on
behalf of Dmitry Kazakov.
Committed on 19/11/2016 at 15:23.
Pushed by scottpetrovic into branch 'petrovic/impex-brush-editor-ui'.

Fix hiding Tool Options widgets when a new window is created

The problem is:

1) All the main windows are connected to
   KoToolManager::toolOptionWidgetsChanged() signal.
2) But different main windows do not share the tools.
3) Therefore the main windows should check if the signal
   was emitted by its own tool.
Fixes T4264

M  +2-2libs/flake/KoToolManager.cpp
M  +1-1libs/flake/KoToolManager.h
M  +13   -3libs/ui/KisMainWindow.cpp
M  +2-1libs/ui/KisMainWindow.h

http://commits.kde.org/krita/7760309b39fadc791dcb5e5905a9464d7971c3f3

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

[krita] [Bug 372572] [appimage] export GIF animation is broken, specific to appimage

[Scott Petrovic]

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

--- Comment #3 from Scott Petrovic  ---
Git commit 5ea2b338f91875d216d7fbd1ec30b345c0bd5a5e by Scott Petrovic, on
behalf of Boudewijn Rempt.
Committed on 19/11/2016 at 15:23.
Pushed by scottpetrovic into branch 'petrovic/impex-brush-editor-ui'.

Refactor the filename requester and filedialog

The messing with relative paths to the default folder meant that
the user never could be sure which path we were going to save to.

Rendering to GIF still fails, though, but I need more brain to
figure out why.
Related: bug 372537

M  +2-2libs/ui/KisMainWindow.cpp
M  +9-10   libs/widgets/kis_file_name_requester.cpp
M  +3-5libs/widgetutils/KoFileDialog.cpp
M  +1-1libs/widgetutils/KoFileDialog.h
M  +3-1plugins/extensions/animationrenderer/DlgAnimationRenderer.cpp
M  +2-2plugins/impex/video/video_saver.cpp

http://commits.kde.org/krita/5ea2b338f91875d216d7fbd1ec30b345c0bd5a5e

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

[krita] [Bug 369349] Low framerate when drawing with the stabilizer

[Scott Petrovic]

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

--- Comment #19 from Scott Petrovic  ---
Git commit 66d3859309dc409a164bfa4841d43a28c144315a by Scott Petrovic, on
behalf of Alvin Wong.
Committed on 19/11/2016 at 15:23.
Pushed by scottpetrovic into branch 'petrovic/impex-brush-editor-ui'.

Fix bent stabilizer finishing line segment
Maniphest Tasks: T4182

M  +5-1libs/ui/tool/kis_stabilized_events_sampler.cpp
M  +3-3libs/ui/tool/kis_tool_freehand_helper.cpp

http://commits.kde.org/krita/66d3859309dc409a164bfa4841d43a28c144315a

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

[krita] [Bug 372221] Pop-up palette color selector - difficult to select colors.

[Scott Petrovic]

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

--- Comment #6 from Scott Petrovic  ---
Git commit 16c1586c6708cfec62e57a371d7b07f787800390 by Scott Petrovic, on
behalf of Boudewijn Rempt.
Committed on 19/11/2016 at 15:23.
Pushed by scottpetrovic into branch 'petrovic/impex-brush-editor-ui'.

Improve rendering speed of the Visual Color Selector

* Convert all colors for the colorselector to a QImage in one go

M  +1-1libs/ui/widgets/KisVisualColorSelector.cpp
M  +51   -43   libs/ui/widgets/KisVisualColorSelectorShape.cpp
M  +4-4libs/ui/widgets/KisVisualColorSelectorShape.h

http://commits.kde.org/krita/16c1586c6708cfec62e57a371d7b07f787800390

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

[krita] [Bug 370193] Save file didn't save work

[Scott Petrovic]

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

Scott Petrovic  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/krit |http://commits.kde.org/krit
   |a/c7eb0977e020b849810eb2756 |a/46283124c08c4af705b483a1f
   |19f8aa87eb616bc |39c733fa54e1bfe

--- Comment #5 from Scott Petrovic  ---
Git commit 46283124c08c4af705b483a1f39c733fa54e1bfe by Scott Petrovic, on
behalf of Boudewijn Rempt.
Committed on 19/11/2016 at 15:23.
Pushed by scottpetrovic into branch 'petrovic/impex-brush-editor-ui'.

Port the save-saving patch from 3.1

This restores the delayed saving dialog, which is now even weirder,
with a cancel running operating button which mostly doesn't work,
a do not save button, and a don't care, save a broken copy button.

See also

https://phabricator.kde.org/D3258
https://phabricator.kde.org/T4220
https://bugs.kde.org/show_bug.cgi?id=370566
https://bugs.kde.org/show_bug.cgi?id=369368
https://bugs.kde.org/show_bug.cgi?id=370193

M  +52   -12   libs/ui/KisDocument.cpp
M  +14   -0libs/ui/KisDocument.h
M  +4-1libs/ui/dialogs/kis_delayed_save_dialog.cpp
M  +26   -8libs/ui/dialogs/kis_delayed_save_dialog.ui
M  +2-2plugins/impex/bmp/kis_bmp_export.cpp
M  +9-12   plugins/impex/brush/kis_brush_export.cpp
M  +2-2plugins/impex/csv/csv_saver.cpp
M  +1-6plugins/impex/exr/exr_export.cc
M  +2-4plugins/impex/heightmap/kis_heightmap_export.cpp
M  +1-3plugins/impex/jpeg/kis_jpeg_export.cc
M  +2-2plugins/impex/kra/kra_converter.cpp
M  +1-2plugins/impex/kra/kra_export.cpp
M  +1-1plugins/impex/ora/ora_export.cc
M  +1-1plugins/impex/png/kis_png_export.cc
M  +1-4plugins/impex/ppm/kis_ppm_export.cpp
M  +1-1plugins/impex/psd/psd_saver.cpp
M  +1-1plugins/impex/qml/qml_export.cc
M  +3-3plugins/impex/spriter/kis_spriter_export.cpp
M  +2-2plugins/impex/tga/kis_tga_export.cpp
M  +5-8plugins/impex/tiff/kis_tiff_export.cc

http://commits.kde.org/krita/46283124c08c4af705b483a1f39c733fa54e1bfe

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

[krita] [Bug 369349] Low framerate when drawing with the stabilizer

[Scott Petrovic]

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

Scott Petrovic  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/krit |http://commits.kde.org/krit
   |a/11f0acc2ce291a020c7b53eb3 |a/7d9d92a9bbcda54321c4d3515
   |8a547a095553c00 |0688829356d8e08

--- Comment #18 from Scott Petrovic  ---
Git commit 7d9d92a9bbcda54321c4d35150688829356d8e08 by Scott Petrovic, on
behalf of Alvin Wong.
Committed on 19/11/2016 at 15:23.
Pushed by scottpetrovic into branch 'petrovic/impex-brush-editor-ui'.

Work around low framerate of stabilizer

Work around low framerate of stabilizer by delaying and painting the
stroke progressively.

The `KisStabilizerDelayedPaintHelper` class collects the sampled events
and distributes them evenly with a timestamp attached, then a timer firing
at a closer interval would paint the line bit by bit in order to give a
smoother user feedback.

The config option `stabilizerDelayedPaintInterval` with default value `20`
controls the paint interval. The delayed painting is disabled if this
value is higher than `stabilizerSampleSize`, which means it is disabled by
default on non-Windows system.
Maniphest Tasks: T4182
Differential Revision: https://phabricator.kde.org/D3321

M  +1-0libs/ui/CMakeLists.txt
M  +13   -0libs/ui/kis_config.cc
M  +3-0libs/ui/kis_config.h
A  +85   -0libs/ui/tool/KisStabilizerDelayedPaintHelper.cpp [License:
GPL (v2+)]
A  +86   -0libs/ui/tool/KisStabilizerDelayedPaintHelper.h [License: GPL
(v2+)]
M  +44   -5libs/ui/tool/kis_tool_freehand_helper.cpp

http://commits.kde.org/krita/7d9d92a9bbcda54321c4d35150688829356d8e08

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

[Breeze] [Bug 361811] Breeze causes hangs and crashes in Krita

[Scott Petrovic]

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

Scott Petrovic  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/krit |http://commits.kde.org/krit
   |a/1ae3767cc2b09040f8c4d12bd |a/187f8d60261c365fcc82d0cfb
   |09f372759ab19b9 |c2fed542ef704f2

--- Comment #22 from Scott Petrovic  ---
Git commit 187f8d60261c365fcc82d0cfbc2fed542ef704f2 by Scott Petrovic, on
behalf of Boudewijn Rempt.
Committed on 19/11/2016 at 15:23.
Pushed by scottpetrovic into branch 'petrovic/impex-brush-editor-ui'.

Allow the breeze style

After a week of testing with current breeze, there are no apparent
problems.

M  +1-1libs/ui/KisApplication.cpp

http://commits.kde.org/krita/187f8d60261c365fcc82d0cfbc2fed542ef704f2

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