[plasmashell] [Bug 394119] New: Panel does not auto-hide while any window wants attention

2018-05-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=394119

Bug ID: 394119
   Summary: Panel does not auto-hide while any window wants
attention
   Product: plasmashell
   Version: 5.11.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: triffid.hun...@gmail.com
  Target Milestone: 1.0

Created attachment 112573
  --> https://bugs.kde.org/attachment.cgi?id=112573&action=edit
Patch to prevent panel un-hiding when a window wants attention

I love an auto-hiding panel.

However, if any window wants attention, the panel will *never* hide until I
have given focus to each and every attention-seeking window across all
desktops. This infuriates me.

The attached patch fixes this behaviour, so the panel will only appear when I
mouse over its activation area or it's being configured, but not if windows
want attention.

I expect there's a more elegant/appropriate way to do it, but I'm not familiar
with KDE's codebase so I started here.

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

[krusader] [Bug 191860] Resizing the krusader window (making it smaller) is made at the expense of the Name column and truncates file names

2018-05-10 Thread Nikita Melnichenko
https://bugs.kde.org/show_bug.cgi?id=191860

Nikita Melnichenko  changed:

   What|Removed |Added

 CC||krusader-bugs-n...@kde.org,
   ||nikita+...@melnichenko.name
 Ever confirmed|0   |1
Version|unspecified |Git
   Assignee|man...@users.sourceforge.ne |krusader-bugs-n...@kde.org
   |t   |
 Status|UNCONFIRMED |CONFIRMED

--- Comment #2 from Nikita Melnichenko  ---
Still the case for current git.

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

[krusader] [Bug 393766] "Open terminal here" action opens shell in home directory

2018-05-10 Thread Nikita Melnichenko
https://bugs.kde.org/show_bug.cgi?id=393766

Nikita Melnichenko  changed:

   What|Removed |Added

 CC||nikita+...@melnichenko.name
 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #11 from Nikita Melnichenko  ---
Please provide your krusaderui.rc, you may have an incorrect binding.

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

[krusader] [Bug 393983] fish protocol not available on ubuntu 18.04

2018-05-10 Thread Nikita Melnichenko
https://bugs.kde.org/show_bug.cgi?id=393983

Nikita Melnichenko  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO
 CC||nikita+...@melnichenko.name

--- Comment #3 from Nikita Melnichenko  ---
Please let us know if installing packages mentioned by Toni helped.

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

[krusader] [Bug 330789] Option for show copy/move progress in dialog (not in notifications)

2018-05-10 Thread Nikita Melnichenko
https://bugs.kde.org/show_bug.cgi?id=330789

Nikita Melnichenko  changed:

   What|Removed |Added

 CC||toddandma...@zoho.com

--- Comment #3 from Nikita Melnichenko  ---
*** Bug 393866 has been marked as a duplicate of this bug. ***

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

[krusader] [Bug 393866] missing progress bar

2018-05-10 Thread Nikita Melnichenko
https://bugs.kde.org/show_bug.cgi?id=393866

Nikita Melnichenko  changed:

   What|Removed |Added

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

--- Comment #7 from Nikita Melnichenko  ---
The solution is to use Job Toolbar for non-KDE systems. Please read the latest
Krusader docbook on this.

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

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

[kgraphviewer] [Bug 394116] Copyright declarations are inconsistent and unclear

2018-05-10 Thread Nicolás Alvarez
https://bugs.kde.org/show_bug.cgi?id=394116

Nicolás Alvarez  changed:

   What|Removed |Added

 CC||nicolas.alva...@gmail.com

--- Comment #1 from Nicolás Alvarez  ---
- The KDE Licensing Policy (https://community.kde.org/Policies/Licensing_Policy
p4/p5) lists what licenses can be used for application source files. Several
source files are GPLv2-only, which is not an option there, they should be
v2-or-later or v3-or-later.

- The KDE Licensing Policy (p13) says CMake modules should be BSD-licensed, but
FindGraphviz.cmake is LGPL2.1+.

- org.kde.kgraphviewer.appdata.xml says the app is GPL-2.0+, which isn't true,
since many source files don't have "or later".

- Some source files have "Copyright Gael de Chalendar, GPLv2", and another
paragraph saying "Copyright Jarosław Staniek, LGPL2 or later". I think there
should be just one comment header with both copyright lines, and no mention of
LGPL (relicensing LGPL2+ to GPL2 is possible and it's unnecessary to say what
the license used to be).

- While I don't know if it's legally required, some people seem to have done
significant (copyrightable) contributions and aren't listed in the copyright
comment lines.

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

[kopete] [Bug 394118] New: Participant window not get updated based on chat tab selected!!!

2018-05-10 Thread droidSumit
https://bugs.kde.org/show_bug.cgi?id=394118

Bug ID: 394118
   Summary: Participant window not get updated based on chat tab
selected!!!
   Product: kopete
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Main Application
  Assignee: kopete-bugs-n...@kde.org
  Reporter: droidsu...@gmail.com
  Target Milestone: ---

Hi,

It has been observed with the latest version of Kopete when multiple chat tabs
are open and if I change the tab from one person to other person participant
sidebar doesn't get updated accordingly.

KDE Frameworks 5.45.0
Qt 5.10.0 (built against 5.10.0)
The xcb windowing system

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

[krita] [Bug 394117] New: Transparency masks of Group Layers are not applied when converting to OpenRaster

2018-05-10 Thread Alex Gleason
https://bugs.kde.org/show_bug.cgi?id=394117

Bug ID: 394117
   Summary: Transparency masks of Group Layers are not applied
when converting to OpenRaster
   Product: krita
   Version: 4.0.2
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: File formats
  Assignee: krita-bugs-n...@kde.org
  Reporter: a...@alexgleason.me
  Target Milestone: ---

Steps to reproduce:

1. Create a group layer.
2. Create three paint layers below it, and scribble around in each.
3. Create a transparency layer for the group layer.
4. Paint the transparency layer so it hides parts of the entire group layer.
5. Export the file to OpenRaster (*.ora) format.
6. Close the file and reopen the *.ora.
7. The effect of the transparency layer will be gone entirely and three paint
layers will be fully visible.

Expected result:

When converting to OpenRaster, the group layer's transparency mask is applied
to each child layer, one at a time, so that the pixels are erased in the output
and the *.ora looks the same as the *.kra when viewed normally.

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

[kgraphviewer] [Bug 394116] New: Copyright declarations are inconsistent and unclear

2018-05-10 Thread Simon Quigley
https://bugs.kde.org/show_bug.cgi?id=394116

Bug ID: 394116
   Summary: Copyright declarations are inconsistent and unclear
   Product: kgraphviewer
   Version: 2.4.2
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kl...@free.fr
  Reporter: tsimo...@ubuntu.com
  Target Milestone: ---

In this package, you have a mix of GPL 2 source files, GPL 2+ source files, and
LGPL 2.1+ source files, with cmake/FindGraphviz.cmake having an interesting
header:

"Under the terms of Contract DE-AC04-94AL85000 with Sandia Coroporation, the
U.S. Government retains certain rights in this software."

This certainly doesn't seem standard.

Additionally, in a lot of the source files, it states what the license is, then
what the license was previously. This makes it really unclear for software
distributors such as Debian who need to have clear and explicit copyright
declarations.

Please fix this.

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

[frameworks-kio] [Bug 394115] New: Unable to read filenames in KDirOperator, because sections are not resizable

2018-05-10 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=394115

Bug ID: 394115
   Summary: Unable to read filenames in KDirOperator, because
sections are not resizable
   Product: frameworks-kio
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Open/save dialogs
  Assignee: fa...@kde.org
  Reporter: cf...@kde.org
CC: kdelibs-b...@kde.org
  Target Milestone: ---

Created attachment 112572
  --> https://bugs.kde.org/attachment.cgi?id=112572&action=edit
Screenshot demonstrating the issue

Steps to reproduce:
- Use "Filesystem Browser" plugin in Kate
- Set its view mode to 'Detailed View'

Actual result:
- Unreadable file names, see screenshot

Expected result:
- Either the section is resized automatically to show the filename, or it
respects a user set (and saved) size, as with previous versions.

This is a regression in KF5 5.46.0.

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

[kwin] [Bug 393284] KWin Segfault Regression in Plasma 5.12.4 re Fall Apart + Desktop Grid.

2018-05-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=393284

--- Comment #11 from kdem...@protonmail.com ---
I do hope that sooner or later the root cause might be eliminated. until then
however, i continue to run with *Fall Apart* disabled, as this way everything
works very nicely. One day it would be nice to be able to use FA again...

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

[akregator] [Bug 394114] Akregator 5.7.3 crash at opening an article

2018-05-10 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=394114

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #2 from Christoph Feck  ---
Correct.

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

[drkonqi] [Bug 391187] Duplicate search needs to search for both 'crash' and 'normal' severity

2018-05-10 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=391187

--- Comment #15 from Christoph Feck  ---
Yes, users could specify a severity when reporting tickets, both via DrKonqi
and the web interface.

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

[akregator] [Bug 394114] Akregator 5.7.3 crash at opening an article

2018-05-10 Thread Pedro
https://bugs.kde.org/show_bug.cgi?id=394114

--- Comment #1 from Pedro  ---
I've tracked the problem, and it seems to be a known bug in nouveau drivers.
Here are the related QT and nouveau bug reports:
https://bugreports.qt.io/browse/QTBUG-41242
https://bugs.freedesktop.org/show_bug.cgi?id=91632

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

[drkonqi] [Bug 391187] Duplicate search needs to search for both 'crash' and 'normal' severity

2018-05-10 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=391187

--- Comment #14 from Nate Graham  ---
Before the change, did users previously have the ability to set the Severity?
Is that why this was working before?

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

[krita] [Bug 392282] No x2 splash screen pixmap for hidpi screens

2018-05-10 Thread L . E . Segovia
https://bugs.kde.org/show_bug.cgi?id=392282

L. E. Segovia  changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED

--- Comment #6 from L. E. Segovia  ---
I compiled 95b62e5041ccdb12c435275be2e73a171deb1fa1 on MacOS Sierra 10.12.6 and
can confirm both issues are fixed.

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

[krita] [Bug 393402] Krita 4 does not show image dimensions in MacOS

2018-05-10 Thread L . E . Segovia
https://bugs.kde.org/show_bug.cgi?id=393402

