[kdeconnect] [Bug 330536] Bluetooth device link

[Brian G .]

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

Brian G.  changed:

   What|Removed |Added

 CC||gis...@gmail.com

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

[kwin] [Bug 379472] Kwin crashes when attempting to start session.

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |INVALID
 Status|NEEDSINFO   |RESOLVED

--- Comment #5 from Martin Gräßlin  ---
Changing to invalid as KWin must be run against the Qt version it was compiled
with.

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

[kwin] [Bug 363224] Kwin crashes from time to time (this time using Virtual Machine Manager)

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

 CC||jv...@altsci.com

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

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

[kwin] [Bug 379493] Kwin Crashes rarely on pinentry dialog

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---


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

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

[kwin] [Bug 379472] Kwin crashes when attempting to start session.

[bugzilla_noreply]

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

kishor...@gmail.com changed:

   What|Removed |Added

 Attachment #105323|0   |1
is obsolete||

--- Comment #4 from kishor...@gmail.com ---
Created attachment 105334
  --> https://bugs.kde.org/attachment.cgi?id=105334=edit
Backtrace with debug symbols for Qt

I have attached a backtrace generated after installing qt with debug symbols.

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

[Breeze] [Bug 379498] Expose QStyle::SH_ScrollBar_LeftClickAbsolutePosition in Widget Style > Scrollbars for Breeze style

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Severity|normal  |wishlist

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

[Breeze] [Bug 379498] New: Expose QStyle::SH_ScrollBar_LeftClickAbsolutePosition in Widget Style > Scrollbars for Breeze style

[Nate Graham]

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

Bug ID: 379498
   Summary: Expose QStyle::SH_ScrollBar_LeftClickAbsolutePosition
in Widget Style > Scrollbars for Breeze style
   Product: Breeze
   Version: 5.9.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: QStyle
  Assignee: hugo.pereira.da.co...@gmail.com
  Reporter: pointedst...@zoho.com
  Target Milestone: ---

Linux Distro: openSUSE Tumbleweed
Plasma version: 5.9.5
Breeze version: 5.9.5

I prefer the scrollbar style where left-clicking on the scroll track jumps the
bar to that location (i.e. the current behavior for a middle-click). To get
this behavior in GTK programs, I can set "gtk-primary-button-warps-slider=1" in
~/.config/gtk-3.0/settings.ini. For QT programs, the equivalent setting is
QStyle::SH_ScrollBar_LeftClickAbsolutePosition, but Breeze doesn't expose that
setting in the GUI, at System Settings > Widget Style > Scrollbars.

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

[Breeze] [Bug 379498] Expose QStyle::SH_ScrollBar_LeftClickAbsolutePosition in Widget Style > Scrollbars for Breeze style

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[okular] [Bug 379497] New: Okular crashed when closing

[bugzilla_noreply]

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

Bug ID: 379497
   Summary: Okular crashed when closing
   Product: okular
   Version: 0.25.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: amamiyam...@gmail.com
  Target Milestone: ---

Application: okular (0.25.0)
KDE Platform Version: 4.14.22
Qt Version: 4.8.7
Operating System: Linux 4.10.12-ram x86_64
Distribution: Ubuntu 16.04.2 LTS

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

I closed the Okular app that I opened last night by clicking on the 'X' button
on title bar. And then it crashed.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Okular (okular), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fee985a7900 (LWP 6086))]

Thread 2 (Thread 0x7fee7dacd700 (LWP 6091)):
#0  0x7fee95736b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fee91db438c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fee91db449c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fee96c3723e in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x7fee96c0513f in
QEventLoop::processEvents(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#5  0x7fee96c054a5 in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x7fee96af4549 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x7fee96be51d3 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x7fee96af6e3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x7fee928ed6ba in start_thread (arg=0x7fee7dacd700) at
pthread_create.c:333
#10 0x7fee9574282d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fee985a7900 (LWP 6086)):
[KCrash Handler]
#6  0x7fee95671428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7fee9567302a in __GI_abort () at abort.c:89
#8  0x7fee956b37ea in __libc_message (do_abort=do_abort@entry=2,
fmt=fmt@entry=0x7fee957cc2e0 "*** Error in `%s': %s: 0x%s ***\n") at
../sysdeps/posix/libc_fatal.c:175
#9  0x7fee956bbe0a in malloc_printerr (ar_ptr=,
ptr=, str=0x7fee957c90b2 "free(): invalid pointer", action=3) at
malloc.c:5004
#10 _int_free (av=, p=, have_lock=0) at
malloc.c:3865
#11 0x7fee956bf98c in __GI___libc_free (mem=) at
malloc.c:2966
#12 0x7fee96c1f221 in QObjectPrivate::deleteChildren() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#13 0x7fee95fa22a2 in QWidget::~QWidget() () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#14 0x7fee86878024 in ?? () from /usr/lib/kde4/okularpart.so
#15 0x7fee86878169 in ?? () from /usr/lib/kde4/okularpart.so
#16 0x7fee868101f8 in Okular::Part::~Part() () from
/usr/lib/kde4/okularpart.so
#17 0x7fee86810539 in Okular::Part::~Part() () from
/usr/lib/kde4/okularpart.so
#18 0x7fee96c1f221 in QObjectPrivate::deleteChildren() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#19 0x7fee95fa22a2 in QWidget::~QWidget() () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#20 0x7fee979d0b56 in KMainWindow::~KMainWindow() () from
/usr/lib/libkdeui.so.5
#21 0x00410256 in ?? ()
#22 0x00410349 in ?? ()
#23 0x7fee96c20d48 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#24 0x7fee95fa2d3c in QWidget::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#25 0x7fee96387063 in QMainWindow::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#26 0x7fee97a108e9 in KXmlGuiWindow::event(QEvent*) () from
/usr/lib/libkdeui.so.5
#27 0x7fee95f4bfdc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#28 0x7fee95f52f16 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#29 0x7fee9790b6ba in KApplication::notify(QObject*, QEvent*) () from
/usr/lib/libkdeui.so.5
#30 0x7fee96c068bd in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#31 0x7fee96c0a376 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#32 0x7fee96c370ae in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#33 0x7fee91db4197 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#34 0x7fee91db43f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#35 0x7fee91db449c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#36 0x7fee96c3721e in

[digikam] [Bug 379420] showPhoto crashed after resize

[bugzilla_noreply]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com
   Platform|unspecified |Gentoo Packages

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

[gwenview] [Bug 379458] Crash at loading a certaing jpg file

[bugzilla_noreply]

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

--- Comment #2 from ndw...@gmail.com ---
I guess providing bug reports for debian stable is not helpful, isn't it?

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

[kdeconnect] [Bug 336043] SFTP: Should be able to browse external SD cards via SFTP too

[bugzilla_noreply]

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

airfullb...@hotmail.com changed:

   What|Removed |Added

 CC||airfullb...@hotmail.com

--- Comment #72 from airfullb...@hotmail.com ---
Galaxy S8+ can be added to the list.

Root folder on the external SD card is shown empty. If I manually enter the
path of a subdirectory, then I can browse it.

I am also unable to write a file to the external SD card (permission problem).
This is the most problematic part imho.

AB

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

[akregator] [Bug 379496] New: akregator crashes on startup

[Peter Gückel]

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

Bug ID: 379496
   Summary: akregator crashes on startup
   Product: akregator
   Version: 5.4.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: pguec...@gmail.com
  Target Milestone: ---

Application: akregator (5.4.3)

Qt Version: 5.7.1
Frameworks Version: 5.33.0
Operating System: Linux 4.11.0-1.fc26.x86_64 x86_64
Distribution: "Fedora release 26 (Twenty Six)"

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

I clicked the icon in the launcher and the application crashed. This has been
going on for about a week, likely since plasma 5.9.5-2 on fedora 26 alpha was
in the repo.

The crash can be reproduced every time.

-- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f04fc5ba600 (LWP 2164))]

Thread 19 (Thread 0x7f047a526700 (LWP 2196)):
#0  0x7f05156737db in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0509c66534 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from
/lib64/libQt5Script.so.5
#2  0x7f0509c66579 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*)
() from /lib64/libQt5Script.so.5
#3  0x7f051566d36d in start_thread () from /lib64/libpthread.so.0
#4  0x7f051ee86e0f in clone () from /lib64/libc.so.6

Thread 18 (Thread 0x7f04a57fa700 (LWP 2191)):
#0  0x7f051ee7641d in read () from /lib64/libc.so.6
#1  0x7f050eb0e1e0 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0
#2  0x7f050eaca038 in g_main_context_check () from /lib64/libglib-2.0.so.0
#3  0x7f050eaca4d0 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#4  0x7f050eaca63c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#5  0x7f051fc96d0b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#6  0x7f051fc46b8a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#7  0x7f051fa9befa in QThread::exec() () from /lib64/libQt5Core.so.5
#8  0x7f051faa01ee in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#9  0x7f051566d36d in start_thread () from /lib64/libpthread.so.0
#10 0x7f051ee86e0f in clone () from /lib64/libc.so.6

Thread 17 (Thread 0x7f04a6ffd700 (LWP 2188)):
#0  0x7f05156737db in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0518a82bb5 in
base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*)
() from /lib64/libQt5WebEngineCore.so.5
#2  0x7f0518a83009 in base::SequencedWorkerPool::Worker::Run() () from
/lib64/libQt5WebEngineCore.so.5
#3  0x7f0518a831b1 in base::SimpleThread::ThreadMain() () from
/lib64/libQt5WebEngineCore.so.5
#4  0x7f0518a7fdeb in base::(anonymous namespace)::ThreadFunc(void*) ()
from /lib64/libQt5WebEngineCore.so.5
#5  0x7f051566d36d in start_thread () from /lib64/libpthread.so.0
#6  0x7f051ee86e0f in clone () from /lib64/libc.so.6