L. E. Segovia  changed:

   What|Removed |Added

Version|4.0.1   |4.0.2
Summary|Krita 4 does not show .kra  |Krita 4 does not show image
   |preview or image dimensions |dimensions in MacOS
   |in MacOS|

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

[akregator] [Bug 394114] New: Akregator 5.7.3 crash at opening an article

2018-05-10 Thread Pedro
https://bugs.kde.org/show_bug.cgi?id=394114

Bug ID: 394114
   Summary: Akregator 5.7.3 crash at opening an article
   Product: akregator
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: pedro.gong...@gmail.com
  Target Milestone: ---

Akregator crashes or hangs when opening some articles. I've noticed that it
only happens when the article has large images.
On my machine, the bug presents always, most times it crashes or just hangs,
but some times it freezes all the plasma desktop.
I'm using Kubuntu 18.04.

Backtrace:

Starting program: /usr/bin/akregator 
[Depuración de hilo usando libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Nuevo Thread 0x7fffc1fd0700 (LWP 14112)]
[Nuevo Thread 0x7fffb5773700 (LWP 14113)]
[Nuevo Thread 0x7fffb4a87700 (LWP 14114)]
[Nuevo Thread 0x7fffae894700 (LWP 14115)]
[Nuevo Thread 0x7fffae093700 (LWP 14120)]
[Nuevo Thread 0x7fffad892700 (LWP 14121)]
[Nuevo Thread 0x7fffad091700 (LWP 14122)]
[Nuevo Thread 0x7fffac890700 (LWP 14123)]
[Nuevo Thread 0x7fff9bdf1700 (LWP 14124)]
[Nuevo Thread 0x7fff9b5f0700 (LWP 14125)]
[Nuevo Thread 0x7fff9adef700 (LWP 14126)]
[Nuevo Thread 0x7fff9a5ee700 (LWP 14127)]
[Nuevo Thread 0x7fff99ded700 (LWP 14128)]
[Nuevo Thread 0x7fff995ec700 (LWP 14129)]
[Nuevo Thread 0x7fff98deb700 (LWP 14130)]
[Nuevo Thread 0x7fff77fff700 (LWP 14131)]
[Nuevo Thread 0x7fff777fe700 (LWP 14132)]
[Nuevo Thread 0x7fff76ffd700 (LWP 14133)]
[Nuevo Thread 0x7fff767fc700 (LWP 14134)]
[Nuevo Thread 0x7fff75ffb700 (LWP 14135)]
[Nuevo Thread 0x7fff757fa700 (LWP 14136)]
[Nuevo Thread 0x7fff74ff9700 (LWP 14137)]
[Nuevo Thread 0x7fff43fff700 (LWP 14138)]
[Nuevo Thread 0x7fff3ac07700 (LWP 14139)]
[Nuevo Thread 0x7fff398e2700 (LWP 14140)]
[Nuevo Thread 0x7fff33fff700 (LWP 14145)]
[Nuevo Thread 0x7fff32697700 (LWP 14156)]
[Thread 0x7fff32697700 (LWP 14156) terminado]
[Nuevo Thread 0x7fff32697700 (LWP 14192)]

Thread 21 "Chrome_InProcGp" received signal SIGSEGV, Segmentation fault.
[Cambiando a Thread 0x7fff75ffb700 (LWP 14135)]
pushbuf_kref (push=push@entry=0x55888a70, bo=0x0, flags=0) at
../../nouveau/pushbuf.c:173
173 ../../nouveau/pushbuf.c: No existe el archivo o el directorio.

Thread 29 (Thread 0x7fff32697700 (LWP 14192)):
#0  0x7fffee0caed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fff326967e0, expected=0, futex_word=0x7fffa0004594) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7fff32696880, mutex=0x7fffa0004540,
cond=0x7fffa0004568) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x7fffa0004568, mutex=0x7fffa0004540,
abstime=0x7fff32696880) at pthread_cond_wait.c:667
#3  0x7fffe46d3652 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7fffe46a9799 in base::PosixDynamicThreadPool::WaitForTask() () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7fffe46a9cfb in base::(anonymous
namespace)::WorkerThread::ThreadMain() () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7fffe46a25eb in base::(anonymous namespace)::ThreadFunc(void*) ()
from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7fffee0c46db in start_thread (arg=0x7fff32697700) at
pthread_create.c:463
#8  0x73da388f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 27 (Thread 0x7fff33fff700 (LWP 14145)):
#0  0x7fffee0ca9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x7fffe10d9fb8 ) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x7fffe10d9f68
, cond=0x7fffe10d9f90
) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x7fffe10d9f90 ,
mutex=0x7fffe10d9f68 ) at pthread_cond_wait.c:655
#3  0x7fffe0de35f4 in QTWTF::TCMalloc_PageHeap::scavengerThread
(this=0x7fffe10cbec0 ) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#4  0x7fffe0de3639 in QTWTF::TCMalloc_PageHeap::runScavengerThread
(context=) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#5  0x7fffee0c46db in start_thread (arg=0x7fff33fff700) at
pthread_create.c:463
#6  0x73da388f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 26 (Thread 0x7fff398e2700 (LWP 14140)):
#0  0x7fffee0ca9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55a32acc) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x55a32a78,
cond=0x55a32aa0) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x55a32aa0, mutex=0x55a32a78) at
pthread_cond_wait.c:655
#3  0x7fffe46a4c95 in
base::SequencedWorkerPool::Inner::ThreadLoop

[Spectacle] [Bug 394113] New: Rectangular Region Screenshot crashes the program

2018-05-10 Thread Chris
https://bugs.kde.org/show_bug.cgi?id=394113

Bug ID: 394113
   Summary: Rectangular Region Screenshot crashes the program
   Product: Spectacle
   Version: 18.04.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: cquick...@gmail.com
  Target Milestone: ---

I updated to the new Spectacle app, and tried to take a rectangular region
screenshot.  After clicking "Take a new screenshot" the program closes.  It
will instead take a screenshot of the entire screen even though it crashes.  

Version 18.04.0-1
Linux, KDE Plasma.

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

[dolphin] [Bug 393412] Dolphin fails to build with disabled support for Baloo

2018-05-10 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=393412

Christoph Feck  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[dolphin] [Bug 394112] New: Dolphin Crashes when moving from a Lunix (ext3, ext4) file system more than 1 file to an NTFS partition

2018-05-10 Thread Maxim Aliev
https://bugs.kde.org/show_bug.cgi?id=394112

Bug ID: 394112
   Summary: Dolphin Crashes when moving from a Lunix (ext3, ext4)
file system more than 1 file to an NTFS partition
   Product: dolphin
   Version: 17.12.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: sepkha...@gmail.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

Application: dolphin (17.12.3)

Qt Version: 5.9.5
Frameworks Version: 5.44.0
Operating System: Linux 4.15.0-20-generic x86_64
Distribution: Ubuntu 18.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I tried to move a number of files. After moving one file, a window pops up
saying permissions were denied. Pressing any button in that pop-up window
crashes Dolphin window with NTFS partition open.

The crash can be reproduced every time.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3457dd56c0 (LWP 11684))]

Thread 5 (Thread 0x7f3427fff700 (LWP 17070)):
#0  0x7f344c72c9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x56072c989500) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x56072c9894b0,
cond=0x56072c9894d8) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x56072c9894d8, mutex=0x56072c9894b0) at
pthread_cond_wait.c:655
#3  0x7f345163d59b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f3451635c0b in QSemaphore::acquire(int) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f34275fa80c in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/texttospeech/libqttexttospeech_flite.so
#6  0x7f345163c16d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f344c7266db in start_thread (arg=0x7f3427fff700) at
pthread_create.c:463
#8  0x7f345766c88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7f342eb41700 (LWP 11693)):
#0  0x7f345765fbf9 in __GI___poll (fds=0x7f34280049b0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f344a5b5439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f344a5b554c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f345187390b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f34518189ea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f345163722a in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f345163c16d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f344c7266db in start_thread (arg=0x7f342eb41700) at
pthread_create.c:463
#8  0x7f345766c88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f343a4d7700 (LWP 11686)):
#0  0x7f345765fbf9 in __GI___poll (fds=0x7f343401a9c0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f344a5b5439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f344a5b554c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f345187390b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f34518189ea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f345163722a in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f3451cf0d45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f345163c16d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f344c7266db in start_thread (arg=0x7f343a4d7700) at
pthread_create.c:463
#9  0x7f345766c88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f3440ca0700 (LWP 11685)):
#0  0x7f345765fbf9 in __GI___poll (fds=0x7f3440c9fca8, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f3449ef6747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f3449ef836a in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f3443a4d2a9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f345163c16d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f344c7266db in start_thread (arg=0x7f3440ca0700) at
pthread_create.c:463
#6  0x7f345766c88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f3457dd56c0 (LWP 11684)):
[KCrash Handler]
#6  0x7f345181dd41 in QCoreApplication::postEvent(QObject*, QEvent*, int)
() 

[krita] [Bug 394046] No Russian language and no full screen mode

2018-05-10 Thread Max
https://bugs.kde.org/show_bug.cgi?id=394046

--- Comment #5 from Max  ---


It's a very strange, but now I have been a russian interface. My computer
changed language, but language changed to "catana" for this result.

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

[krita] [Bug 394046] No Russian language and no full screen mode

2018-05-10 Thread Max
https://bugs.kde.org/show_bug.cgi?id=394046

Max  changed:

   What|Removed |Added

Version|4.0.1   |4.0.2

--- Comment #4 from Max  ---
It's a very strange, but now I have been a russian interface. My computer chang

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

[ktorrent] [Bug 394111] KTorrent crashes why I try to quit it

2018-05-10 Thread Ezra
https://bugs.kde.org/show_bug.cgi?id=394111

--- Comment #1 from Ezra  ---
Ok, I'm trying now to reproduce it again and I didn't succeed,it should be
changed to reproduced only sometimes.

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

[ktorrent] [Bug 394111] New: KTorrent crashes why I try to quit it

2018-05-10 Thread Ezra
https://bugs.kde.org/show_bug.cgi?id=394111

Bug ID: 394111
   Summary: KTorrent crashes why I try to quit it
   Product: ktorrent
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: joris.guis...@gmail.com
  Reporter: ezra...@gmail.com
  Target Milestone: ---

Application: ktorrent (5.1.0)

Qt Version: 5.10.1
Frameworks Version: 5.45.0
Operating System: Linux 4.16.7-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:
I was closing the application via the File->Quit.
It always happens when I close this way or via Ctrl+Q, it doesn't ask me if I
wanna quit but just crashes. When I'm closing it via the notifications, it asks
me as (I guess) it should and doesn't cause any problems.

The crash can be reproduced every time.

-- Backtrace:
Application: KTorrent (ktorrent), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1f68ce5380 (LWP 846))]

Thread 4 (Thread 0x7f1f077fe700 (LWP 1055)):
#0  0x7f1f62dc0ea9 in poll () at /usr/lib/libc.so.6
#1  0x7f1f55279310 in  () at /usr/lib/libresolv.so.2
#2  0x7f1f55276d9d in __res_context_query () at /usr/lib/libresolv.so.2
#3  0x7f1f2e8f30d7 in _nss_dns_gethostbyaddr2_r () at
/usr/lib/libnss_dns.so.2
#4  0x7f1f2e8f33c3 in _nss_dns_gethostbyaddr_r () at
/usr/lib/libnss_dns.so.2
#5  0x7f1f62ddcee2 in gethostbyaddr_r@@GLIBC_2.2.5 () at /usr/lib/libc.so.6
#6  0x7f1f62de53a7 in gni_host_inet_name.isra () at /usr/lib/libc.so.6
#7  0x7f1f62de5ab9 in getnameinfo () at /usr/lib/libc.so.6
#8  0x7f1f68506308 in  () at /usr/lib/libKF5Torrent.so.6
#9  0x7f1f68506a41 in  () at /usr/lib/libKF5Torrent.so.6
#10 0x7f1f63a74abd in  () at /usr/lib/libQt5Core.so.5
#11 0x7f1f5e69f075 in start_thread () at /usr/lib/libpthread.so.0
#12 0x7f1f62dcb53f in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f1f49f4b700 (LWP 855)):
#0  0x7f1f5bf66010 in g_ptr_array_set_size () at /usr/lib/libglib-2.0.so.0
#1  0x7f1f5bf9393a in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7f1f5bf9444e in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f1f5bf9463e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f1f63cbe254 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f1f63c6031b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f1f63a6f71e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f1f63a74abd in  () at /usr/lib/libQt5Core.so.5
#8  0x7f1f5e69f075 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f1f62dcb53f in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f1f4b95d700 (LWP 850)):
#0  0x7f1f62dc0ea9 in poll () at /usr/lib/libc.so.6
#1  0x7f1f5bf94523 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f1f5bf9463e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f1f63cbe254 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f1f63c6031b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f1f63a6f71e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f1f650fc416 in  () at /usr/lib/libQt5DBus.so.5
#7  0x7f1f63a74abd in  () at /usr/lib/libQt5Core.so.5
#8  0x7f1f5e69f075 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f1f62dcb53f in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f1f68ce5380 (LWP 846)):
[KCrash Handler]
#6  0x7f1f63ca4b20 in QVariant::QVariant(QString const&) () at
/usr/lib/libQt5Core.so.5
#7  0x56356b98f10d in  ()
#8  0x56356b991a7d in  ()
#9  0x7f1f64c5f6a1 in
QStyledItemDelegate::initStyleOption(QStyleOptionViewItem*, QModelIndex const&)
const () at /usr/lib/libQt5Widgets.so.5
#10 0x7f1f64c5eb77 in QStyledItemDelegate::sizeHint(QStyleOptionViewItem
const&, QModelIndex const&) const () at /usr/lib/libQt5Widgets.so.5
#11 0x56356b998145 in  ()
#12 0x7f1f64ca3b56 in QTreeView::indexRowSizeHint(QModelIndex const&) const
() at /usr/lib/libQt5Widgets.so.5
#13 0x7f1f64ca450f in QTreeViewPrivate::layout(int, bool, bool) () at
/usr/lib/libQt5Widgets.so.5
#14 0x7f1f64cac710 in QTreeView::doItemsLayout() () at
/usr/lib/libQt5Widgets.so.5
#15 0x7f1f64ca6bd6 in QTreeViewPrivate::updateScrollBars() () at
/usr/lib/libQt5Widgets.so.5
#16 0x7f1f64cae2fe in QTreeView::updateGeometries() () at
/usr/lib/libQt5Widgets.so.5
#17 0x7f1f64c3b859 in  () at /usr/lib/libQt5Widgets.so.5
#18 0x7f1f63c92606 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/libQt5Core.so.5
#19 0x7f1f64c51dab in QHeaderView::viewportEvent(QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#20 0x7f1f63c619a

[drkonqi] [Bug 391187] Duplicate search needs to search for both 'crash' and 'normal' severity

2018-05-10 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=391187

--- Comment #13 from Christoph Feck  ---
Nate, any opinion on comment #4?

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

[kde] [Bug 394108] Testing reporting bug severity to wishlist

2018-05-10 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=394108

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #2 from Christoph Feck  ---


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

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

[drkonqi] [Bug 391187] Duplicate search needs to search for both 'crash' and 'normal' severity

2018-05-10 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=391187

Christoph Feck  changed:

   What|Removed |Added

 CC||reptilli...@live.com

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

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

[krita] [Bug 394110] Unable to render animation

2018-05-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=394110

--- Comment #1 from mastertobygam...@gmail.com ---
Created attachment 112571
  --> https://bugs.kde.org/attachment.cgi?id=112571&action=edit
Log created when rendering with 4.0 version of FFmpeg

The other file made by the other version of FFmpeg

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

[krita] [Bug 394110] New: Unable to render animation

2018-05-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=394110

Bug ID: 394110
   Summary: Unable to render animation
   Product: krita
   Version: 4.0.2
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: mastertobygam...@gmail.com
  Target Milestone: ---

Created attachment 112570
  --> https://bugs.kde.org/attachment.cgi?id=112570&action=edit
Log created when rendering

On Windows 8.1, I am trying to export 500 frames at a time out of about 9500
frames. The first 500 frames went fine when exporting as a ".ogg" file. The
next set of frames (501 through 1000) and the next (1001 through 1500) did not
render properly. It gave me the error "Could not render animation: FFmpeg
failed to convert the image sequence" error. I have used the "20180508-293a6e8"
nightly git build of FFmpeg (log linked) and the 4.0 release build. I did find
the log in the folder where I set the files to go when rendering. My animation
is in 1080p (1920 x 1080) with a bit depth of 8 and the lowest layer is white
(dunno if that counts as transparent or not). The entire animation is about
9500 frames long, but I only tried to render 500 of them, specifically frames
1001 through 1500.

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

[krita] [Bug 392190] 4.0 + flatpak: Crash when painting

2018-05-10 Thread Peter Eszlari
https://bugs.kde.org/show_bug.cgi?id=392190

--- Comment #11 from Peter Eszlari  ---
I used git bisect to find the faulty commit:

28f16e0f83741e518c0916598cb2a3032b377a07 is the first bad commit
commit 28f16e0f83741e518c0916598cb2a3032b377a07
Author: Allen Marshall 
Date:   Fri Jun 2 15:54:54 2017 -0500

Performance improvement: Airbrushing no longer reads properties from a
KisPropertiesConfiguration during painting.

:04 04 c03a21c961299bdf2406c787dc99713493fee834
4085f375a485d4ebe43e4dc34d2737e506904d91 M  plugins

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

[digikam] [Bug 393925] UpdateSchemaFromV7ToV9 fails due to duplicate key in album_2

2018-05-10 Thread Theo van Rijn
https://bugs.kde.org/show_bug.cgi?id=393925

--- Comment #3 from Theo van Rijn  ---
The migration tool worked like a charm, the new schema does not have any of the
superfluous indexes any more. The DB size shrank from almost 2GB to just over
200MB. Thanks Maik! For both solutions.

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

[plasmashell] [Bug 393986] plasmashell PID: 4969 Signal: Segmentation fault

2018-05-10 Thread Nick
https://bugs.kde.org/show_bug.cgi?id=393986

Nick  changed:

   What|Removed |Added

 CC||nick.craig@gmail.com

--- Comment #2 from Nick  ---
I can't reproduce it, any letters in particular that you're typing ? What theme
are you using ? Which launcher are you using, dashboard, launcher (the
standard) or menu ?

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

[kmail2] [Bug 392996] links and attachments don't open with qtwebengine 5.11 beta 3

2018-05-10 Thread Antonio Rojas
https://bugs.kde.org/show_bug.cgi?id=392996

Antonio Rojas  changed:

   What|Removed |Added

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

--- Comment #1 from Antonio Rojas  ---
Fixed in 18.04.1

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

[krita] [Bug 394109] Copy/paste followed by use of transformation tool leads to crash

2018-05-10 Thread Boudewijn Rempt
https://bugs.kde.org/show_bug.cgi?id=394109

Boudewijn Rempt  changed:

   What|Removed |Added

 OS|Linux   |MS Windows
   Platform|Windows CE  |MS Windows
 CC||b...@valdyas.org

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

[krita] [Bug 394109] New: Copy/paste followed by use of transformation tool leads to crash

2018-05-10 Thread Alvin Shi
https://bugs.kde.org/show_bug.cgi?id=394109

Bug ID: 394109
   Summary: Copy/paste followed by use of transformation tool
leads to crash
   Product: krita
   Version: 4.0.2
  Platform: Windows CE
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tools/Move
  Assignee: krita-bugs-n...@kde.org
  Reporter: alvin@gmail.com
  Target Milestone: ---

I am using a windows surface pro, running windows 10. In drawing, I repeatedly
attempted to select a particular section of drawing, then copy/pasting a copy
of that section to another part on the canvas. On every attempt, the
copy/pasting was successful, but trying to move the copy around with the
transformation tool leads to an instantaneous crash.

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

[kio-extras] [Bug 381437] FTP "Can't get into folder" after succesfull login

2018-05-10 Thread Rafael
https://bugs.kde.org/show_bug.cgi?id=381437

Rafael  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED
 CC||rafael.linux.u...@gmail.com

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

[krita] [Bug 393851] If Krita loads with the Eraser as default brush, it paints to black when used

2018-05-10 Thread Scott Petrovic
https://bugs.kde.org/show_bug.cgi?id=393851