Thread 16 (Thread 0x7f04a77fe700 (LWP 2187)):
#0  0x7f051ee7641d in read () from /lib64/libc.so.6
#1  0x7f05023f40b1 in pa_read () from
/usr/lib64/pulseaudio/libpulsecommon-10.0.so
#2  0x7f050dd8111e in pa_mainloop_prepare () from /lib64/libpulse.so.0
#3  0x7f050dd81b90 in pa_mainloop_iterate () from /lib64/libpulse.so.0
#4  0x7f050dd81c50 in pa_mainloop_run () from /lib64/libpulse.so.0
#5  0x7f050dd8fab9 in thread () from /lib64/libpulse.so.0
#6  0x7f0502423078 in internal_thread_func () from
/usr/lib64/pulseaudio/libpulsecommon-10.0.so
#7  0x7f051566d36d in start_thread () from /lib64/libpthread.so.0
#8  0x7f051ee86e0f in clone () from /lib64/libc.so.6

Thread 15 (Thread 0x7f04a7fff700 (LWP 2186)):
#0  0x7f0515673cda in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0518a78be2 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () from /lib64/libQt5WebEngineCore.so.5
#2  0x7f0518a79412 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () from /lib64/libQt5WebEngineCore.so.5
#3  0x7f0518a5b00b in
base::MessagePumpDefault::Run(base::MessagePump::Delegate*) () from
/lib64/libQt5WebEngineCore.so.5
#4  0x7f0518a6d908 in base::RunLoop::Run() () from
/lib64/libQt5WebEngineCore.so.5
#5  0x7f0518a834b5 in base::Thread::Run(base::MessageLoop*) () from
/lib64/libQt5WebEngineCore.so.5
#6  0x7f0518a83774 in base::Thread::ThreadMain() () from
/lib64/libQt5WebEngineCore.so.5
#7  0x7f0518a7fdeb in base::(anonymous namespace)::ThreadFunc(void*) ()
from /lib64/libQt5WebEngineCore.so.5
#8  0x7f051566d36d in start_thread () from /lib64/libpthread.so.0
#9  0x7f051ee86e0f in clone () from /lib64/libc.so.6

Thread 14 (Thread 

[systemsettings] [Bug 379495] New: sending keyboard input of repeating alternate case ignores case on second character

[bugzilla_noreply]

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

Bug ID: 379495
   Summary: sending keyboard input of repeating alternate case
ignores case on second character
   Product: systemsettings
   Version: 5.8.6
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: scott.notting...@gmail.com
  Target Milestone: ---

When creating a "Send Keyboard Input" shortcut, if the sequence involves
sending a lower case letter immediately followed by an upper case of the same
letter, both letters are sent as lower case.  The same is true for the opposite
scenario, where if you first send a capital letter followed by lower case of
the same letter, both result in upper case.

For example, the sequence:
Sequence -- f:Shift+f
Expected result:  fF
Actual result:  ff

Sequence -- Shift+F:f
Expected result: Ff
Actual result:  FF

Work around:
to produce the string fF, use the sequence:
f:f:Backspace:Shift+F

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

[konsole] [Bug 379494] Konsole renders font in incorrect width on startup

[Grief]

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

Grief  changed:

   What|Removed |Added

 CC||iamgr...@gmail.com

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

[konsole] [Bug 379494] New: Konsole renders font in incorrect width on startup

[Grief]

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

Bug ID: 379494
   Summary: Konsole renders font in incorrect width on startup
   Product: konsole
   Version: 17.04.0
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: font
  Assignee: konsole-de...@kde.org
  Reporter: iamgr...@gmail.com
  Target Milestone: ---

When I use konsole (or yakuake) when the app started, fonts are rendered very
wide, but if I set the font to the exact same font in konsole settings - it
starts to be rendered correctly until the restart. The issue didn't appear in
version 15.12.3 for sure. 

I recorded a small video to demonstrate the issue:
https://www.youtube.com/watch?v=psAeKRFxXv4

The font I am using is Input, it can be downloaded here
http://input.fontbureau.com/preview/

I am experiencing the issue not with every font, but I really like this one and
don't want to change it to ubuntu mono or something. Konsole is the only app in
the system (including other KDE apps) which renders it wrong.

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

[kwin] [Bug 379493] New: Kwin Crashes rarely on pinentry dialog

[Joel R . Voss]

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

Bug ID: 379493
   Summary: Kwin Crashes rarely on pinentry dialog
   Product: kwin
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: jv...@altsci.com
  Target Milestone: ---

Created attachment 105333
  --> https://bugs.kde.org/attachment.cgi?id=105333=edit
Kwin crash data

I wrote a mail client that uses gpgme to handle PGP. On rare occasion (1/50 or
so decryption/signs) kwin will crash as pinentry pops up. The crash handler
comes up and I save the crash information.

I am happy to help debug this issue as it is blocking release of my mail
client. I hope very much that someone will be able to find a reliable repro
this issue or fix it.

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

[Discover] [Bug 379492] New: probleme plasma discover

[moussa]

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

Bug ID: 379492
   Summary: probleme plasma discover
   Product: Discover
   Version: 5.9.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: diawmou...@live.fr
  Target Milestone: ---

la logiteque discover ne charge pas les paquets. impossible de faire une
recherche d application

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

[krita] [Bug 379491] New: Crash.

[Psicopompo]

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

Bug ID: 379491
   Summary: Crash.
   Product: krita
   Version: 3.1.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: takoj...@gmail.com
  Target Milestone: ---

Application: krita (3.1.3)

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

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

Selecting stock brush.

Application: Krita (krita), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f652eca75c0 (LWP 7738))]

Thread 6 (Thread 0x7f64e90db700 (LWP 7749)):
#0  0x7f652574c756 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f652c35858b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f652d439a91 in ?? () from /usr/lib/libQt5Widgets.so.5
#3  0x7f652c3576d8 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7f65257462e7 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7f652ba5354f in clone () from /usr/lib/libc.so.6

Thread 5 (Thread 0x7f64e98dc700 (LWP 7748)):
#0  0x7f652574c756 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f652c35858b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f652c3517c6 in QSemaphore::tryAcquire(int, int) () from
/usr/lib/libQt5Core.so.5
#3  0x7f652985a0ba in KisTileDataSwapper::run() () from
/usr/lib/libkritaimage.so.16
#4  0x7f652c3576d8 in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7f65257462e7 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7f652ba5354f in clone () from /usr/lib/libc.so.6

Thread 4 (Thread 0x7f64ea0dd700 (LWP 7747)):
#0  0x7f652574c756 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f652c35858b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f652c3514d3 in QSemaphore::acquire(int) () from
/usr/lib/libQt5Core.so.5
#3  0x7f652983db3d in ?? () from /usr/lib/libkritaimage.so.16
#4  0x7f652c3576d8 in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7f65257462e7 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7f652ba5354f in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7f650bcae700 (LWP 7741)):
#0  0x7f652ba4967d in poll () from /usr/lib/libc.so.6
#1  0x7f6523e9f9b6 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f6523e9facc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f652c58709b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f652c5308ca in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f652c352a73 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f6525973125 in ?? () from /usr/lib/libQt5DBus.so.5
#7  0x7f652c3576d8 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f65257462e7 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f652ba5354f in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f6519746700 (LWP 7740)):
#0  0x7f652ba4967d in poll () from /usr/lib/libc.so.6
#1  0x7f6529fd88e0 in ?? () from /usr/lib/libxcb.so.1
#2  0x7f6529fda679 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7f651bea2239 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#4  0x7f652c3576d8 in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7f65257462e7 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7f652ba5354f in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f652eca75c0 (LWP 7738)):
[KCrash Handler]
#6  0x0050 in ?? ()
#7  0x7f652c53b2f9 in QMetaObject::cast(QObject const*) const () from
/usr/lib/libQt5Core.so.5
#8  0x7f652d36f88c in QMdiArea::eventFilter(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#9  0x7f652c5320a6 in
QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#10 0x7f652d214388 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#11 0x7f652d21bb61 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#12 0x7f652e63b677 in KisApplication::notify(QObject*, QEvent*) () from
/usr/lib/libkritaui.so.16
#13 0x7f652c532470 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#14 0x7f652c534bfd in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#15 0x7f652c586c73 in ?? () from /usr/lib/libQt5Core.so.5
#16 0x7f6523e9f7b7 in g_main_context_dispatch () from

[kdenlive] [Bug 379490] Crop, Scale and Tilt effect not working [video example included]

[Jesse]

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

Jesse  changed:

   What|Removed |Added

URL||https://youtu.be/jL5M3vfz6U
   ||o
 CC||jesse.dub...@gmail.com

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

[kdenlive] [Bug 379490] New: Crop, Scale and Tilt effect not working [video example included]

[Jesse]

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

Bug ID: 379490
   Summary: Crop, Scale and Tilt effect not working [video example
included]
   Product: kdenlive
   Version: git-master
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: jesse.dub...@gmail.com
  Target Milestone: ---

See video in URL field for example.

BEHAVIOR
When I apply the "Crop, Scale and Tilt" effect to a clip in the Timeline, it
effectively hides the clip from the Project Monitor. Editing the parameters
doesn't affect anything, visually.

EXPECTED BEHAVIOR
For the "Crop, Scale and Tilt" effect to affect the video clip in Timeline,
normally.

BUG DISCOVERED USING
Kdenlive 17.07.70 via ppa:kdenlive/kdenlive-master
Movit package version 1.4.0-1
Ubuntu GNOME 17.04 x64
GNOME 3.24.0 desktop environment
Linux kernel 4.10.0-20-generic
Nvidia GTX 980ti graphics card
Nvidia 375.39 proprietary graphics driver

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

[digikam] [Bug 379420] showPhoto crashed after resize

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

Version|unspecified |5.5.0
Product|kde |digikam
   Assignee|unassigned-b...@kde.org |digikam-de...@kde.org
  Component|general |showfoto

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

[gwenview] [Bug 379458] Crash at loading a certaing jpg file

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---
Crash is in libexiv2. You could try a newer libexiv2 version.

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