--- Comment #2 from Scott Petrovic  ---
I started looking at this, but it appears it might be a bit deeper than I
thought. The code that loads the preset when the application starts is here

KisViewManager::setCurrentView(KisView *view):409

When this function grabs the last used preset, it grabs the correct name. The
code seems to think the composite mode is "normal" and erase mode is set to
false which isn't what is saved in the preset. There must be something that
hasn't been loaded correctly when this gets called.

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

[krita] [Bug 391273] Crashed when dragging several keyframes around

2018-05-10 Thread Scott Petrovic
https://bugs.kde.org/show_bug.cgi?id=391273

Scott Petrovic  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #4 from Scott Petrovic  ---
I am pretty sure this is fixed as part of this commit by Dmitry... marking
resolved unless someone can prove me wrong.


Author: Dmitry Kazakov 
Author date:4 days ago (5/6/2018 6:47:45 AM)
Commit date:4 days ago (5/6/2018 7:02:33 AM)
Commit hash:b6c39175b43c5f7a2d6613019fab4bbcd31f3302

Fix copy-paste frames operation when the timeline layout changes

Now "application/x-krita-frame" mime type also saves the UUID of the
source node, so pasting the frames after the row layout changed is still
valid.

The patch also implements a new version of
KisAnimationUtils::createMoveKeyframesCommand which is safe to use
when the frame moves have cyclic dependencies (one frame is going to
overwrite another frame during the move). Theoretically, we don't need
to use sortPointsForSafeMove() anymore. But it should be tested.

Contained in branches: master
Contained in no tag

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

[dolphin] [Bug 392339] Show filesystem type in information panel

2018-05-10 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=392339

Nate Graham  changed:

   What|Removed |Added

Summary|auto-detect the filesystem  |Show filesystem type in
   |in panel information in |information panel
   |Dolphin |
   Keywords||usability

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

[kio] [Bug 238690] video thumbnail not displayed on directory icon on kubuntu x64 karmic and lucid

2018-05-10 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=238690

Nate Graham  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #17 from Nate Graham  ---
Hmm, I see video previews for all my videos without having that setting set in
kdeglobals. Since the original issue is resolved, let's track the remaining
issue in a new bug. Thanks all!

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

[okular] [Bug 377688] No output to print for PDF since update to 1.0.3

2018-05-10 Thread Michael Weghorn
https://bugs.kde.org/show_bug.cgi?id=377688

Michael Weghorn  changed:

   What|Removed |Added

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