[plasmashell] [Bug 375053] enabling global menu breaks copy/paste shortcuts in qupzilla

[Antonio Rojas]

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

--- Comment #11 from Antonio Rojas  ---
Seems to be fixed for real with Qt 5.9

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

[dolphin] [Bug 379336] Folder icon text label multi line behavior

[Christoph Feck]

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

--- Comment #4 from Christoph Feck  ---
Does changing "Configure Dolphin > View Modes > Text Width" make a difference?

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

[Akonadi] [Bug 379300] Gmail IMAP token/code not saved

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||isalgue...@gmail.com

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

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

[Akonadi] [Bug 379401] Can't add GMail account

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---


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

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

[Akonadi] [Bug 379300] Gmail IMAP token/code not saved

[Christoph Feck]

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

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

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

[Akonadi] [Bug 379320] Akonadi asks GMail for permission to manage account, but has nowhere to paste the code

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---


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

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

[dolphin] [Bug 379489] [Multiple separate X11 screens] [Multiple WMs] Dolphin spawns applications on current active tag of wrong X11 screen

[Manfred Knick]

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

--- Comment #1 from Manfred Knick  ---
Created attachment 105332
  --> https://bugs.kde.org/attachment.cgi?id=105332=edit
emerge --info dbus >> 0_emerge--info-dbus.txt

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

[dolphin] [Bug 379489] New: [Multiple separate X11 screens] [Multiple WMs] Dolphin spawns applications on current active tag of wrong X11 screen

[Manfred Knick]

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

Bug ID: 379489
   Summary: [Multiple separate X11 screens] [Multiple WMs] Dolphin
spawns applications on current active tag of wrong X11
screen
   Product: dolphin
   Version: 17.04.0
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: manfred.kn...@t-online.de
  Target Milestone: ---

Created attachment 105331
  --> https://bugs.kde.org/attachment.cgi?id=105331=edit
emerge --info dolphin >> 0_emerge--info-dolphin.txt

Apps started via file-entries' context menu pop up on a wrong X11 screen.

The real pursuit may well reside inside klauncher or dbus.

In case, please be so kind to re-locate (I am not a QT/KDE expert).

Overview:
https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298620529

Description of Startup Procedure:
https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298611832

Observation of Patterns:
https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298374308

Please, let me know which further information would be helpful.

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

[digikam] [Bug 377197] Customize grouping behaviour [patch]

[Simon]

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

Simon  changed:

   What|Removed |Added

 Attachment #105016|0   |1
is obsolete||

--- Comment #33 from Simon  ---
Created attachment 105330
  --> https://bugs.kde.org/attachment.cgi?id=105330=edit
Customize grouping behavior patch version 9

I updated this with information about the operation in the dialog, streamlined
the setup page creation and added some documentation.

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

[kate] [Bug 379488] New: [Multiple separate X11 screens] [Awesome WM] kate starts on wrong tag of current active X11 screen

[Manfred Knick]

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

Bug ID: 379488
   Summary: [Multiple separate X11 screens] [Awesome WM] kate
starts on wrong tag of current active X11 screen
   Product: kate
   Version: 17.04.0
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: manfred.kn...@t-online.de
  Target Milestone: ---

Created attachment 105329
  --> https://bugs.kde.org/attachment.cgi?id=105329=edit
emerge --info kate >> 0_emerge--info-kate.txt

Overview:
https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298620529

Description of Startup Procedure:
https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298611832

Observation of Patterns:
https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298374308

Please, let me know which further information would be helpful.

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

[QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus

[Eugene Shalygin]

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

--- Comment #66 from Eugene Shalygin  
---
https://bugreports.qt.io/browse/QTBUG-60558

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

[kdevelop] [Bug 341568] Support "::class" as of PHP 5.5

[Heinz Wiesinger]

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

Heinz Wiesinger  changed:

   What|Removed |Added

 CC||ppr...@liwjatan.at

--- Comment #1 from Heinz Wiesinger  ---
I think this was fixed with
https://cgit.kde.org/kdev-php.git/commit/?id=ff5a7d86a3f13634d000bf9efde3d1d4ef8e9326,
which was included in the 5.0.0 release

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

[Discover] [Bug 376910] Scrolling does not follow system settings

[Nate Graham]

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

--- Comment #10 from Nate Graham  ---
Still not fixed in discover 5.9.5 and kirigami 2.0.0-1.1.

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

[plasmashell] [Bug 378508] when remove panel applet plasma crashed

[RJ]

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

--- Comment #16 from RJ  ---
KDE 5.9.5 same bug here :/

#6  0x7f0271240754 in NotificationsApplet::onScreenChanges (this=0x42190e0)
at
/usr/src/debug/plasma-workspace-5.9.5/applets/notifications/lib/notificationsapplet.cpp:70


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

Thread 7 (Thread 0x7f0271c46700 (LWP 2343)):
#0  0x7f03330562a9 in g_mutex_lock (mutex=mutex@entry=0x7f026c000990) at
gthread-posix.c:1336
#1  0x7f033300ff99 in g_main_context_prepare
(context=context@entry=0x7f026c000990, priority=priority@entry=0x7f0271c45b70)
at gmain.c:3513
#2  0x7f03330109bb in g_main_context_iterate
(context=context@entry=0x7f026c000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3918
#3  0x7f0333010bac in g_main_context_iteration (context=0x7f026c000990,
may_block=may_block@entry=1) at gmain.c:3999
#4  0x7f0338b531bb in QEventDispatcherGlib::processEvents
(this=0x7f026c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f0338afcb1a in QEventLoop::exec (this=this@entry=0x7f0271c45cb0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f033892a813 in QThread::exec (this=) at
thread/qthread.cpp:507
#7  0x7f02744ffdf7 in KCupsConnection::run() () from
/usr/lib64/libkcupslib.so
#8  0x7f033892f4c8 in QThreadPrivate::start (arg=0x3890ba0) at
thread/qthread_unix.cpp:368
#9  0x7f03377e0537 in start_thread (arg=0x7f0271c46700) at
pthread_create.c:456
#10 0x7f033823a04f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 6 (Thread 0x7f02851fe700 (LWP 2332)):
#0  0x7f03330562a9 in g_mutex_lock (mutex=mutex@entry=0x7f028990) at
gthread-posix.c:1336
#1  0x7f033300fab4 in g_main_context_release (context=0x7f028990) at
gmain.c:3312
#2  0x7f0333010a4a in g_main_context_iterate
(context=context@entry=0x7f028990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3940
#3  0x7f0333010bac in g_main_context_iteration (context=0x7f028990,
may_block=may_block@entry=1) at gmain.c:3999
#4  0x7f0338b531bb in QEventDispatcherGlib::processEvents
(this=0x7f0288c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f0338afcb1a in QEventLoop::exec (this=this@entry=0x7f02851fdc80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f033892a813 in QThread::exec (this=this@entry=0x1273290) at
thread/qthread.cpp:507
#7  0x7f033c5ae2d6 in QQuickPixmapReader::run (this=0x1273290) at
/usr/src/debug/qtdeclarative-opensource-src-5.7.1/src/quick/util/qquickpixmapcache.cpp:822
#8  0x7f033892f4c8 in QThreadPrivate::start (arg=0x1273290) at
thread/qthread_unix.cpp:368
#9  0x7f03377e0537 in start_thread (arg=0x7f02851fe700) at
pthread_create.c:456
#10 0x7f033823a04f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 5 (Thread 0x7f03195d4700 (LWP 2326)):
#0  0x7f03377e69a6 in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f033e545fd8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x7f033e545f88,
cond=0x7f033e545fb0) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x7f033e545fb0, mutex=0x7f033e545f88) at
pthread_cond_wait.c:655
#3  0x7f033e24e974 in ?? () from /usr/lib64/libQt5Script.so.5
#4  0x7f033e24e9b9 in ?? () from /usr/lib64/libQt5Script.so.5
#5  0x7f03377e0537 in start_thread (arg=0x7f03195d4700) at
pthread_create.c:456
#6  0x7f033823a04f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 4 (Thread 0x7f031b3bd700 (LWP 2325)):
#0  0x7f033300da7c in g_source_iter_next (iter=iter@entry=0x7f031b3bcb10,
source=source@entry=0x7f031b3bcb08) at gmain.c:987
#1  0x7f033300ff2b in g_main_context_prepare
(context=context@entry=0x7f031990, priority=priority@entry=0x7f031b3bcb90)
at gmain.c:3488
#2  0x7f03330109bb in g_main_context_iterate
(context=context@entry=0x7f031990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3918
#3  0x7f0333010bac in g_main_context_iteration (context=0x7f031990,
may_block=may_block@entry=1) at gmain.c:3999
#4  0x7f0338b531bb in QEventDispatcherGlib::processEvents
(this=0x7f0318c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f0338afcb1a in QEventLoop::exec (this=this@entry=0x7f031b3bccd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f033892a813 in QThread::exec (this=this@entry=0xa04ca0) at
thread/qthread.cpp:507
#7  0x7f033ba1d305 in QQmlThreadPrivate::run (this=0xa04ca0) at
/usr/src/debug/qtdeclarative-opensource-src-5.7.1/src/qml/qml/ftw/qqmlthread.cpp:147
#8  

[Akonadi] [Bug 283682] KMail duplicates filtered messages

[bugzilla_noreply]

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

--- Comment #193 from gra...@howlingfrog.com ---
Agreed!  Exciting to see progress, as KMail is close to unusable at this point.

MUCH appreciated!

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

[QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus

[RJVB]

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

--- Comment #65 from RJVB  ---
OK, so that sounds like a regression in Qt, something you ought to report on
bugreports.qt.io .

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

[frameworks-baloo] [Bug 378750] Baloo crashes with clawsmain and other

[pkjdje]

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

--- Comment #4 from pkjdje  ---
Hi,
thought it useful if I sent another crash log,
I have had baloo crash several times since updating to Kubuntu 17.04
but only have 1 new file in /var/crash dated 3/5/17

I have attached it for your info.






On
Thu, 27 Apr 2017 11:34:13 + Christoph Feck
 wrote:

> https://bugs.kde.org/show_bug.cgi?id=378750
> 
> Christoph Feck  changed:
> 
>What|Removed |Added
> 
> Version|unspecified |5.31.0
>  Status|NEEDSINFO   |UNCONFIRMED
>  Resolution|BACKTRACE   |---
> 
> --- Comment #3 from Christoph Feck  ---
> Thanks for the update; changing status.
>

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

[kwin] [Bug 348569] KWin's timestamp mechanism isn't robust against bogus event times

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

  Flags||ReviewRequest+
URL||https://phabricator.kde.org
   ||/D5704

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

[kwin] [Bug 377901] Window movement breaks after 49 days

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

URL||https://phabricator.kde.org
   ||/D5704
  Flags||ReviewRequest+

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

[plasma-integration] [Bug 376395] libreoffice and the xorg-xserver-video-intel-native-modesetting

[Martin Gräßlin]

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

--- Comment #5 from Martin Gräßlin  ---
You reported this bug against Plasma-integration. Neither Neon, nor
libreoffice, nor the libreoffice-kde integration are developed by Plasma
developers. I'm sorry, you are wrong here.

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

[QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus

[Eugene Shalygin]

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

--- Comment #64 from Eugene Shalygin  
---
(In reply to RJVB from comment #63)
> And you don't get that crash without the patch?

With 5.9 it crashes under any conditions, albeit with different stack traces.

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

[QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus

[RJVB]

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

--- Comment #63 from RJVB  ---
And you don't get that crash without the patch?

See https://phabricator.kde.org/D5702 for a version which already moved the
unregisterCallback() call.

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

[elisa] [Bug 379487] New: Elisa doesn’t handle non-default font/display settings

[Karl Ove Hufthammer]

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

Bug ID: 379487
   Summary: Elisa doesn’t handle non-default font/display settings
   Product: elisa
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: k...@huftis.org
  Target Milestone: ---

Created attachment 105327
  --> https://bugs.kde.org/attachment.cgi?id=105327=edit
Screenshot showing layout problems in Elisa

Elisa doesn’t seem to handle non-default font/display settings properly. It’s a
bit difficult to explain the problem, so I’ll attach a screenshot showing how
Elisa looks on my system.

Here’s the problems I observe:

- Overlapping text
- Too small spacing between lines of text
- Inconsistent font size
- Parts of application window hidden (lower right part)
- Non-working widgets (because of overlapping text)

Note that I use a larger font size than the default. Other KDE applications
handle this fine, but Elisa doesn’t. (Perhaps due to pixel-based hardcoding of
element positions instead of letting Qt and its layout algorithms take care of
it?)

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

[QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus

[Eugene Shalygin]

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

--- Comment #62 from Eugene Shalygin  
---
Moved, but the stack trace is the same:

#6  0x7f9b4acea981 in QInternal::unregisterCallback(QInternal::Callback,
bool (*)(void**)) () from /usr/lib64/libQt5Core.so.5
#7  0x7f9b3a160364 in QtCurve::StylePlugin::~StylePlugin (this=0x21efe50,
__in_chrg=) at
/usr/src/debug/x11-themes/qtcurve-/qtcurve-/qt5/style/qtcurve_plugin.cpp:144
#8  0x7f9b3a1604e4 in QtCurve::StylePlugin::~StylePlugin (this=0x21efe50,
__in_chrg=) at
/usr/src/debug/x11-themes/qtcurve-/qtcurve-/qt5/style/qtcurve_plugin.cpp:159
#9  0x7f9b4ae84f11 in QLibraryPrivate::unload(QLibraryPrivate::UnloadFlag)
() from /usr/lib64/libQt5Core.so.5
#10 0x7f9b4ae7bb32 in QFactoryLoaderPrivate::~QFactoryLoaderPrivate() ()
from /usr/lib64/libQt5Core.so.5
#11 0x7f9b4ae7bc59 in QFactoryLoaderPrivate::~QFactoryLoaderPrivate() ()
from /usr/lib64/libQt5Core.so.5
#12 0x7f9b4aebb7c7 in QObject::~QObject() () from
/usr/lib64/libQt5Core.so.5
#13 0x7f9b4ae7b001 in QFactoryLoader::~QFactoryLoader() () from
/usr/lib64/libQt5Core.so.5
#14 0x7f9b4b7334b9 in (anonymous
namespace)::Q_QGS_loader::innerFunction()::Holder::~Holder() () from
/usr/lib64/libQt5Widgets.so.5
#15 0x7f9b49fea9e0 in __run_exit_handlers () from /lib64/libc.so.6
#16 0x7f9b49feaa3a in exit () from /lib64/libc.so.6
#17 0x7f9b4ada64b4 in QCommandLineParser::showHelp(int) () from
/usr/lib64/libQt5Core.so.5
#18 0x0040f9b1 in main ()

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

[Akonadi] [Bug 283682] KMail duplicates filtered messages

[Frits Spieker]

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

--- Comment #192 from Frits Spieker  ---
Excellent! Good to know there is some progress.

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

[QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus

[RJVB]

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

--- Comment #61 from RJVB  ---
That looks like it should be unrelated at least to the purpose of my patch.

There is a tiny possibility though that the event callback is called during
destruction, and that it obtains a stale pointer to the object's style. Could
you try moving the if with the unregisterCallback() call to immediately after
the qtcInfo call and report back, please?

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

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

[bugzilla_noreply]

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

--- Comment #6 from caulier.gil...@gmail.com ---
The tab view exists but are reduced to the minimum due to lack of icon on your
system.

Use Universal Linux AppImage instead. Current pre-version 5.6.0 is available
here :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[digikam] [Bug 379226] digiKam Properties Metadata not shown in Editor Captions

[bugzilla_noreply]

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

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

   What|Removed |Added

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

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

[digikam] [Bug 379226] digiKam Properties Metadata not shown in Editor Captions

[Geoff King]

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

--- Comment #2 from Geoff King  ---
Okay that fixed it.  Thanks.

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

[frameworks-kio] [Bug 379477] The file manager does not save file changes on the remote serve

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

   Assignee|dolphin-bugs-n...@kde.org   |fa...@kde.org
  Component|general |general
 CC||elvis.angelac...@kde.org,
   ||kdelibs-b...@kde.org
Product|dolphin |frameworks-kio
Version|17.04.0 |unspecified

--- Comment #1 from Elvis Angelaccio  ---
Can you try again making sure to have only ONE instance of Atom or VSCode or
Sublime running?

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

[plasma-integration] [Bug 376395] libreoffice and the xorg-xserver-video-intel-native-modesetting

[PK]

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

--- Comment #4 from PK  ---
I'm sorry for the very late reaction. I really don't think the kde-integration
of libreoffice could be the real guilty one.
I mean this started after neon switched to the new intel video driver
(native-modesetting). And that driver isn't at all developed by LibreOffice. I
tried to go back to the old video driver but that doesn't seem possible any
more.

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

[QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus

[Eugene Shalygin]

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

--- Comment #60 from Eugene Shalygin  
---
BTW, https://codereview.qt-project.org/180231 &
https://codereview.qt-project.org/180232 are applied too.

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

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

[Lukas Polacek]

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

Lukas Polacek  changed:

   What|Removed |Added

 CC||lu...@ksp.sk

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

[QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus

[Eugene Shalygin]

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

--- Comment #59 from Eugene Shalygin  
---
Latest version of QtCurve? Yes.

Thread 1 "kdialog" received signal SIGSEGV, Segmentation fault.
0x7235c981 in QInternal::unregisterCallback(QInternal::Callback, bool
(*)(void**)) () from /usr/lib64/libQt5Core.so.5
(gdb) bt
#0  0x7235c981 in QInternal::unregisterCallback(QInternal::Callback,
bool (*)(void**)) () from /usr/lib64/libQt5Core.so.5
#1  0x7fffe17ce489 in QtCurve::StylePlugin::~StylePlugin (this=0x680500,
__in_chrg=)
at
/usr/src/debug/x11-themes/qtcurve-/qtcurve-/qt5/style/qtcurve_plugin.cpp:153
#2  0x7fffe17ce4e4 in QtCurve::StylePlugin::~StylePlugin (this=0x680500,
__in_chrg=)
at
/usr/src/debug/x11-themes/qtcurve-/qtcurve-/qt5/style/qtcurve_plugin.cpp:159
#3  0x724f6f11 in QLibraryPrivate::unload(QLibraryPrivate::UnloadFlag)
() from /usr/lib64/libQt5Core.so.5
#4  0x724edb32 in QFactoryLoaderPrivate::~QFactoryLoaderPrivate() ()
from /usr/lib64/libQt5Core.so.5
#5  0x724edc59 in QFactoryLoaderPrivate::~QFactoryLoaderPrivate() ()
from /usr/lib64/libQt5Core.so.5
#6  0x7252d7c7 in QObject::~QObject() () from
/usr/lib64/libQt5Core.so.5
#7  0x724ed001 in QFactoryLoader::~QFactoryLoader() () from
/usr/lib64/libQt5Core.so.5
#8  0x72da54b9 in (anonymous
namespace)::Q_QGS_loader::innerFunction()::Holder::~Holder() () from
/usr/lib64/libQt5Widgets.so.5
#9  0x7165c9e0 in __run_exit_handlers () from /lib64/libc.so.6
#10 0x7165ca3a in exit () from /lib64/libc.so.6
#11 0x724184b4 in QCommandLineParser::showHelp(int) () from
/usr/lib64/libQt5Core.so.5
#12 0x0040f9b1 in main ()

This is from running `gdb kdialog`

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

[QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus

[RJVB]

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

--- Comment #58 from RJVB  ---
Quick reaction: are you using the latest version in git - if not, could you
please pull the latest version and rebuild with debug info so I can see how you
get into `unregisterCallback()`?

This is running `foo --help`?

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

[digikam] [Bug 379442] AppImage package does not find the files needed for panorama

[bugzilla_noreply]

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

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

   What|Removed |Added

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

--- Comment #3 from caulier.gil...@gmail.com ---
yes, Remote storage tool is disabled in AppImage. It fact KIO dependencies do
not work at run time. An alternative need to be found to replace it.

Q : Does Panorama tool work as expected to stitch images together ? Which Hugin
version do you use exactly ?

Gilles Caulier

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

[QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus

[Eugene Shalygin]

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

--- Comment #57 from Eugene Shalygin  
---
With the patch from comment 54 applied, it crashes with Qt 5.9.0 beta 3 with
the following stacktrace:

#6  0x7f42b7f24981 in QInternal::unregisterCallback(QInternal::Callback,
bool (*)(void**)) () from /usr/lib64/libQt5Core.so.5
#7  0x7f42a73bbdde in QtCurve::StylePlugin::~StylePlugin() () from
/usr/lib64/qt5/plugins/styles/qtcurve.so
#8  0x7f42a73bbe89 in QtCurve::StylePlugin::~StylePlugin() () from
/usr/lib64/qt5/plugins/styles/qtcurve.so
#9  0x7f42b80bef11 in QLibraryPrivate::unload(QLibraryPrivate::UnloadFlag)
() from /usr/lib64/libQt5Core.so.5
#10 0x7f42b80b5b32 in QFactoryLoaderPrivate::~QFactoryLoaderPrivate() ()
from /usr/lib64/libQt5Core.so.5
#11 0x7f42b80b5c59 in QFactoryLoaderPrivate::~QFactoryLoaderPrivate() ()
from /usr/lib64/libQt5Core.so.5
#12 0x7f42b80f57c7 in QObject::~QObject() () from
/usr/lib64/libQt5Core.so.5
#13 0x7f42b80b5001 in QFactoryLoader::~QFactoryLoader() () from
/usr/lib64/libQt5Core.so.5
#14 0x7f42b896d4b9 in (anonymous
namespace)::Q_QGS_loader::innerFunction()::Holder::~Holder() () from
/usr/lib64/libQt5Widgets.so.5
#15 0x7f42b72249e0 in __run_exit_handlers () from /lib64/libc.so.6
#16 0x7f42b7224a3a in exit () from /lib64/libc.so.6
#17 0x7f42b7fe04b4 in QCommandLineParser::showHelp(int) () from
/usr/lib64/libQt5Core.so.5
#18 0x0040f9b1 in main ()

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

[digikam] [Bug 379442] AppImage package does not find the files needed for panorama

[bugzilla_noreply]

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

--- Comment #2 from philippe.quag...@laposte.net ---
Yes, it works well. Many thanks !

The «export to remote folder» function has been removed until it works again ?
Is there another mean to copy an image to another folder ?
Best regards.

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

[konqueror] [Bug 379486] New: Konqueror UI is hard to use for people with limited eyesight.

[bugzilla_noreply]

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

Bug ID: 379486
   Summary: Konqueror UI is hard to use for people with limited
eyesight.
   Product: konqueror
   Version: 5.0.97
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: konq-b...@kde.org
  Reporter: r03...@gmail.com
  Target Milestone: ---

Hello,

I am not the one experiencing the problem, but there was a user (who wished to
not submit a report themselves) that was having trouble using the newest
version of Konquerer due to UI changes and poor eyesight.

2. The menu shows no icons, only text; buttons like open new tab/close
current tab show no icons, making difficult to guess.

<...>

7. Konqueror Introduction page, no icons; unless I hover over them, 
hyperlinked titles shown in dark grey over a blue background.  I know my 
eye sight is not as good as it used to be, but this is really akin to 
usability sabotage.

This was, of course, accompanied by other complaints, but I feel this issue is
important enough to take out of context for submission to this tracker.

If I had to guess I think the issue stems from the adoption, knowingly or
unknowingly, of what is now called "material design"*. While I quite like most
interfaces produced using design guidelines that one could say are material
design please take note that it is very very easy to produce incomprehensible
UIs following Google's guidelines (and Google has done some of this).



* Material design actually existed for a number of years before Google started
using it under that name. It was "created" by FOSS projects who didn't have any
artists that decided to draw colored rectangles with text in them.

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

[Akonadi] [Bug 283682] KMail duplicates filtered messages

[Martin Koller]

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

--- Comment #191 from Martin Koller  ---
I am currently looking into this and have already implemented some patches
which hopefully improve the situation (although I have no final fix yet).
E.g. https://phabricator.kde.org/D5667
It's very complicated and has to do with timing of messages between 3 processes
...

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

[valgrind] [Bug 378931] Add ISA 3.0B additional isnstructions, add OV32, CA32 setting support

[Carl Love]

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

Carl Love  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from Carl Love  ---
Attached patch was committed,  Vex commit 3359
The test case result files, test case changes are in Valgrind commit 16329

There is a lot of changes to the test case outputs.  I think it is all fine but
will leave this Bug open until I verify the regression tests are OK.

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

[Akonadi] [Bug 283682] KMail duplicates filtered messages

[Frits Spieker]

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

--- Comment #190 from Frits Spieker  ---
But is one of the developers actually looking at this? The duplication of the
messages, combined with the akonadi hanging itself out to dry when deleting
messages (resulting in the famous "retrieving folder content" screen) makes
KMail basically unusable. I'm really baffled how such a crucial piece of
software (unless developers use other program to read email) can be so broken
for so long.

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

[KScreen] [Bug 379485] New: infinit switch

[bugzilla_noreply]

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

Bug ID: 379485
   Summary: infinit switch
   Product: KScreen
   Version: 5.9.5
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: common
  Assignee: se...@kde.org
  Reporter: t...@tuor.org
  Target Milestone: ---

Created attachment 105326
  --> https://bugs.kde.org/attachment.cgi?id=105326=edit
printf "[Rules]\nkscreen.*=true" >> ~/.config/QtProject/qtlogging.ini;
kscreen-console bug > $(tempfile)

Hi Folks

I'm running KDE Neon 5.9 (current version, all up to date).

Symptom:
Infinit wwitching of Display configurations. It does just switch and switch and
switch an so on. It just don't stop.

When does it occure?
Most of the time when I just connected a new screen. But sometimtes when i
unlock my screen. For example I'm off wokring for 30 minutes, come back, unlock
the screen and it happens.
It ONLY happens, when I have a secondary screen connected.

Workaround:
reboot! After a reboot all is fine again.

How often?
Today 3 Times! Other days never. From time to time it just happens randomly.
Like 2 times a week.

Pleas tell me if I can do something to get this bug solved!

Salutations
Aaron

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

[kile] [Bug 379435] The settings menu mising kile config item

[Jonathan Verner]

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

--- Comment #1 from Jonathan Verner  ---
I have more info: Although the Configure Keyboard Shortcuts menu entry is also
missing, I can assign a global shortcut to this action in systemsettings. Then, 
I use this shortcut to open the config in kile and assign a shortcut to the
settings dialog. However, the settings dialog does not open even after
activating it via this new keyboard shortcut.

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

[ktorrent] [Bug 379483] ktorrent PID: 5740 Señal: Segmentation fault

[bugzilla_noreply]

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

--- Comment #1 from ernestopereslo...@yahoo.es ---
Application: KTorrent (ktorrent), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb69f7da840 (LWP 6449))]

Thread 8 (Thread 0x7fb60700 (LWP 6487)):
#0  0x7fb694d48756 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fb69a3d958b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7fb69f0e6388 in ?? () from /usr/lib/libktorrent.so.6
#3  0x7fb69a3d86d8 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7fb694d422e7 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7fb6997b754f in clone () from /usr/lib/libc.so.6

Thread 7 (Thread 0x7fb624ff9700 (LWP 6484)):
#0  0x7fb6997b2889 in syscall () from /usr/lib/libc.so.6
#1  0x7fb69a3cf865 in QBasicMutex::lockInternal() () from
/usr/lib/libQt5Core.so.5
#2  0x7fb69a3cf922 in QMutex::lock() () from /usr/lib/libQt5Core.so.5
#3  0x7fb69f0e2d3c in ?? () from /usr/lib/libktorrent.so.6
#4  0x7fb69f0e3589 in ?? () from /usr/lib/libktorrent.so.6
#5  0x7fb69a3d86d8 in ?? () from /usr/lib/libQt5Core.so.5
#6  0x7fb694d422e7 in start_thread () from /usr/lib/libpthread.so.0
#7  0x7fb6997b754f in clone () from /usr/lib/libc.so.6

Thread 6 (Thread 0x7fb6257fa700 (LWP 6483)):
[KCrash Handler]
#6  0x7fb69a459ecc in QString::indexOf(QChar, int, Qt::CaseSensitivity)
const () from /usr/lib/libQt5Core.so.5
#7  0x7fb69f126f66 in ?? () from /usr/lib/libktorrent.so.6
#8  0x7fb69f127d94 in ?? () from /usr/lib/libktorrent.so.6
#9  0x7fb69f125508 in ?? () from /usr/lib/libktorrent.so.6
#10 0x7fb69f1262a3 in ?? () from /usr/lib/libktorrent.so.6
#11 0x7fb69f0e887f in ?? () from /usr/lib/libktorrent.so.6
#12 0x7fb69f0e4a24 in ?? () from /usr/lib/libktorrent.so.6
#13 0x7fb69f0e39ca in ?? () from /usr/lib/libktorrent.so.6
#14 0x7fb69f0e3551 in ?? () from /usr/lib/libktorrent.so.6
#15 0x7fb69f0e3589 in ?? () from /usr/lib/libktorrent.so.6
#16 0x7fb69a3d86d8 in ?? () from /usr/lib/libQt5Core.so.5
#17 0x7fb694d422e7 in start_thread () from /usr/lib/libpthread.so.0
#18 0x7fb6997b754f in clone () from /usr/lib/libc.so.6

Thread 5 (Thread 0x7fb66dc52700 (LWP 6456)):
#0  0x7fb694d48ca6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fb66fd06e44 in ?? () from /usr/lib/libGLX_nvidia.so.0
#2  0x7fb66ea1e394 in ?? () from /usr/lib/libnvidia-glcore.so.378.13
#3  0x7fb66fd0612c in ?? () from /usr/lib/libGLX_nvidia.so.0
#4  0x7fb694d422e7 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7fb6997b754f in clone () from /usr/lib/libc.so.6

Thread 4 (Thread 0x7fb682ab2700 (LWP 6454)):
#0  0x7fb69a60785e in ?? () from /usr/lib/libQt5Core.so.5
#1  0x7fb692724e8d in g_main_context_prepare () from
/usr/lib/libglib-2.0.so.0
#2  0x7fb6927258db in ?? () from /usr/lib/libglib-2.0.so.0
#3  0x7fb692725acc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#4  0x7fb69a60809b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#5  0x7fb69a5b18ca in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#6  0x7fb69a3d3a73 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#7  0x7fb69a3d86d8 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7fb694d422e7 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7fb6997b754f in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7fb6822a2700 (LWP 6453)):
#0  0x7fb6997ad67d in poll () from /usr/lib/libc.so.6
#1  0x7fb6927259b6 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fb692725acc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fb69a60809b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7fb69a5b18ca in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7fb69a3d3a73 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7fb69a3d86d8 in ?? () from /usr/lib/libQt5Core.so.5
#7  0x7fb694d422e7 in start_thread () from /usr/lib/libpthread.so.0
#8  0x7fb6997b754f in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7fb6832da700 (LWP 6451)):
#0  0x7fb69276b1c9 in g_mutex_lock () from /usr/lib/libglib-2.0.so.0
#1  0x7fb6927249b4 in g_main_context_release () from
/usr/lib/libglib-2.0.so.0
#2  0x7fb69272596a in ?? () from /usr/lib/libglib-2.0.so.0
#3  0x7fb692725acc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#4  0x7fb69a60809b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#5  0x7fb69a5b18ca in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#6  0x7fb69a3d3a73 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#7  0x7fb698d11125 in ?? () from /usr/lib/libQt5DBus.so.5
#8  0x7fb69a3d86d8 in ?? () from 

[kdevelop] [Bug 379484] New: KDevelop disregards target property OUTPUT_NAME

[Alexander Potashev]

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

Bug ID: 379484
   Summary: KDevelop disregards target property OUTPUT_NAME
   Product: kdevelop
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Build tools: CMake
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: aspotas...@gmail.com
  Target Milestone: ---

KDevelop disregards target property OUTPUT_NAME when auto-detecting executable
path for launch configuration.

Steps to reproduce:

1. Create a cmake target (e.g. "abc"); set its property OUTPUT_NAME to
something else, e.g. "xyz_binary":

set_property(TARGET abc PROPERTY OUTPUT_NAME "xyz_binary")

2. Go to Run -> Run Configurations...

3. Use the "Add" drop-down to add a run configuration for the target "abc".

4. Press Shift+F9 to run the target.

Actual results: it tries to run "abc" which does not exist.

Expected results: run "xyz_binary".

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

[ktorrent] [Bug 379483] New: ktorrent PID: 5740 Señal: Segmentation fault

[bugzilla_noreply]

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

Bug ID: 379483
   Summary: ktorrent PID: 5740 Señal: Segmentation fault
   Product: ktorrent
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: joris.guis...@gmail.com
  Reporter: ernestopereslo...@yahoo.es
  Target Milestone: ---

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

Thread 10 (Thread 0x7f9b0d7fa700 (LWP 5789)):
#0  0x7f9b66308b63 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f9b6b9994c6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f9b6b994bc4 in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7f9b6b9986d8 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7f9b663022e7 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7f9b6ad7754f in clone () from /usr/lib/libc.so.6

Thread 9 (Thread 0x7f9b0700 (LWP 5786)):
#0  0x7f9b66308b63 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f9b6b9994c6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f9b6b994bc4 in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7f9b6b9986d8 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7f9b663022e7 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7f9b6ad7754f in clone () from /usr/lib/libc.so.6

Thread 8 (Thread 0x7f9aed7fa700 (LWP 5780)):
#0  0x7f9b66308756 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f9b6b99958b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f9b706a6388 in ?? () from /usr/lib/libktorrent.so.6
#3  0x7f9b6b9986d8 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7f9b663022e7 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7f9b6ad7754f in clone () from /usr/lib/libc.so.6

Thread 7 (Thread 0x7f9aedffb700 (LWP 5778)):
#0  0x7f9b6ad72889 in syscall () from /usr/lib/libc.so.6
#1  0x7f9b6b98f865 in QBasicMutex::lockInternal() () from
/usr/lib/libQt5Core.so.5
#2  0x7f9b6b98f922 in QMutex::lock() () from /usr/lib/libQt5Core.so.5
#3  0x7f9b706a2d3c in ?? () from /usr/lib/libktorrent.so.6
#4  0x7f9b706a3589 in ?? () from /usr/lib/libktorrent.so.6
#5  0x7f9b6b9986d8 in ?? () from /usr/lib/libQt5Core.so.5
#6  0x7f9b663022e7 in start_thread () from /usr/lib/libpthread.so.0
#7  0x7f9b6ad7754f in clone () from /usr/lib/libc.so.6

Thread 6 (Thread 0x7f9aee7fc700 (LWP 5777)):
[KCrash Handler]
#6  0x7f9b6ba13fd4 in ?? () from /usr/lib/libQt5Core.so.5
#7  0x7f9b706e6f66 in ?? () from /usr/lib/libktorrent.so.6
#8  0x7f9b706e7d94 in ?? () from /usr/lib/libktorrent.so.6
#9  0x7f9b706e5508 in ?? () from /usr/lib/libktorrent.so.6
#10 0x7f9b706e62a3 in ?? () from /usr/lib/libktorrent.so.6
#11 0x7f9b706a887f in ?? () from /usr/lib/libktorrent.so.6
#12 0x7f9b706a4a24 in ?? () from /usr/lib/libktorrent.so.6
#13 0x7f9b706a39ca in ?? () from /usr/lib/libktorrent.so.6
#14 0x7f9b706a3551 in ?? () from /usr/lib/libktorrent.so.6
#15 0x7f9b706a3589 in ?? () from /usr/lib/libktorrent.so.6
#16 0x7f9b6b9986d8 in ?? () from /usr/lib/libQt5Core.so.5
#17 0x7f9b663022e7 in start_thread () from /usr/lib/libpthread.so.0
#18 0x7f9b6ad7754f in clone () from /usr/lib/libc.so.6

Thread 5 (Thread 0x7f9b44f9a700 (LWP 5748)):
#0  0x7f9b66308ca6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f9b4704ee44 in ?? () from /usr/lib/libGLX_nvidia.so.0
#2  0x7f9b45d66394 in ?? () from /usr/lib/libnvidia-glcore.so.378.13
#3  0x7f9b4704e12c in ?? () from /usr/lib/libGLX_nvidia.so.0
#4  0x7f9b663022e7 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7f9b6ad7754f in clone () from /usr/lib/libc.so.6

Thread 4 (Thread 0x7f9b53fff700 (LWP 5745)):
#0  0x7fffdcda5939 in ?? ()
#1  0x7fffdcda5bc5 in clock_gettime ()
#2  0x7f9b6ad84826 in clock_gettime () from /usr/lib/libc.so.6
#3  0x7f9b6bbc7231 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7f9b6bbc59f9 in QTimerInfoList::updateCurrentTime() () from
/usr/lib/libQt5Core.so.5
#5  0x7f9b6bbc5fa5 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib/libQt5Core.so.5
#6  0x7f9b6bbc7904 in ?? () from /usr/lib/libQt5Core.so.5
#7  0x7f9b63ce4e8d in g_main_context_prepare () from
/usr/lib/libglib-2.0.so.0
#8  0x7f9b63ce58db in ?? () from /usr/lib/libglib-2.0.so.0
#9  0x7f9b63ce5acc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#10 0x7f9b6bbc809b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#11 0x7f9b6bb718ca in

[kwin] [Bug 378679] Intel modeseting drive intense tear with Skylake CPUs

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #3 from Christoph Feck  ---
To further investigate this issue, KDE developers need the information
requested in comment #1. If you can provide it, or need help with finding that
information, please add a comment.

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

[kwin] [Bug 379472] Kwin crashes when attempting to start session.

[bugzilla_noreply]

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

--- Comment #3 from kishor...@gmail.com ---
On further digging, I found that this happens when I'm using qt 5.9 beta 3.
Using qt 5.8, the wayland session launches normally.

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

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

[John]

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

--- Comment #5 from John  ---
I'm running Digikam 5.4 (build 4:5.4.0-0ubuntu3, the distribution's version)
with Ubuntu 17.04 x64 (upgrade) and the problem has returned. 

https://www.flickr.com/photos/39126243@N03/34045069610/in/dateposted-public/

Only the GeoLocations sidebar is shown - can I get the Settings sidebar to
display on the Import window with this version?

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

[kwin] [Bug 379472] Kwin crashes when attempting to start session.

[bugzilla_noreply]

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

--- Comment #2 from kishor...@gmail.com ---
(In reply to Martin Gräßlin from comment #1)
> Given the information we have from it: do
> you have the KWin QPA plugin installed to the correct location so that Qt
> finds it?

How can I check if I have it? I'm not sure if this is related, but when I type
'kwin_wayland --version', I get the following output:

kwin_wayland --version
This application failed to start because it could not find or load the Qt
platform plugin "wayland-org.kde.kwin.qpa"
in "".

Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs, linuxfb,
minimal, minimalegl, offscreen, vnc, wayland-egl, wayland,
wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

Reinstalling the application may fix this problem.
fish: “kwin_wayland --version” terminated by signal SIGABRT (Abort)

However, typing 'kwin_x11 --version' gives just the application name and
version number as expected.

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

[Heaptrack] [Bug 379082] Unit tests are failing in Debian Stretch (9)

[Milian Wolff]

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

Milian Wolff  changed:

   What|Removed |Added

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

--- Comment #1 from Milian Wolff  ---
commit 3ddc8ba3c751436fddd2969ba349a76ab6b7f8d1
Author: Milian Wolff 
Date:   Wed May 3 17:35:18 2017 +0200

Filter zero frames from the end of the stack returned by libunwind

Some (older) versions of libunwind eratically return zero frames
at the end of the stack. This happened on Debian and Ubuntu with the
distro provided libunwind. In such situations, we now skip these
uninteresting frames.

BUG: 379082

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

[krita] [Bug 379482] Krita does not recognize touch input on Windows 10 TrekStore SurfTab twin 11.6

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

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

--- Comment #1 from Boudewijn Rempt  ---


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

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

[krita] [Bug 368179] Freehand brush tool does not support touch screen painting

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||m.pat...@hotmail.de

--- Comment #4 from Boudewijn Rempt  ---
*** Bug 379482 has been marked as a duplicate of this bug. ***

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

[krita] [Bug 379482] New: Krita does not recognize touch input on Windows 10 TrekStore SurfTab twin 11.6

[bugzilla_noreply]

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

Bug ID: 379482
   Summary: Krita does not recognize touch input on Windows 10
TrekStore SurfTab twin 11.6
   Product: krita
   Version: 3.1.3
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: task
  Priority: NOR
 Component: tablet support
  Assignee: krita-bugs-n...@kde.org
  Reporter: m.pat...@hotmail.de
  Target Milestone: ---

Created attachment 105325
  --> https://bugs.kde.org/attachment.cgi?id=105325=edit
Mouse movemend between line 56 and 174, Line 101 and 103 mousebutton: both
"Blocked"

Krita doesen't move the Cursor on the painting-screen.
Other Actions work.

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

[kmail2] [Bug 379476] Renaming attachments should also change their Content-Disposition/filename attribute

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
 CC||mon...@kde.org

--- Comment #1 from Laurent Montel  ---
It's already fixed in 5.5.0

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

[kwin] [Bug 379472] Kwin crashes when attempting to start session.

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---
Unfortuntely the debug symbols for Qt are missing and it crashes directly when
creating the QApplication. Given the information we have from it: do you have
the KWin QPA plugin installed to the correct location so that Qt finds it?

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

[kwin] [Bug 363224] Kwin crashes from time to time (this time using Virtual Machine Manager)

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

 CC||aaroncdcalc...@gmail.com

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

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

[kwin] [Bug 379480] Random kWin crashes

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---


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

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

[kwin] [Bug 379465] kwin_x11 crashes after mpv is set to fullscreen

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---
As always for arch users the backtrace is completely useless as it's missing
debug symbols. Nothing we can do.

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

[gwenview] [Bug 170124] set as wallpaper option

[Dr . Chapatin]

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

Dr. Chapatin  changed:

   What|Removed |Added

 CC||yy...@gmx.com

--- Comment #20 from Dr. Chapatin  ---
Almost nine years later and this feature is still missing...
Dear devs, give us this useful feature please.

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

[kmenuedit] [Bug 379481] New: would like ability to manually sort menu items

[bugzilla_noreply]

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

Bug ID: 379481
   Summary: would like ability to manually sort menu items
   Product: kmenuedit
   Version: 5.9.5
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: wizard10...@gmail.com
  Target Milestone: ---

Wishlist item - I use the classic desktop menu in Plasma 5.9.5 and would like
the ability to manually sort the applications I stick in this menu.

For example, dolphin comes up first on the menu even though I'd prefer it was
google-chrome and shutdown is in the bottom third of the application list
although I'd really like to have it at the bottom.

Coming from fluxbox and openbox my workflow is kinda used to having my top ten
applications on a right-click menu in the order I specify.  Can we add an
option to manually sort these items if the user doesn't want to sort by name or
description?

Thank you -

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

[Breeze] [Bug 369676] White lockscreen text's readability depends on background

[Rog131]

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

--- Comment #5 from Rog131  ---
Dublicate / same kind of as Bug 374300 - Option to change the font color on the
lock screen - https://bugs.kde.org/show_bug.cgi?id=374300

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

[Breeze] [Bug 374300] Option to change the font color on the lock screen

[Rog131]

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

Rog131  changed:

   What|Removed |Added

 CC||samrog...@hotmail.com

--- Comment #3 from Rog131  ---
Dublicate / same kind of as Bug 369676 - White lockscreen text's readability
depends on background - https://bugs.kde.org/show_bug.cgi?id=369676

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

[kwin] [Bug 379480] New: Random kWin crashes

[Aarón CdC]

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

Bug ID: 379480
   Summary: Random kWin crashes
   Product: kwin
   Version: 5.9.4
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: aaroncdcalc...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.9.4)

Qt Version: 5.7.1
Frameworks Version: 5.31.0
Operating System: Linux 4.10.0-20-generic x86_64
Distribution: Ubuntu 17.04

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

Setting up a virtual machine using Oracle Virtual Box version 5.1.18 (Just
closed the virtual machine Settings window by clicking OK). The error
reproduces constantly whenever I do the same thing.

- Unusual behavior I noticed:

This error also happens when I'm using Gwenview, sometimes  when I start it,
other times when I move or resize the window, but it's not constant. The whole
desktop restarts, and the windows move around a bit when it starts again.

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa5f76f5980 (LWP 1808))]