--- Comment #15 from Michael Weghorn  ---
(In reply to Michael Weghorn from comment #14)
> I just tried to reproduce with one of the attached documents and did not
> encounter the problem.
> 
> Is the problem still present for you?
> Is it specific to a specific printer? (As a test, you can try for example
> whether the problem also occurs with the "CUPS-PDF" printer that prints to a
> file if you just have one physical device.)
> 
> If so, could you please attach the PPD file of the printer on which the
> problem occurs for you? (It should be located at
> /etc/cups/ppd/.ppd .)

I'm setting the status to NEEDINFO, since the question has not been answered
yet and that additional information is required to analyse the problem further.

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

[kdelibs] [Bug 313796] printer will not print a landscape page

2018-05-10 Thread Michael Weghorn
https://bugs.kde.org/show_bug.cgi?id=313796

Michael Weghorn  changed:

   What|Removed |Added

 CC||m.wegh...@posteo.de
 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #2 from Michael Weghorn  ---
(In reply to Mike from comment #0)
> had trouble getting printer to work on ubuntu got it to work but will not
> print a landscape document
> 
> Reproducible: Always

Hi Mike, are you still having issues to print landscape with current versions
of KDE and Qt?

If so, could you please add a step-by-step description of one scenario that
fails for you? (It seems to be working fine for me.)

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

[kio-extras] [Bug 392803] Dolphin Samba Network Discovery Not Seeing Samba Drives 18.04 Kubuntu

2018-05-10 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=392803

Nate Graham  changed:

   What|Removed |Added

URL||https://bugzilla.samba.org/
   ||show_bug.cgi?id=12876

--- Comment #6 from Nate Graham  ---
Digging a bit, smbtree intelligently downgrades itself to using the old SMB1
version for the purposes of browsing.[1] Connections are actually made using
the newer, more secure version. libsamba (the actual library that we use) does
not have the same behavior.

It's a decent enough temporary workaround, except of course for the fact that
more and more network resources don't use SMB1, so smbtree won't find them.
Going forward, what's needed is support foe one of the modern service discovery
protocols. The referenced bug report is the one to follow, as that's there the
Samba developers are trying to figure how what to do here.

[1] https://bugzilla.samba.org/show_bug.cgi?id=12876#c2

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

[kdelibs] [Bug 320625] printouts are nearly black

2018-05-10 Thread Michael Weghorn
https://bugs.kde.org/show_bug.cgi?id=320625

Michael Weghorn  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO
 CC||m.wegh...@posteo.de

--- Comment #10 from Michael Weghorn  ---
(In reply to Axel Krebs from comment #0)
> When printing in digiKam, black-and-white print are nearly black.
> 
> [...]

Hi Axel, are you still experiencing this issue with current versions of digiKam
and Qt?

If so, can you please attach your printer's PPD file (which should be located
at '/etc/cups/ppd/.ppd') and a sample file with which you can
reproduce this when printing from digiKam?

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

[kdelibs] [Bug 333375] Print does not print landscape outside LibreOffice, Problem: PDF/PS driver?

2018-05-10 Thread Michael Weghorn
https://bugs.kde.org/show_bug.cgi?id=75

Michael Weghorn  changed:

   What|Removed |Added

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

--- Comment #1 from Michael Weghorn  ---
(In reply to Hubert Kaschulke from comment #0)
> Suse Linux 13.1 KDE (on different computers)
>[...]
> Begins to print the "thought landscape file" in the second third of the page
> and throws away the part not fitting on the physical page 1

Hi, is this still an issue with current versions of KDE and KDE applications,
e.g. Kate?
I quickly tested and it seems to be be working just fine for me.

(Firefox uses the GTK print dialog and is thus out of the control of KDE
software.)

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

[kdelibs] [Bug 180364] "umlauts" are not printed

2018-05-10 Thread Christopher Bräuer
https://bugs.kde.org/show_bug.cgi?id=180364

--- Comment #8 from Christopher Bräuer  ---
Yes, thank you!

Michael Weghorn  schrieb am Do., 10. Mai 2018,
22:53:

> https://bugs.kde.org/show_bug.cgi?id=180364
>
> Michael Weghorn  changed:
>
>What|Removed |Added
>
> 
>  Resolution|WAITINGFORINFO  |WORKSFORME
>  Status|NEEDSINFO   |RESOLVED
>
> --- Comment #7 from Michael Weghorn  ---
> (In reply to Christopher Bräuer from comment #6)
> > Created attachment 112568 [details]
> > attachment-10492-0.html
> >
> > Hey,
> > I think, this big can be closed. I didn't see the problem anymore.
>
> Thanks for your reply! I'm therefore closing this.
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[kdelibs] [Bug 180364] "umlauts" are not printed

2018-05-10 Thread Michael Weghorn
https://bugs.kde.org/show_bug.cgi?id=180364

Michael Weghorn  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #7 from Michael Weghorn  ---
(In reply to Christopher Bräuer from comment #6)
> Created attachment 112568 [details]
> attachment-10492-0.html
> 
> Hey,
> I think, this big can be closed. I didn't see the problem anymore.

Thanks for your reply! I'm therefore closing this.

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

[kmail2] [Bug 394099] Weird black box appearing alongside the split between message list and preview

2018-05-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=394099

andreas.sturmlech...@gmail.com changed:

   What|Removed |Added

 CC||andreas.sturmlechner@gmail.
   ||com

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

[kdelibs] [Bug 180364] "umlauts" are not printed

2018-05-10 Thread Christopher Bräuer
https://bugs.kde.org/show_bug.cgi?id=180364

--- Comment #6 from Christopher Bräuer  ---
Hey,
I think, this big can be closed. I didn't see the problem anymore.


Michael Weghorn  schrieb am Do., 10. Mai 2018,
21:33:

> https://bugs.kde.org/show_bug.cgi?id=180364
>
> Michael Weghorn  changed:
>
>What|Removed |Added
>
> 
>  Resolution|--- |WAITINGFORINFO
>  Status|UNCONFIRMED |NEEDSINFO
>
> --- Comment #5 from Michael Weghorn  ---
> (In reply to Michael Weghorn from comment #4)
> > This bug is quite old and I could not find any "page label" field in the
> > print dialog shown in current Okular versions.
> >
> > @Christopher Bräuer:
> > Is this still relevant with current Okular versions? If so, could you
> please
> > specify where the "page label" field can be found?
>
> I'm setting the bug status to NEEDSINFO for now, since the question has not
> been answered yet.
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[kdelibs] [Bug 199357] Okular not printing to configured printer

2018-05-10 Thread Michael Weghorn
https://bugs.kde.org/show_bug.cgi?id=199357

Michael Weghorn  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #9 from Michael Weghorn  ---
(In reply to John Wheaton from comment #8)
> This is no longer an issue for me due to a complete OS change.  Thanks! 
> Apologies for not replying to the JAN email.  I did not see it.
> 
> I'd update the status, but I'm not sure what it would be set to.
> 
> Cheers!

No problem, thanks for your quick reply now! I think we can close this bug
report as "WORKSFORME" in this case, which I'm doing hereby.

Should you switch your OS again in the future, please feel free to file a new
bug report in case you're still having any issues with this.

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

[kdelibs] [Bug 199357] Okular not printing to configured printer

2018-05-10 Thread John Wheaton
https://bugs.kde.org/show_bug.cgi?id=199357

--- Comment #8 from John Wheaton  ---
This is no longer an issue for me due to a complete OS change.  Thanks! 
Apologies for not replying to the JAN email.  I did not see it.

I'd update the status, but I'm not sure what it would be set to.

Cheers!

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

[kdelibs] [Bug 179955] KDE print dialog loads very slowly

2018-05-10 Thread Michael Weghorn
https://bugs.kde.org/show_bug.cgi?id=179955

Michael Weghorn  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UPSTREAM
 CC||m.wegh...@posteo.de

--- Comment #21 from Michael Weghorn  ---
Note that there was the idea to add a handling upstream in the Qt print dialog
to handle the case where attempting to retrieve the PPD from a remote CUPS
server takes a long time to not block the UI, s. e.g. the change at [1] , in
particular the comments on patch set 4 [2].

The patch set was dropped in the end though, since the underlying issue is a
CUPS one and the behaviour has changed in the most recent CUPS version 2.2.7,
s. [2] and also the CUPS issue [3] that describes that the new behaviour is
intended.

The problem should no longer occur with CUPS version 2.2.7 or later or with a
modified setup as suggested by CUPS developer Michael Sweet in [3].

I'm therefore closing this bug report as RESOLVED UPSTREAM.

[1] https://codereview.qt-project.org/#/c/225203/
[2] https://codereview.qt-project.org/#/c/225203/4//ALL
[3] https://github.com/apple/cups/issues/5293

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

[kde] [Bug 394108] Testing reporting bug severity to wishlist

2018-05-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=394108

--- Comment #1 from reptilli...@live.com ---
Failed, it ends up on NOR normal.

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

[kde] [Bug 394108] New: Testing reporting bug severity to wishlist

2018-05-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=394108

Bug ID: 394108
   Summary: Testing reporting bug severity to wishlist
   Product: kde
   Version: unspecified
  Platform: Other
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: reptilli...@live.com
  Target Milestone: ---

There was some bug reports where I was sure that I have set severity to
wishlist to krita, and it failed. I have set severity to wishlist upon this bug
report. Please verify it works.

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

[kdelibs] [Bug 208973] ppd description file constrains

2018-05-10 Thread Michael Weghorn
https://bugs.kde.org/show_bug.cgi?id=208973

Michael Weghorn  changed:

   What|Removed |Added

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

--- Comment #2 from Michael Weghorn  ---
Proper handling of PPD constraints has been implemented in Qt upstream in the
meanwhile, therefore I am closing this bug report.

Related upstream Qt changes that implement this:
https://codereview.qt-project.org/#/c/215221/
https://codereview.qt-project.org/#/c/215441/
https://codereview.qt-project.org/#/c/222854/

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

[kdelibs] [Bug 366401] Printing to A3 doesn't work always printed as A4

2018-05-10 Thread Michael Weghorn
https://bugs.kde.org/show_bug.cgi?id=366401

Michael Weghorn  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO
 CC||m.wegh...@posteo.de

--- Comment #1 from Michael Weghorn  ---
@Thaodan: Is this still a problem? If so, can you please attach a sample
document, e.g. a PDF file for Okular?

Also: What version of the Qt library is being used?

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

[krita] [Bug 394103] Reference Images Tool in 4.02 Pre-Alpha seem to be blurry

2018-05-10 Thread Boudewijn Rempt
https://bugs.kde.org/show_bug.cgi?id=394103

Boudewijn Rempt  changed:

   What|Removed |Added

   Severity|normal  |wishlist
 CC||b...@valdyas.org
Version|4.0.2   |git master

--- Comment #1 from Boudewijn Rempt  ---
Setting to wish, since you're asking for a new feature.

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

[kdelibs] [Bug 204531] UI inconsistency in target file selection for print-to-file printers

2018-05-10 Thread Michael Weghorn
https://bugs.kde.org/show_bug.cgi?id=204531

Michael Weghorn  changed:

   What|Removed |Added

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

--- Comment #2 from Michael Weghorn  ---
(In reply to Michael Weghorn from comment #1)
> This bug report is quite old.
> 
> @Stefan Majewsky:
> Does this still apply for current versions of KDE applications (and
> underlying Qt)?
> If so, could you add an example on where the file selection interface is as
> desired/expected?

I'm setting the bug status to NEEDSINFO for now, since the question has not
been answered yet.

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

[kdelibs] [Bug 180364] "umlauts" are not printed

2018-05-10 Thread Michael Weghorn
https://bugs.kde.org/show_bug.cgi?id=180364

Michael Weghorn  changed:

   What|Removed |Added

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

--- Comment #5 from Michael Weghorn  ---
(In reply to Michael Weghorn from comment #4)
> This bug is quite old and I could not find any "page label" field in the
> print dialog shown in current Okular versions.
> 
> @Christopher Bräuer:
> Is this still relevant with current Okular versions? If so, could you please
> specify where the "page label" field can be found?

I'm setting the bug status to NEEDSINFO for now, since the question has not
been answered yet.

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

[kdelibs] [Bug 308768] Changing printer to "Print To File" should set printout to color

2018-05-10 Thread Michael Weghorn
https://bugs.kde.org/show_bug.cgi?id=308768

Michael Weghorn  changed:

   What|Removed |Added

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

--- Comment #2 from Michael Weghorn  ---
(In reply to Michael Weghorn from comment #1)
> @Kai Uwe: Is this still a problem?
> I think that this should be solved at the latest with the following change
> just integrated into Qt's "dev" branch:
> https://codereview.qt-project.org/#/c/215069

As mentioned, this should be fixed upstream now, so I'm closing this bug
report. Please reopen in case you're still experiencing any issues with Qt
versions >= 5.11.

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

[kdelibs] [Bug 219990] Print dialog: Clicking on page counters should select Pages checker

2018-05-10 Thread Michael Weghorn
https://bugs.kde.org/show_bug.cgi?id=219990

Michael Weghorn  changed:

   What|Removed |Added

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

--- Comment #2 from Michael Weghorn  ---
(In reply to Michael Weghorn from comment #1)
> This bug report is quite old.
> 
> @Vsevolod Krishchenko: Is this still valid for current versions of KDE?
> If so: Could you possibly describe in a more detailed way which "page number
> counters" exactly you mean and what exactly the expected behaviour is?
> A step-by-step description of how to reproduce might help here.

I'm setting the bug status to NEEDSINFO for now, since the question has not
been answered yet.

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

[cantor] [Bug 375467] Cantor hangs at "Initializing Session" when choosing Sage backend (Sage version 7.6)

2018-05-10 Thread Nikita Sirgienko
https://bugs.kde.org/show_bug.cgi?id=375467

Nikita Sirgienko  changed:

   What|Removed |Added

 CC||warqu...@gmail.com

--- Comment #10 from Nikita Sirgienko  ---
I suspect, that this is still a problem with multiline input with ipython. I
have tested sage backend with changed process ('maxima', 'octave-cli',
'mathjs', 'python', 'nodejs') and all of them read multiline input from backend
correctly and only ipython and sage read only first line of the multiline
input.

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

[kdelibs] [Bug 288086] No 'Pages' or 'Jobs' tabs in printing dialog

2018-05-10 Thread Michael Weghorn
https://bugs.kde.org/show_bug.cgi?id=288086

Michael Weghorn  changed:

   What|Removed |Added

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

--- Comment #7 from Michael Weghorn  ---
(In reply to Michael Weghorn from comment #6)
> @qdiesel.mipt
> 
> This bug is quite old. Do you still encounter the described problem with
> current versions of Okular?

I'm setting the bug status to NEEDSINFO for now, since the question has not
been answered yet.

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

[kdelibs] [Bug 199472] Default Printer setting is not honoured by KDE apps

2018-05-10 Thread Michael Weghorn
https://bugs.kde.org/show_bug.cgi?id=199472

Michael Weghorn  changed:

   What|Removed |Added

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

--- Comment #6 from Michael Weghorn  ---
(In reply to Michael Weghorn from comment #5)
> This bug report is quite old and I cannot reproduce.
> 
> @Hrishikesh Mehendale (हृषीकेश मेहेंदळे):
> Do you still encounter the described problem with current versions of KDE
> applications?

I'm setting the bug status to NEEDSINFO for now, since the question has not
been answered yet and I am unable to reproduce.

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

[kdelibs] [Bug 199357] Okular not printing to configured printer

2018-05-10 Thread Michael Weghorn
https://bugs.kde.org/show_bug.cgi?id=199357

Michael Weghorn  changed:

   What|Removed |Added

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

--- Comment #7 from Michael Weghorn  ---
(In reply to Michael Weghorn from comment #6)
> This bug report is quite old.
> 
> @John Wheaton:
> Do you still encounter the described problem with current versions of Okular?

I'm setting the bug status to NEEDSINFO for now, since the question has not
been answered yet.

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

[kdelibs] [Bug 201380] Printing cuts a part of the content

2018-05-10 Thread Michael Weghorn
https://bugs.kde.org/show_bug.cgi?id=201380

Michael Weghorn  changed:

   What|Removed |Added

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

--- Comment #2 from Michael Weghorn  ---
(In reply to Michael Weghorn from comment #1)
> This bug report is quite old.
> 
> @Rosetzky Cedric:
> Is the problem still present in today's KDE applications?
> If so, could you please give more details on how to reproduce the problem
> (in particular, what application you are using for printing and which
> document is being used...)?

I'm setting the bug status to NEEDSINFO for now, since the question has not
been answered yet.

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

[kdelibs] [Bug 241873] Problem with cups

2018-05-10 Thread Michael Weghorn
https://bugs.kde.org/show_bug.cgi?id=241873

Michael Weghorn  changed:

   What|Removed |Added

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

--- Comment #4 from Michael Weghorn  ---
(In reply to Michael Weghorn from comment #3)
> @dan: This bug report is quite old. Is this still a problem for you?

I'm setting the bug status to NEEDSINFO for now, since the question has not
been answered yet.

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

[kdevelop] [Bug 394107] New: UI hangs when scanning include folders

2018-05-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=394107

Bug ID: 394107
   Summary: UI hangs when scanning include folders
   Product: kdevelop
   Version: 5.2.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: dpiskyu...@yahoo.com
  Target Milestone: ---

Periodically, but way too often, the whole UI freezes. After gdb and strace I
have narrowed it down to KDevelop scanning the folders from
.kdev_include_paths. After 'tuning' the .kdev_include_paths file the freezes
are much shorter but it is still fairly unusable.

Please move such tasks to a background thread and do not block the main UI. In
addition some control over how often such rescans are done can be useful.

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

[kdelibs] [Bug 257961] Add printout size to printer dialog

2018-05-10 Thread Michael Weghorn
https://bugs.kde.org/show_bug.cgi?id=257961

Michael Weghorn  changed:

   What|Removed |Added

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

--- Comment #2 from Michael Weghorn  ---
(In reply to Michael Weghorn from comment #1)
> @Kai Uwe: Is this still a problem nowadays?
> In general, the Qt print dialog used by KolourPaint does offer the
> possibility of choosing paper sizes ("Properties" -> "Page").
> It is also possible to use custom page sizes there, which has only recently
> been fixed in Qt by Albert, s. https://codereview.qt-project.org/#/c/215054/
> .
> 
> Is that already what you need or do you mean that a more advanced handling
> of any kind is needed?

I'm setting the bug status to NEEDSINFO for now, since the question has not
been answered yet.

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

[kdelibs] [Bug 186458] Please add free-style page range as a third option in Print dialog

2018-05-10 Thread Michael Weghorn
https://bugs.kde.org/show_bug.cgi?id=186458

Michael Weghorn  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|CONFIRMED   |RESOLVED

--- Comment #10 from Michael Weghorn  ---
(In reply to Michael Weghorn from comment #9)
> Note that there is the following upstream Qt change recently integrated into
> Qt's development branch which adds the requested feature:
> https://codereview.qt-project.org/#/c/215390/

Since this has been implemented in Qt, I'm closing this bug report now.

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

[kdelibs] [Bug 182794] Options displayed on the print dialog don't "agree" with options under properties > advanced

2018-05-10 Thread Michael Weghorn
https://bugs.kde.org/show_bug.cgi?id=182794

Michael Weghorn  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Michael Weghorn  ---
(In reply to Michael Weghorn from comment #1)
> While the original bug report is for KDE 4 (and thus Qt 4) and the
> "Advanced" tab has initially been removed from the Qt 5 print dialog, it is
> now back (in the current development branch). The bug mentioned here has
> been fixed there as well, see the following two changes:
> 
> https://codereview.qt-project.org/#/c/215131/
> https://codereview.qt-project.org/#/c/215069

Since this has been fixed in Qt, I'm closing this bug report now.

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

[kdelibs] [Bug 183632] Printing to printer doesn't work with LPR (except in Okular)

2018-05-10 Thread Michael Weghorn
https://bugs.kde.org/show_bug.cgi?id=183632

Michael Weghorn  changed:

   What|Removed |Added

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

--- Comment #6 from Michael Weghorn  ---
(In reply to Michael Weghorn from comment #5)
> This bug report is quite old.
> 
> @James Richard Tyrer: Is this still a problem nowadays?

I'm changing the bug status to NEEDSINFO for now, since the questions has not
been answered yet.

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

[kdeplasma-addons] [Bug 361968] weather widget settings: location search field default action should be "search" (instead of closing the dialog by OK)

2018-05-10 Thread Friedrich W . H . Kossebau
https://bugs.kde.org/show_bug.cgi?id=361968

Friedrich W. H. Kossebau  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
   Version Fixed In||5.13.0
  Latest Commit||https://commits.kde.org/kde
   ||plasma-addons/1634d5ed82b43
   ||d9b86efd2e0d69fa137865292ba
 Resolution|--- |FIXED

--- Comment #8 from Friedrich W. H. Kossebau  ---
Git commit 1634d5ed82b43d9b86efd2e0d69fa137865292ba by Friedrich W. H.
Kossebau.
Committed on 10/05/2018 at 19:11.
Pushed by kossebau into branch 'master'.

[weather applet] Config: Use separate dialog for searching a new station

Prepares for having a set of stations which then could be switched
between to select the currently shown one

Having a separate dialog with completely own code also allows to
handle the Enter key as shortcut for triggering the search button.
FIXED-IN: 5.13.0

M  +37   -131 
applets/weather/package/contents/ui/config/ConfigWeatherStation.qml
C  +40   -87  
applets/weather/package/contents/ui/config/WeatherStationPicker.qml [from:
applets/weather/package/contents/ui/config/ConfigWeatherStation.qml - 058%
similarity]
A  +115  -0   
applets/weather/package/contents/ui/config/WeatherStationPickerDialog.qml
[License: GPL (v2+)]

https://commits.kde.org/kdeplasma-addons/1634d5ed82b43d9b86efd2e0d69fa137865292ba

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

[plasma-nm] [Bug 393794] Scrollbar in main window barely visible with Breeze Dark desktop theme - should use ScrollView from QtQuickControls

2018-05-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=393794

--- Comment #2 from yst...@posteo.net ---
Cheers!

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

[okular] [Bug 325119] Size of inline notes not adjusted to font size and does not respect drawn boundaries

2018-05-10 Thread Tobias Deiminger
https://bugs.kde.org/show_bug.cgi?id=325119

--- Comment #10 from Tobias Deiminger  ---
(In reply to Chris from comment #9)
> There is also a Poppler bug concerning fonts in annotations which might be
> related to the present matter:
> https://bugs.freedesktop.org/show_bug.cgi?id=65956#c14
> 
> Apparently the font configured to be used in the annotation is ignored in
> general. Maybe this should be fixed and the rest might work then?
> 
There's one more dedicated poppler bug "FreeText annotation ignores font":
https://bugs.freedesktop.org/show_bug.cgi?id=81748
Hopefully we can fix it during GSoC 18, or in some follow up patches.

> Another point is I agree with comment saying that the shape and size of the
> bounding box cannot be reasonably be fixed in advance ("drawn boundaries")
> .
Would you agree with Simone in comment 7?
> default behavior of an inline note should be to resize the rectangle
> in order to show all the text and allow the user to resize it down
Because that's what we try atm, even for a "drawn boundary". It just doesn't
work 100% perfect because of more subtle problems (font ignored, different
rendering engines at work).

> I think it should be marked as duplicate of the above Poppler bug; and as
> for the "drawn boundaries", a wishlist bug should be opened where the
> intended behavior of the "drawn box" could be discussed.
Poppler is hosted by freedesktop, Okular is hosted by KDE. We can't mark
duplicates between different projects on different hosts, can we? But giving a
link in each place is always good.

> Also, since applications 17.08, it is very easy to reshape the box after the
> text is entered.
Glad if it's useful:)

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

[kopete] [Bug 394106] New: Unable to show old histories after recent update!!!

2018-05-10 Thread droidSumit
https://bugs.kde.org/show_bug.cgi?id=394106

Bug ID: 394106
   Summary: Unable to show old histories after recent update!!!
   Product: kopete
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: History Plugin
  Assignee: kopete-bugs-n...@kde.org
  Reporter: droidsu...@gmail.com
  Target Milestone: ---

Hi,

Recently my system with KDE Neon got updated and as part of that Kopete too got
updated to new kopete with KF5. 

But soon after the update following issues I faced:
1. My Jabber account got deleted
2. I added back the jabber account but my old **History** is not showing.
3. Configure Video device is broken none of the option work

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

[kdevelop] [Bug 394105] New: Clicking on build error will not give focus to editor component

2018-05-10 Thread Rolf Eike Beer
https://bugs.kde.org/show_bug.cgi?id=394105

Bug ID: 394105
   Summary: Clicking on build error will not give focus to editor
component
   Product: kdevelop
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: k...@opensource.sf-tec.de
  Target Milestone: ---

If clicking on a build error in the build log the editor component will scroll
to the given position, but it will not receive focus. Cursor keys etc. will
still scroll the log window.

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

[digikam] [Bug 393399] windows defender freaks out in windows 10 and Edge

2018-05-10 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=393399

Maik Qualmann  changed:

   What|Removed |Added

   Version Fixed In||6.0.0
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #10 from Maik Qualmann  ---
Tested today, the server mirror.mit.edu is no longer on the blacklist. I close
the bug now.

Maik

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

[kdevelop] [Bug 394104] New: Warning that previous program is still running even if build failed

2018-05-10 Thread Rolf Eike Beer
https://bugs.kde.org/show_bug.cgi?id=394104

Bug ID: 394104
   Summary: Warning that previous program is still running even if
build failed
   Product: kdevelop
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: CPP Debugger
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: k...@opensource.sf-tec.de
CC: niko.s...@gmail.com
  Target Milestone: ---

-set up everything that you can debug a program
-intentionally introduce a syntax error in your program
-hit Alt-F9 -> compilation will fail
-fix it, hit Alt-F9
-> warning that previous instance is still running, even if it never was
started.

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

[kdelibs] [Bug 180051] [KDE4] Need a way to have default printer settings

2018-05-10 Thread Michael Weghorn
https://bugs.kde.org/show_bug.cgi?id=180051

--- Comment #105 from Michael Weghorn  ---
The issue that a printer's default CUPS options are not properly initialized in
the print dialog has been fixed upstream in Qt now, along with several other
improvements of the Qt print dialog.

Most of the improvements will be contained in Qt version 5.11 already (s. [1]
for more details), while the proper initialization of the duplex option --
which is mentioned in this bug report pretty often -- will be implemented in Qt
5.12 (s. [2]).

I therefore suggest to close this bug as RESOLVED UPSTREAM - and will do so
soon unless any objections are brought up here in the meantime.

[1] https://www.kdab.com/better-support-for-cups-features-in-qt-5-11/
[2] https://codereview.qt-project.org/#/c/226881/

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

[krita] [Bug 394103] New: Reference Images Tool in 4.02 Pre-Alpha seem to be blurry

2018-05-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=394103

Bug ID: 394103
   Summary: Reference Images Tool in 4.02 Pre-Alpha seem to be
blurry
   Product: krita
   Version: 4.0.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: reptilli...@live.com
  Target Milestone: ---

1. Generate a .png image from a sharp vector image. You could even use Krita
for this by making a circle with a few line on a vector layer, and exporting
the result.
2. Load the generated image into Krita 4.0.2 Pre-Alpha
3. Load the generated image as a reference image
4. Move the reference image
5. Note how the reference image is a slight blurrier even when size are the
same

There should some way to disable anti-aliasing on the reference image.

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

[marble] [Bug 394102] New: crash on expanding gpx file node

2018-05-10 Thread rainer
https://bugs.kde.org/show_bug.cgi?id=394102

Bug ID: 394102
   Summary: crash on expanding gpx file node
   Product: marble
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: marble-b...@kde.org
  Reporter: kdeb...@munin-soft.de
  Target Milestone: ---

Application: marble (2.2.20 (2.3 development version))

Qt Version: 5.10.0
Frameworks Version: 5.45.0
Operating System: Linux 4.16.6-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
I loaded a gpx track and started to expand the node in the file view. When
trying to expand the second level, marble crashed

-- Backtrace:
Application: Marble – Virtueller Globus (marble), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
28return SYSCALL_CANCEL (nanosleep, requested_time, remaining);
[Current thread is 1 (Thread 0x7fcbddf24940 (LWP 22135))]

Thread 12 (Thread 0x7fcb4d6de700 (LWP 22202)):
#0  0x7fcbd2b47899 in futex_reltimed_wait_cancelable (private=, reltime=0x7fcb4d6ddb20, expected=0, futex_word=0x7fcb50005760) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7fcbd2b47899 in __pthread_cond_wait_common (abstime=0x7fcb4d6ddbe0,
mutex=0x7fcb50005710, cond=0x7fcb50005738) at pthread_cond_wait.c:533
#2  0x7fcbd2b47899 in __pthread_cond_timedwait (cond=0x7fcb50005738,
mutex=0x7fcb50005710, abstime=0x7fcb4d6ddbe0) at pthread_cond_wait.c:667
#3  0x7fcbd9b76dc8 in QWaitConditionPrivate::wait_relative(unsigned long)
(time=3, this=0x7fcb50005710) at thread/qwaitcondition_unix.cpp:133
#4  0x7fcbd9b76dc8 in QWaitConditionPrivate::wait(unsigned long)
(time=3, this=0x7fcb50005710) at thread/qwaitcondition_unix.cpp:141
#5  0x7fcbd9b76dc8 in QWaitCondition::wait(QMutex*, unsigned long)
(this=this@entry=0x7fcb500054b0, mutex=mutex@entry=0x560c8f99c130, time=3)
at thread/qwaitcondition_unix.cpp:215
#6  0x7fcbd9b7305e in QThreadPoolThread::run() (this=0x7fcb500054a0) at
thread/qthreadpool.cpp:146
#7  0x7fcbd9b75ba0 in QThreadPrivate::start(void*) (arg=0x7fcb500054a0) at
thread/qthread_unix.cpp:376
#8  0x7fcbd2b4159b in start_thread (arg=0x7fcb4d6de700) at
pthread_create.c:463
#9  0x7fcbd9256a1f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 11 (Thread 0x7fcb5dcbc700 (LWP 22172)):
#0  0x7fcbd2b4756c in futex_wait_cancelable (private=,
expected=0, futex_word=0x7fcbc584105c) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fcbd2b4756c in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7fcbc5841008, cond=0x7fcbc5841030) at pthread_cond_wait.c:502
#2  0x7fcbd2b4756c in __pthread_cond_wait (cond=0x7fcbc5841030,
mutex=0x7fcbc5841008) at pthread_cond_wait.c:655
#3  0x7fcbd97f0b3c in __gthread_cond_wait (__mutex=,
__cond=) at
/usr/src/debug/gcc8-8.0.1+r259636-1.2.x86_64/obj-x86_64-suse-linux/x86_64-suse-linux/libstdc++-v3/include/x86_64-suse-linux/bits/gthr-default.h:864
#4  0x7fcbd97f0b3c in
std::condition_variable::wait(std::unique_lock&) (this=, __lock=...) at
../../../../../libstdc++-v3/src/c++11/condition_variable.cc:53
#5  0x7fcbd6333e89 in WTF::ParkingLot::parkConditionally(void const*,
std::function, std::function,
std::chrono::time_point > >) () at
/usr/lib64/libQt5WebKit.so.5
#6  0x7fcbd6332b90 in  () at /usr/lib64/libQt5WebKit.so.5
#7  0x7fcbd6336e68 in  () at /usr/lib64/libQt5WebKit.so.5
#8  0x7fcbd636952a in  () at /usr/lib64/libQt5WebKit.so.5
#9  0x7fcbd2b4159b in start_thread (arg=0x7fcb5dcbc700) at
pthread_create.c:463
#10 0x7fcbd9256a1f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 10 (Thread 0x7fcb5ecbe700 (LWP 22171)):
#0  0x7fcbd2b4756c in futex_wait_cancelable (private=,
expected=0, futex_word=0x7fcbc5825058) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fcbd2b4756c in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7fcbc5825008, cond=0x7fcbc5825030) at pthread_cond_wait.c:502
#2  0x7fcbd2b4756c in __pthread_cond_wait (cond=0x7fcbc5825030,
mutex=0x7fcbc5825008) at pthread_cond_wait.c:655
#3  0x7fcbd97f0b3c in __gthread_cond_wait (__mutex=,
__cond=) at
/usr/src/debug/gcc8-8.0.1+r259636-1.2.x86_64/obj-x86_64-suse-linux/x86_64-suse-linux/libstdc++-v3/include/x86_64-suse-linux/bits/gthr-default.h:864
#4  0x7fcbd97f0b3c in
std::condition_variable::wait(std::unique_lock&) (this=, __lock=...) at
../../../../../libstdc++-v3/src/c++11/condition_variable.cc:53
#5  0x7fcbd6333e89 in WTF::ParkingLot::parkConditionally(void const*,
std::function, std::function,
std::chrono::time_point > >) () at
/usr/lib64/libQt5WebKit.so.5
#6  0x7fcbd6332b90 in  () at /usr/lib64/libQt5WebKit.so.5
#7  0x7fcbd6336e68 in  () at /usr/lib64/lib

[digikam] [Bug 392134] SIGSEGV While Scanning Faces [patch]

2018-05-10 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=392134

--- Comment #33 from Maik Qualmann  ---
Gilles, would be nice if you press the button again. Only the AppImage is
needed.

Maik

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

[digikam] [Bug 392134] SIGSEGV While Scanning Faces [patch]

2018-05-10 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=392134

--- Comment #32 from Maik Qualmann  ---
Git commit 979c7b188435ccd38e5dbd76b492d1e8b5505da0 by Maik Qualmann.
Committed on 10/05/2018 at 18:26.
Pushed by mqualmann into branch 'master'.

QHash test, this commit is for testing purposes only and will be revert

M  +24   -8core/libs/threadimageio/loadingcache.cpp

https://commits.kde.org/digikam/979c7b188435ccd38e5dbd76b492d1e8b5505da0

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

[marble] [Bug 394101] New: Crash when working with a GPX-track

2018-05-10 Thread rainer
https://bugs.kde.org/show_bug.cgi?id=394101

Bug ID: 394101
   Summary: Crash when working with a GPX-track
   Product: marble
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: marble-b...@kde.org
  Reporter: kdeb...@munin-soft.de
  Target Milestone: ---

Application: marble (2.2.20 (2.3 development version))

Qt Version: 5.10.0
Frameworks Version: 5.45.0
Operating System: Linux 4.16.6-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
I had loaded a GPX-track into marbel and wnated to visualize it. I enabled the
'Files' view deselected some of the entries and reselected them. They started
to appear in the 'Search' view (where they haven't been present before. While
reselecting the GPX track and then trying to expand the node in the files view,
Marble crashed.

-- Backtrace:
Application: Marble – Virtueller Globus (marble), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
28return SYSCALL_CANCEL (nanosleep, requested_time, remaining);
[Current thread is 1 (Thread 0x7f70e1dae940 (LWP 19507))]

Thread 12 (Thread 0x7f7061dfe700 (LWP 19627)):
#0  0x7f70d69d156c in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f70c9838058) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f70d69d156c in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7f70c9838008, cond=0x7f70c9838030) at pthread_cond_wait.c:502
#2  0x7f70d69d156c in __pthread_cond_wait (cond=0x7f70c9838030,
mutex=0x7f70c9838008) at pthread_cond_wait.c:655
#3  0x7f70dd67ab3c in __gthread_cond_wait (__mutex=,
__cond=) at
/usr/src/debug/gcc8-8.0.1+r259636-1.2.x86_64/obj-x86_64-suse-linux/x86_64-suse-linux/libstdc++-v3/include/x86_64-suse-linux/bits/gthr-default.h:864
#4  0x7f70dd67ab3c in
std::condition_variable::wait(std::unique_lock&) (this=, __lock=...) at
../../../../../libstdc++-v3/src/c++11/condition_variable.cc:53
#5  0x7f70da1bde89 in WTF::ParkingLot::parkConditionally(void const*,
std::function, std::function,
std::chrono::time_point > >) () at
/usr/lib64/libQt5WebKit.so.5
#6  0x7f70da1bcb90 in  () at /usr/lib64/libQt5WebKit.so.5
#7  0x7f70da1c0e68 in  () at /usr/lib64/libQt5WebKit.so.5
#8  0x7f70da1f352a in  () at /usr/lib64/libQt5WebKit.so.5
#9  0x7f70d69cb59b in start_thread (arg=0x7f7061dfe700) at
pthread_create.c:463
#10 0x7f70dd0e0a1f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 11 (Thread 0x7f70625ff700 (LWP 19626)):
#0  0x7f70d69d156c in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f70c990e058) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f70d69d156c in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7f70c990e008, cond=0x7f70c990e030) at pthread_cond_wait.c:502
#2  0x7f70d69d156c in __pthread_cond_wait (cond=0x7f70c990e030,
mutex=0x7f70c990e008) at pthread_cond_wait.c:655
#3  0x7f70dd67ab3c in __gthread_cond_wait (__mutex=,
__cond=) at
/usr/src/debug/gcc8-8.0.1+r259636-1.2.x86_64/obj-x86_64-suse-linux/x86_64-suse-linux/libstdc++-v3/include/x86_64-suse-linux/bits/gthr-default.h:864
#4  0x7f70dd67ab3c in
std::condition_variable::wait(std::unique_lock&) (this=, __lock=...) at
../../../../../libstdc++-v3/src/c++11/condition_variable.cc:53
#5  0x7f70da1bde89 in WTF::ParkingLot::parkConditionally(void const*,
std::function, std::function,
std::chrono::time_point > >) () at
/usr/lib64/libQt5WebKit.so.5
#6  0x7f70da1bcb90 in  () at /usr/lib64/libQt5WebKit.so.5
#7  0x7f70da1c0e68 in  () at /usr/lib64/libQt5WebKit.so.5
#8  0x7f70da1f352a in  () at /usr/lib64/libQt5WebKit.so.5
#9  0x7f70d69cb59b in start_thread (arg=0x7f70625ff700) at
pthread_create.c:463
#10 0x7f70dd0e0a1f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 10 (Thread 0x7f70537fe700 (LWP 19625)):
#0  0x7f70d69d156c in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f70c990e1a8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f70d69d156c in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7f70c990e158, cond=0x7f70c990e180) at pthread_cond_wait.c:502
#2  0x7f70d69d156c in __pthread_cond_wait (cond=0x7f70c990e180,
mutex=0x7f70c990e158) at pthread_cond_wait.c:655
#3  0x7f70dd67ab3c in __gthread_cond_wait (__mutex=,
__cond=) at
/usr/src/debug/gcc8-8.0.1+r259636-1.2.x86_64/obj-x86_64-suse-linux/x86_64-suse-linux/libstdc++-v3/include/x86_64-suse-linux/bits/gthr-default.h:864
#4  0x7f70dd67ab3c in
std::condition_variable::wait(std::unique_lock&) (this=, __lock=...) at
../../../../../libstdc++-v3/src/c++11/condition_variable.cc:53
#5  0x7f70da1bde89 in WTF::ParkingLot::parkConditionally(void const*,
std::function, std::funct

[digikam] [Bug 392134] SIGSEGV While Scanning Faces [patch]

2018-05-10 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=392134

--- Comment #31 from Maik Qualmann  ---
It may also be that it is more likely with the AppImage. The QHash are "salted"
with a value of a random number generator. Maybe here is something "different"
in the AppImage. I will insert the test in git/master and Gilles presses the
button.

Maik

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

[plasmashell] [Bug 394100] New: [Wayland+Nouveau] Desktop crashed after login.

2018-05-10 Thread Tony
https://bugs.kde.org/show_bug.cgi?id=394100

Bug ID: 394100
   Summary: [Wayland+Nouveau] Desktop crashed after login.
   Product: plasmashell
   Version: 5.12.4
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: jodr...@live.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.12.4)

Qt Version: 5.11.0
Frameworks Version: 5.45.0
Operating System: Linux 4.16.6-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
Just updated my system, rebooted and login into a wayland session. The crash
happen soon after the panels showed up.

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

Thread 11 (Thread 0x7fdffa0eb700 (LWP 9699)):
#0  0x7fe0c49fd56c in futex_wait_cancelable (private=,
expected=0, futex_word=0x7fdff00bca00) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x7fdff00bc9b0,
cond=0x7fdff00bc9d8) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x7fdff00bc9d8, mutex=0x7fdff00bc9b0) at
pthread_cond_wait.c:655
#3  0x7fe0c585e86b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib64/libQt5Core.so.5
#4  0x7fe0c961b558 in QSGRenderThread::processEventsAndWaitForMore() ()
from /usr/lib64/libQt5Quick.so.5
#5  0x7fe0c961b93a in QSGRenderThread::run() () from
/usr/lib64/libQt5Quick.so.5
#6  0x7fe0c585daf8 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#7  0x7fe0c49f759b in start_thread (arg=0x7fdffa0eb700) at
pthread_create.c:463
#8  0x7fe0c5151a1f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 10 (Thread 0x7fdffa8ec700 (LWP 9698)):
#0  0x7fe0c49fd56c in futex_wait_cancelable (private=,
expected=0, futex_word=0x564e66f04e34) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x564e66f04de0,
cond=0x564e66f04e08) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x564e66f04e08, mutex=0x564e66f04de0) at
pthread_cond_wait.c:655
#3  0x7fe0c585e86b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib64/libQt5Core.so.5
#4  0x7fe0c961b558 in QSGRenderThread::processEventsAndWaitForMore() ()
from /usr/lib64/libQt5Quick.so.5
#5  0x7fe0c961b93a in QSGRenderThread::run() () from
/usr/lib64/libQt5Quick.so.5
#6  0x7fe0c585daf8 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#7  0x7fe0c49f759b in start_thread (arg=0x7fdffa8ec700) at
pthread_create.c:463
#8  0x7fe0c5151a1f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 9 (Thread 0x7fdffb114700 (LWP 9695)):
#0  0x7fe0c49fd56c in futex_wait_cancelable (private=,
expected=0, futex_word=0x564e66da02a0) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x564e66da0250,
cond=0x564e66da0278) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x564e66da0278, mutex=0x564e66da0250) at
pthread_cond_wait.c:655
#3  0x7fe0c585e86b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib64/libQt5Core.so.5
#4  0x7fe0c961b558 in QSGRenderThread::processEventsAndWaitForMore() ()
from /usr/lib64/libQt5Quick.so.5
#5  0x7fe0c961b93a in QSGRenderThread::run() () from
/usr/lib64/libQt5Quick.so.5
#6  0x7fe0c585daf8 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#7  0x7fe0c49f759b in start_thread (arg=0x7fdffb114700) at
pthread_create.c:463
#8  0x7fe0c5151a1f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 8 (Thread 0x7fdffbb66700 (LWP 9694)):
[KCrash Handler]
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#7  0x7fe0c508fda1 in __GI_abort () at abort.c:79
#8  0x7fe0c508710a in __assert_fail_base (fmt=0x7fe0c51dc460 "%s%s%s:%u:
%s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fe0a48a5cb5
"kref", file=file@entry=0x7fe0a48a5caa "pushbuf.c", line=line@entry=727,
function=function@entry=0x7fe0a48a5ce0 <__PRETTY_FUNCTION__.6480>
"nouveau_pushbuf_data") at assert.c:92
#9  0x7fe0c5087182 in __GI___assert_fail
(assertion=assertion@entry=0x7fe0a48a5cb5 "kref",
file=file@entry=0x7fe0a48a5caa "pushbuf.c", line=line@entry=727,
function=function@entry=0x7fe0a48a5ce0 <__PRETTY_FUNCTION__.6480>
"nouveau_pushbuf_data") at assert.c:101
#10 0x7fe0a48a4128 in nouveau_pushbuf_data (push=push@entry=0x564e651158c0,
bo=0x564e65115a80, offset=19700, length=928) at pushbuf.c:727
#11 0x7fe0a48a40f0 in nouveau_pushbuf_data (push=push@entry=0x564e651158c0,
bo=bo@entry=0x