Thread 6 (Thread 0x7fa5cacb9700 (LWP 2258)):
#0  0x7fa5f0828510 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa5f47cab4b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fa5efc59495 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#3  0x7fa5efc59d8a in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7fa5f47c9c98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa5f08226da in start_thread (arg=0x7fa5cacb9700) at
pthread_create.c:456
#6  0x7fa5f712e17f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 5 (Thread 0x7fa5bb5ef700 (LWP 1968)):
#0  0x7fa5f7122251 in __GI_ppoll (fds=0x7fa5b4000ae8, nfds=1,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x7fa5f49e9251 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fa5f49eab4a in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7fa5f499788a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa5f47c4fe3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa5ef58fdf5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x7fa5f47c9c98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa5f08226da in start_thread (arg=0x7fa5bb5ef700) at
pthread_create.c:456
#8  0x7fa5f712e17f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 4 (Thread 0x7fa5ba604700 (LWP 1914)):
#0  0x7fa5f0828510 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa5f3b532c4 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7fa5f3b53309 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7fa5f08226da in start_thread (arg=0x7fa5ba604700) at
pthread_create.c:456
#4  0x7fa5f712e17f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 3 (Thread 0x7fa5c97f3700 (LWP 1906)):
#0  0x7fa5f7122251 in __GI_ppoll (fds=0x7fa5cae8, nfds=1,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x7fa5f49e9251 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fa5f49eab4a in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7fa5f499788a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa5f47c4fe3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa5ef58fdf5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x7fa5f47c9c98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa5f08226da in start_thread (arg=0x7fa5c97f3700) at
pthread_create.c:456
#8  0x7fa5f712e17f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7fa5db833700 (LWP 1821)):
#0  0x7fa5f712218d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa5ebd4c576 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa5ebd4c68c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa5f49edf2b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa5f499788a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa5f47c4fe3 in QThread::exec() () at

[dolphin] [Bug 357542] [Feature request] Working "Recently used files / folders"

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[kmail2] [Bug 379479] New: Frequent crashes with kmail in Ubuntu 17.04 (updated kmail)

[Anders Bolager]

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

Bug ID: 379479
   Summary: Frequent crashes with kmail in Ubuntu 17.04 (updated
kmail)
   Product: kmail2
   Version: 5.4.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: and...@bolager.com
  Target Milestone: ---

Application: kmail (5.4.3)

Qt Version: 5.7.1
Frameworks Version: 5.31.0
Operating System: Linux 4.10.0-20-generic x86_64
Distribution: Ubuntu 17.04

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

Almost always when selecting a message to view, the program crash. At the
longest, I managed to work in it (watching messages, even sending one) for
about 20 minutes or so. Usually, it crash right after startup.

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f093d633b80 (LWP 3388))]

Thread 27 (Thread 0x7f086b9c1700 (LWP 3452)):
#0  0x7f09301f4510 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f09208582c4 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f0920858309 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f09301ee6da in start_thread (arg=0x7f086b9c1700) at
pthread_create.c:456
#4  0x7f093a5b217f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 26 (Thread 0x7f08719c0700 (LWP 3440)):
#0  0x7f093a5a618d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f092e421576 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f092e42168c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f093b0e0f2b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f093b08a88a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f093aeb7fe3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f093aebcc98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f09301ee6da in start_thread (arg=0x7f08719c0700) at
pthread_create.c:456
#8  0x7f093a5b217f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 25 (Thread 0x7f0896ffd700 (LWP 3420)):
#0  0x7f09301f4510 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0925b1dc09 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#2  0x7f0925b1e209 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#3  0x7f0925b1e3c0 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f0925b1ad5c in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f09301ee6da in start_thread (arg=0x7f0896ffd700) at
pthread_create.c:456
#6  0x7f093a5b217f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 24 (Thread 0x7f08977fe700 (LWP 3419)):
#0  0x7f093a5a1cad in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f0912b7c611 in pa_read () at
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so
#2  0x7f091bdec21e in pa_mainloop_prepare () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x7f091bdecc90 in pa_mainloop_iterate () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7f091bdecd50 in pa_mainloop_run () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7f091bdfad39 in  () at /usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7f0912bab7d8 in  () at
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so
#7  0x7f09301ee6da in start_thread (arg=0x7f08977fe700) at
pthread_create.c:456
#8  0x7f093a5b217f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 23 (Thread 0x7f0897fff700 (LWP 3418)):
#0  0x7f093a5c013c in __lll_lock_wait_private () at
../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95
#1  0x7f093a5c1d44 in ___fprintf_chk (fp=0x7f093a86d750
<_IO_stdfile_2_lock>, flag=1, format=0x7f0918b737b4 "[%s] %s\n") at
fprintf_chk.c:30
#2  0x7f0918b5b51e in  () at /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5
#3  0x7f0918b5b714 in event_warn () at
/usr/lib/x86_64-linux-gnu/libevent-2.0.so.5
#4  0x7f0918b5fd38 in  () at /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5
#5  0x7f0918b49efa in event_base_loop () at
/usr/lib/x86_64-linux-gnu/libevent-2.0.so.5
#6  0x7f0925ac92aa in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f0925b05a84 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7f0925aef9d5 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7f0925b1e9ea in  () at