[frameworks-baloo] [Bug 375370] Unable to remove a folder from excludeFolders list

2018-05-10 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=375370

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|REOPENED|NEEDSINFO

--- Comment #5 from Nate Graham  ---
Can you phrase the problem in terms of Steps To Reproduce? See
https://community.kde.org/Get_Involved/Bug_Reporting#Steps_to_Reproduce

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

[kwin] [Bug 393284] KWin Segfault Regression in Plasma 5.12.4 re Fall Apart + Desktop Grid.

2018-05-10 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=393284

Christoph Feck  changed:

   What|Removed |Added

 Status|NEEDSINFO   |UNCONFIRMED
 Resolution|BACKTRACE   |---

--- Comment #10 from Christoph Feck  ---
Thanks for the update. The abort message is "Splitting quads is allowed only in
pre-paint calls!", see also bug 368847.

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

[krusader] [Bug 393866] missing progress bar

2018-05-10 Thread Todd
https://bugs.kde.org/show_bug.cgi?id=393866

--- Comment #6 from Todd  ---
Created attachment 112567
  --> https://bugs.kde.org/attachment.cgi?id=112567&action=edit
Thunar progess bar

This is what Thunar's progress bar looks like

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

[cantor] [Bug 387303] lateX-export generates outdated code for matrices