[Discover] [Bug 379478] New: Plasma Discover Crash on search

[Steve Davis]

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

Bug ID: 379478
   Summary: Plasma Discover Crash on search
   Product: Discover
   Version: 5.9.5
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: t.m.inbox...@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.9.5)

Qt Version: 5.7.1
Frameworks Version: 5.33.0
Operating System: Linux 4.8.0-51-generic x86_64
Distribution: KDE neon User Edition 5.9

-- Information about the crash:
- What I was doing when the application crashed:
any time i perfrome a second search in Plasma Discover or press the backspace
key in search box

The crash can be reproduced every time.

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7efdf61078c0 (LWP 6149))]

Thread 9 (Thread 0x7efd7a7fc700 (LWP 7808)):
#0  QMutex::lock (this=this@entry=0x1bbd0e0) at thread/qmutex.cpp:225
#1  0x7efdf305f029 in QMutexLocker::QMutexLocker (m=0x1bbd0e0,
this=) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:137
#2  QThreadData::canWaitLocked (this=0x1bbd0b0) at
../../include/QtCore/5.7.1/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:253
#3  postEventSourcePrepare (timeout=, s=0x7efd64001810) at
kernel/qeventdispatcher_glib.cpp:259
#4  postEventSourceCheck (source=0x7efd64001810) at
kernel/qeventdispatcher_glib.cpp:269
#5  0x7efded80bdc1 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7efded80c330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7efded80c49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7efdf305f75b in QEventDispatcherGlib::processEvents
(this=0x7efd64002230, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#9  0x7efdf300a0ba in QEventLoop::exec (this=this@entry=0x7efd7a7fbd00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#10 0x7efdf2e39f64 in QThread::exec (this=) at
thread/qthread.cpp:507
#11 0x7efdf2e3eb48 in QThreadPrivate::start (arg=0x54849a0) at
thread/qthread_unix.cpp:368
#12 0x7efdef8c76ba in start_thread (arg=0x7efd7a7fc700) at
pthread_create.c:333
#13 0x7efdf244282d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7efd98ff9700 (LWP 7802)):
#0  0x7efded850a79 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7efded80c34e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7efded80c49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7efdf305f75b in QEventDispatcherGlib::processEvents
(this=0x7efd80001c90, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7efdf300a0ba in QEventLoop::exec (this=this@entry=0x7efd98ff8d00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7efdf2e39f64 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7efdf2e3eb48 in QThreadPrivate::start (arg=0x2792e00) at
thread/qthread_unix.cpp:368
#7  0x7efdef8c76ba in start_thread (arg=0x7efd98ff9700) at
pthread_create.c:333
#8  0x7efdf244282d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7efdbf7fe700 (LWP 6159)):
#0  0x7efded850a94 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7efded80b9a0 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7efded80c2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7efded80c49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7efdf305f75b in QEventDispatcherGlib::processEvents
(this=0x7efdac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7efdf300a0ba in QEventLoop::exec (this=this@entry=0x7efdbf7fdd00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7efdf2e39f64 in QThread::exec (this=) at
thread/qthread.cpp:507
#7  0x7efdf2e3eb48 in QThreadPrivate::start (arg=0x2a8e0a0) at
thread/qthread_unix.cpp:368
#8  0x7efdef8c76ba in start_thread (arg=0x7efdbf7fe700) at
pthread_create.c:333
#9  0x7efdf244282d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7efdc5ec1700 (LWP 6156)):
#0  0x7efdf2436b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7efded80c38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7efded80c49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7efdf305f75b in QEventDispatcherGlib::processEvents
(this=0x7efdc8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7efdf300a0ba in QEventLoop::exec (this=this@entry=0x7efdc5ec0d00,
flags=..., flags@entry=...) at 

[libkface] [Bug 377425] libkface FTBFS against opencv-3.2.0

[Rex Dieter]

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

--- Comment #2 from Rex Dieter  ---
Re-confimed with 17.04.0 release (and master/ branch which as of now, has no
relevant commits beyond v17.04.0 tag as far as I can tell)

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

[Breeze] [Bug 374300] Option to change the font color on the lock screen

[bugzilla_noreply]

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

kishor...@gmail.com changed:

   What|Removed |Added

 CC||kishor...@gmail.com

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

[QtCurve] [Bug 379354] Control and shift conquer

[Hamid]

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

--- Comment #5 from Hamid  ---
For anyone's reference, there was a conflict between the keyboard layout change
mechanism (Ctrl + Shift) and the normal use of these keys in applications.
Changed the keyboard layout change sequence to something else and the symptom
is gone. Still it shouldn't interfere, it worked fine in Kubuntu 16.10 and
before.

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

[KScreen] [Bug 379474] KScreen wakes up the monitor right after going to sleep

[David Rosca]

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

--- Comment #1 from David Rosca  ---
The issue is when monitor is turned off, KScreen emits output disconnected and
KScreenDaemon::outputConnectedChanged reapplies config which turns the monitor
back on.
I'm not sure what would be correct fix, my workaround is to query DPMS state in
KScreenDaemon::outputConnectedChanged and if DPMS state is off, skip the
reconfiguration.

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

[dolphin] [Bug 379477] New: The file manager does not save file changes on the remote serve

[Alex]

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

Bug ID: 379477
   Summary: The file manager does not save file changes on the
remote serve
   Product: dolphin
   Version: 17.04.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: kozackunis...@gmail.com
  Target Milestone: ---

I opened the remote directory
sftp://root@myHostIP:22/fileToEdit

And I tried to edit the file. "Open with ..." of different editors

Atom (1.16.0-1)
A local copy of the file was created.
After the file was modified nothing happened.
After the editor was closed, a dialogue appeared to load the local copy of the
file to the remote server.

Visual Studio Code (1.11.2-1)
A local copy of the file was created.
After the file was modified nothing happened.
After the editor was closed nothing happened.

Sublime Text (3.3126-1)
A local copy of the file was created.
After the file was modified nothing happened.
After the editor was closed nothing happened.

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

[QtCurve] [Bug 379354] Control and shift conquer

[Hamid]

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

Hamid  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |INVALID

--- Comment #4 from Hamid  ---
The active widget style is Breeze. Then I should file this bug somewhere else
regarding keyboard input.

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

[kdev-python] [Bug 378827] Kevelop 4.7, 5.0.x, and 5.1.0 crashes when background parsing is turned on for Unreal Engine 4

[Francis Herne]

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

--- Comment #10 from Francis Herne  ---
Correction, it's related to the use of MacOS Classic (why?!) line endings -
i.e. just a carriage return but no newline.

Many places in kdev-python assume that lines can be split with \n, so we should
probably normalise these earlier.

Alternative patch that solves this particular case:


diff --git a/parser/astbuilder.cpp b/parser/astbuilder.cpp
index 0e19f367..15df40a9 100644
--- a/parser/astbuilder.cpp
+++ b/parser/astbuilder.cpp
@@ -98,7 +98,8 @@ private:
 class RangeFixVisitor : public AstDefaultVisitor {
 public:
 RangeFixVisitor(const QString& contents)
-: lines(contents.split('\n')) { };
+// Split on all three variants - \r, \n or \r\n
+: lines(contents.split(QRegExp("\\r\\n?|\\n"))) { };

 void visitNode(Ast* node) override {
 AstDefaultVisitor::visitNode(node);

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

[plasma-nm] [Bug 350521] [RFE] [OpenVPN] kdeplasma-applets-plasma-nm does not support OTP Tokens for OpenVPN connections

[vst]

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

--- Comment #6 from vst  ---
Unfortunately I cannot test this now, because I don't have access to an
OTP-enabled OpenVPN server.

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

[kmail2] [Bug 379476] New: Renaming attachments should also change their Content-Disposition/filename attribute

[Gunter Ohrner]

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

Bug ID: 379476
   Summary: Renaming attachments should also change their
Content-Disposition/filename attribute
   Product: kmail2
   Version: 5.4.3
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: composer
  Assignee: kdepim-b...@kde.org
  Reporter: kdeb...@customcdrom.de
  Target Milestone: ---

1) Attach a file to a message.
2) Right-click the attachment, choose Properties and change the attachment's
name.

Result: The "Content-Type" "name" attribute is changed, as follows:

Content-Type: application/pdf; name="new_name.pdf"

The "Content-Disposition" "filename" attribute stays unchanged, though:

Content-Disposition: attachment; filename="orig_name.pdf"


Somewhat counter-intuitive, this will in most cases cause the attachment to be
called "orig_name.pdf" on the receiver's side, not "new_name.pdf" as one might
expect when using the properties dialog.

By default, the name and filename attributes are set to the same values by
kMail, as far as I can see.

Either the "name" field should change both values, or there should be a
separate "File Name" property.

Maybe interesting in this regard:

https://mailarchive.ietf.org/arch/msg/ietf-smtp/KtN0TdoHDayKvKycNbsFD-GB-e4#

Wishlist item Bug #311179 may be related.

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