2018-05-10 Thread Alexander Semke
https://bugs.kde.org/show_bug.cgi?id=387303

Alexander Semke  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

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

[cantor] [Bug 387303] lateX-export generates outdated code for matrices

2018-05-10 Thread Alexander Semke
https://bugs.kde.org/show_bug.cgi?id=387303

Alexander Semke  changed:

   What|Removed |Added

   Version Fixed In||18.04.1
  Latest Commit||220b864d6ac26efae7081f53ab6
   ||cadb96dcb3076

--- Comment #1 from Alexander Semke  ---
This was fixed for Maxima matrices. Please check it in 18.04.1

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

[kdevelop] [Bug 393138] “Delete session” confirmation dialog lacks session name

2018-05-10 Thread Sven Brauch
https://bugs.kde.org/show_bug.cgi?id=393138

--- Comment #9 from Sven Brauch  ---
Hi, please submit your review requests on phabricator.kde.org. Thank you!

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

[krita] [Bug 394068] Can't copy between kra files, causes Runtime error

2018-05-10 Thread Boudewijn Rempt
https://bugs.kde.org/show_bug.cgi?id=394068

--- Comment #3 from Boudewijn Rempt  ---
https://bugs.kde.org/show_bug.cgi?id=394098 is probably a duplicate, even
though the way to get to the crash is different.

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

[krita] [Bug 394098] Krita crashes when trying to move a layer

2018-05-10 Thread Boudewijn Rempt
https://bugs.kde.org/show_bug.cgi?id=394098

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO
 CC||b...@valdyas.org

--- Comment #1 from Boudewijn Rempt  ---
Hi,

I'm pretty sure this is the same issue as with bug 394068 -- even though
there's a different way to reach the output. Since you're on arch linux, could
you make sure you've got the debug info installed and create a proper
backtrace?

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

[kmail2] [Bug 394099] New: Weird black box appearing alongside the split between message list and preview

2018-05-10 Thread clivejo
https://bugs.kde.org/show_bug.cgi?id=394099

Bug ID: 394099
   Summary: Weird black box appearing alongside the split between
message list and preview
   Product: kmail2
   Version: 5.8.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: cliv...@protonmail.com
  Target Milestone: ---

Created attachment 112566
  --> https://bugs.kde.org/attachment.cgi?id=112566&action=edit
Weird Black box

There is a weird black box appearing alongside the split between message list
and preview.

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

[elisa] [Bug 391496] Crash when spamming the "Configure Elisa" action through hotkeys

2018-05-10 Thread Matthieu Gallien
https://bugs.kde.org/show_bug.cgi?id=391496

Matthieu Gallien  changed:

   What|Removed |Added

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

--- Comment #3 from Matthieu Gallien  ---
Thanks for your report. Please let us know if you have other issues.

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

[krita] [Bug 393508] Krita 4.0.1 crashes when creating a canvas

2018-05-10 Thread Boudewijn Rempt
https://bugs.kde.org/show_bug.cgi?id=393508

Boudewijn Rempt  changed:

   What|Removed |Added

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

--- Comment #19 from Boudewijn Rempt  ---
Okay, thanks for getting back to me. I'm not sure what should be done next --
that really depends on your individual system setup.

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

  1   2   3   >