[Heaptrack] [Bug 386923] heaptrack stalls forever in LineReader::getLine

2017-11-16 Thread Giuseppe Bilotta
https://bugs.kde.org/show_bug.cgi?id=386923

--- Comment #6 from Giuseppe Bilotta  ---
Thanks for the extensive tracking, Milian, I'll find sometime later today to
try the latest git master of heaptrack.

FWIW, I do have the Intel platform available, but I can reproduce the deadlock
by limiting the available platforms to just the Mesa one (using ocl-icd for
libOpenCL and setting OCL_ICD_VENDORS so that only Mesa is found), so I don't
thin Intel's TBB would be at fault in my case. Maybe Mesa does its own alloc
meddling? I'm using mesa 17.2.4-1+b1 packaged in Debian sid.

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

[LabPlot2] [Bug 387017] function override warnings in column/Column.h and core/AbstractColumn.h

2017-11-16 Thread Alexander Semke
https://bugs.kde.org/show_bug.cgi?id=387017

Alexander Semke  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/lab
   ||plot/b026e35cbebd399871d8cf
   ||b015dbc1cb58a761a9
 Resolution|--- |FIXED

--- Comment #1 from Alexander Semke  ---
Git commit b026e35cbebd399871d8cfb015dbc1cb58a761a9 by Alexander Semke.
Committed on 17/11/2017 at 07:49.
Pushed by asemke into branch 'master'.

Removed unneeded const's in the overridden functions in Column.
FIX-IN: 2.5

M  +18   -17   src/backend/core/column/Column.h

https://commits.kde.org/labplot/b026e35cbebd399871d8cfb015dbc1cb58a761a9

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

[krita] [Bug 387023] Krita crashes, lags, and freezes often.

2017-11-16 Thread Boudewijn Rempt
https://bugs.kde.org/show_bug.cgi?id=387023

Boudewijn Rempt  changed:

   What|Removed |Added

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

--- Comment #1 from Boudewijn Rempt  ---
Well, it does sound like your system is messed up. It's impossible to figure
out what's up from a distance, but have you got any "security" software other
than that what comes with Windows installed? Total Defender or Sandboxie or
something like that?

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

[kile] [Bug 387024] New: manually update live preview and separate it from editor

2017-11-16 Thread Stas
https://bugs.kde.org/show_bug.cgi?id=387024

Bug ID: 387024
   Summary: manually update live preview and separate it from
editor
   Product: kile
   Version: 2.9.91
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: michel.lud...@kdemail.net
  Reporter: stas.kaz...@googlemail.com
  Target Milestone: ---

1. It would be great to have an option to update live preview only manually but
still show it all the time. While writing I often save my document after each
sentence (just to be sure everything is saved when a crash happens, it is an
old automatic behavior ;) ) but I do not want to compile my live preview each
time I save a document. Often it is even a bad idea to compile after saving
only one file (e. g. when I have a text file where I need a new command which I
want to declare in the preamble). So adding a shortcut or a button for live
preview while disable it on saving would be rely convenient.

2. It is related to the first part. How about make a temporary copy of the
actual project and compile from that. In this way one could save a file and
continue typing while the live preview will update to the saved version. For
now the live preview just breaks when a file is modified while compiling. This
feature could also solve the first problem I mentioned.

Thanks for such great software.

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

[krita] [Bug 360601] [INTEL] Various issues caused by buggy Intel drivers.

2017-11-16 Thread Boudewijn Rempt
https://bugs.kde.org/show_bug.cgi?id=360601

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||elliotuk2...@gmail.com

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

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

[krita] [Bug 387003] slow

2017-11-16 Thread Boudewijn Rempt
https://bugs.kde.org/show_bug.cgi?id=387003

Boudewijn Rempt  changed:

   What|Removed |Added

   Platform|Windows CE  |MS Windows
 Status|UNCONFIRMED |RESOLVED
 OS|Windows CE  |MS Windows
  Component|general |OpenGL Canvas
 Resolution|--- |DUPLICATE
 CC||b...@valdyas.org

--- Comment #1 from Boudewijn Rempt  ---
Sounds like:

https://docs.krita.org/KritaFAQ#Krita_starts_with_a_black_or_blank_canvas_and_nothing_changes_when_you_try_to_draw.2Fshows_a_black_or_blank_screen_on_my_Windows_system_with_an_Intel_GPU

Please paste the output of help/system information for bug reports into a
comment on this bug _before_ you apply the remedy from the FAQ.

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

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

[amarok] [Bug 386765] missing information

2017-11-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=386765

--- Comment #4 from altodr...@gmail.com ---
Yes the track is from local collection.

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

[frameworks-kwindowsystem] [Bug 387012] Failing tests in master

2017-11-16 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=387012

--- Comment #1 from Martin Flöser  ---
Please report to Qt that there are runtime regressions.

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

[frameworks-kguiaddons] [Bug 365894] KMail(2) documentation not available

2017-11-16 Thread Burkhard Lueck
https://bugs.kde.org/show_bug.cgi?id=365894

--- Comment #2 from Burkhard Lueck  ---
Ubuntu 17.10 kmail2  5.5.3 KDE Frameworks 5.39.0  Qt 5.9.1 
Using F1 or Help->KMail Handbook opens the documentation properly

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

[krita] [Bug 387023] New: Krita crashes, lags, and freezes often.

2017-11-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=387023

Bug ID: 387023
   Summary: Krita crashes, lags, and freezes often.
   Product: krita
   Version: 3.3.2
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: thepaleher...@gmail.com
  Target Milestone: ---

I notice that when I work with multiple images, within and without the same
document, that Krita freezes and crashes. 

There are also times that my brush freezes while I am drawing. The only way to
'unstick' it is to move the cursor off the canvas and over one of the docks. It
happens rather frequently.

I also experience lag at seemingly random times.

I use a Huion 610Pro tablet and have an Intel i3 Core (unfortunately) but I
have run the program as administrator and even done a clean reinstall. Help?

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

[kmenuedit] [Bug 387022] Deleting hidden application entries does not delete them

2017-11-16 Thread Nicholas Estrada
https://bugs.kde.org/show_bug.cgi?id=387022

Nicholas Estrada <116ni...@gmail.com> changed:

   What|Removed |Added

 CC||116ni...@gmail.com

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

[kmenuedit] [Bug 387022] New: Deleting hidden application entries does not delete them

2017-11-16 Thread Nicholas Estrada
https://bugs.kde.org/show_bug.cgi?id=387022

Bug ID: 387022
   Summary: Deleting hidden application entries does not delete
them
   Product: kmenuedit
   Version: 5.11.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: 116ni...@gmail.com
  Target Milestone: ---

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

I delete the entries, then save, but they don't stay deleted. Screenshot
attached shows what exactly I'm talking about.

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

[krita] [Bug 386927] Brush first draws a straight line

2017-11-16 Thread Azher Krimson
https://bugs.kde.org/show_bug.cgi?id=386927

--- Comment #7 from Azher Krimson  ---
(In reply to Alvin Wong from comment #6)
> What if you disable "Canvas Graphics Acceleration" in configure
> krita->display? Or change renderer to ANGLE?

Both fixes tried, not working :/

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

[tellico] [Bug 386548] The ID field now includes an icon in 3.1 compared to 3.0.2

2017-11-16 Thread Robby Stephenson
https://bugs.kde.org/show_bug.cgi?id=386548

--- Comment #2 from Robby Stephenson  ---
Git commit 9ba3c5ad2bb830614a954edb8b6a701b25863aa0 by Robby Stephenson.
Committed on 17/11/2017 at 01:56.
Pushed by rstephenson into branch 'master'.

Improve EntryIconModel to act more as proxy for EntryModel for images

Add a new data role to designate the primary image for an entry. Break
out the image request for the model into a separate method so multiple
places can use it.

Also, use an icon for the EntryModel instead of a pixmap which solves
problems of weirdly big images in the tree view.

M  +2-2src/collection.cpp
M  +1-1src/collection.h
M  +0-1src/mainwindow.cpp
M  +14   -19   src/models/entryiconmodel.cpp
M  +38   -13   src/models/entrymodel.cpp
M  +1-0src/models/entrymodel.h
M  +2-1src/models/models.h

https://commits.kde.org/tellico/9ba3c5ad2bb830614a954edb8b6a701b25863aa0

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

[kdevelop] [Bug 387021] New: instance hangs after session selection

2017-11-16 Thread Eli MacKenzie
https://bugs.kde.org/show_bug.cgi?id=387021

Bug ID: 387021
   Summary: instance hangs after session selection
   Product: kdevelop
   Version: 5.1.1
  Platform: RedHat RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Session support
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: argo...@gmail.com
  Target Milestone: ---

I've a `kdevelop --ps` launcher. Somewhat often, I'll find an instance of
kdevelop using one full core, even after all sessions have been quit.

backtrace:

#0  0x7fd2396ccf8a in KDevelop::Bucket::followerIndex(unsigned short)
const (index=0, this=0x7fd1d81524d0)
at /usr/src/debug/kdevplatform-5.1.1/serialization/itemrepository.h:941
#1  0x7fd2396ccf8a in KDevelop::Bucket::deleteItem >(unsigned short,
unsigned int, KDevelop::ItemRepository&) (repository=...,
hash=, index=14586, this=0x7fd1d81524d0)
at /usr/src/debug/kdevplatform-5.1.1/serialization/itemrepository.h:547
#2  0x7fd2396ccf8a in KDevelop::Bucket::finalCleanup
>(KDevelop::ItemRepository&) (repository=...,
this=) at
/usr/src/debug/kdevplatform-5.1.1/serialization/itemrepository.h:677
#3  0x7fd2396ccf8a in KDevelop::ItemRepository::finalCleanup()
(this=)
at /usr/src/debug/kdevplatform-5.1.1/serialization/itemrepository.h:2074
#4  0x7fd2380468a1 in KDevelop::ItemRepositoryRegistry::finalCleanup()
(this=) at
/usr/src/debug/kdevplatform-5.1.1/serialization/itemrepositoryregistry.cpp:366
#5  0x7fd239606149 in KDevelop::finalCleanup () at
/usr/src/debug/kdevplatform-5.1.1/language/duchain/duchain.cpp:1585
#6  0x7fd239606149 in KDevelop::DUChain::shutdown() (this=)
at /usr/src/debug/kdevplatform-5.1.1/language/duchain/duchain.cpp:1623
#7  0x7fd241a7c988 in KDevelop::Core::cleanup()
(this=this@entry=0x562e0c59b980) at
/usr/src/debug/kdevplatform-5.1.1/shell/core.cpp:461
#8  0x7fd241a7cc08 in KDevelop::Core::shutdown() (this=0x562e0c59b980) at
/usr/src/debug/kdevplatform-5.1.1/shell/core.cpp:412
#9  0x7fd241a5c70d in KDevelop::MainWindow::~MainWindow()
(this=this@entry=0x562e0c4a5fa0, __in_chrg=,
__vtt_parm=) at
/usr/src/debug/kdevplatform-5.1.1/shell/mainwindow.cpp:158
#10 0x7fd241a5c769 in KDevelop::MainWindow::~MainWindow()
(this=0x562e0c4a5fa0, __in_chrg=, __vtt_parm=) at
/usr/src/debug/kdevplatform-5.1.1/shell/mainwindow.cpp:162
#11 0x7fd23c2fa8f8 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#12 0x7fd23cb640db in QWidget::event(QEvent*) () at
/lib64/libQt5Widgets.so.5
#13 0x7fd23cc5df2b in QMainWindow::event(QEvent*) () at
/lib64/libQt5Widgets.so.5
#14 0x7fd23f9bca57 in KMainWindow::event(QEvent*) () at
/lib64/libKF5XmlGui.so.5
#15 0x7fd23fa01a65 in KXmlGuiWindow::event(QEvent*) () at
/lib64/libKF5XmlGui.so.5
#16 0x7fd23cb1d5dc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#17 0x7fd23cb24c74 in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQt5Widgets.so.5
#18 0x7fd23c2d2627 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#19 0x7fd23c2d485b in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /lib64/libQt5Core.so.5
#20 0x7fd23c320dd3 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQt5Core.so.5
#21 0x7fd22e42d247 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#22 0x7fd22e42d5e8 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#23 0x7fd22e42d67c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#24 0x7fd23c320e4f in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#25 0x7fd23c2d160a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#26 0x7fd23c2d927c in QCoreApplication::exec() () at /lib64/libQt5Core.so.5
#27 0x562e0b89f2a7 in main(int, char**) (argc=,
argv=) at /usr/src/debug/kdevelop-5.1.1/app/main.cpp:763

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

[k3b] [Bug 387020] New: Remove unnecessary line break from copyright bar

2017-11-16 Thread Dr . Chapatin
https://bugs.kde.org/show_bug.cgi?id=387020

Bug ID: 387020
   Summary: Remove unnecessary line break from copyright bar
   Product: k3b
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: GUI/Usability
  Assignee: k...@kde.org
  Reporter: bugsefor...@gmx.com
CC: mich...@jabster.pl, tr...@kde.org
  Target Milestone: ---

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

It's just a detail, but can you remove the line break after "k3b" please?
Thanks.

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

[krita] [Bug 386625] Problem when merging layers

2017-11-16 Thread Daniel Aragao
https://bugs.kde.org/show_bug.cgi?id=386625

Daniel Aragao  changed:

   What|Removed |Added

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

--- Comment #4 from Daniel Aragao  ---
Still with no solution.

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

[kdevelop] [Bug 372686] KDevelop random crash during edit [clang_Cursor_getParsedComment]

2017-11-16 Thread Sven Brauch
https://bugs.kde.org/show_bug.cgi?id=372686

Sven Brauch  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
   Version Fixed In||5.2.1
  Latest Commit||https://commits.kde.org/kde
   ||velop/a2712c8d9691375545f50
   ||2c10f4f76fa10452e90
 Resolution|--- |FIXED

--- Comment #8 from Sven Brauch  ---
Git commit a2712c8d9691375545f502c10f4f76fa10452e90 by Sven Brauch.
Committed on 17/11/2017 at 00:45.
Pushed by brauch into branch '5.2'.

work around clang bug 35333: don't crash when switching git branches

See https://bugs.llvm.org/show_bug.cgi?id=35333 for details and
explanation.

We need to do two things to work around this bug: disable -Wdocumentation,
and only use the plain text from the comments instead of the parsed
version.

REVIEW: https://phabricator.kde.org/D8857
Related: bug 358205
FIXED-IN: 5.2.1

M  +4-0plugins/clang/duchain/builder.cpp
M  +7-0plugins/clang/duchain/parsesession.cpp

https://commits.kde.org/kdevelop/a2712c8d9691375545f502c10f4f76fa10452e90

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

[kdevelop] [Bug 358205] crash in clang_Cursor_getParsedComment

2017-11-16 Thread Sven Brauch
https://bugs.kde.org/show_bug.cgi?id=358205

Sven Brauch  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kde
   ||velop/a2712c8d9691375545f50
   ||2c10f4f76fa10452e90
   Version Fixed In||5.2.1
 Resolution|UPSTREAM|FIXED

--- Comment #6 from Sven Brauch  ---
Git commit a2712c8d9691375545f502c10f4f76fa10452e90 by Sven Brauch.
Committed on 17/11/2017 at 00:45.
Pushed by brauch into branch '5.2'.

work around clang bug 35333: don't crash when switching git branches

See https://bugs.llvm.org/show_bug.cgi?id=35333 for details and
explanation.

We need to do two things to work around this bug: disable -Wdocumentation,
and only use the plain text from the comments instead of the parsed
version.

REVIEW: https://phabricator.kde.org/D8857
Related: bug 372686
FIXED-IN: 5.2.1

M  +4-0plugins/clang/duchain/builder.cpp
M  +7-0plugins/clang/duchain/parsesession.cpp

https://commits.kde.org/kdevelop/a2712c8d9691375545f502c10f4f76fa10452e90

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

[plasmashell] [Bug 387019] New: Plasma shell crash - plasmoids

2017-11-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=387019

Bug ID: 387019
   Summary: Plasma shell crash - plasmoids
   Product: plasmashell
   Version: 5.11.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: function.esc...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.11.3)

Qt Version: 5.9.2
Frameworks Version: 5.40.0
Operating System: Linux 4.13.12-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
I was trying to remove the "Device Notifier" plasmoid from the desktop.

- Unusual behavior I noticed:
When I right-clicked and chose the "remove" option, the desktop went black. The
plasmoid then appeared again at the top left corner of my desktop.

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

Thread 6 (Thread 0x7f1cc1158700 (LWP 1938)):
#0  0x7f1d721fdf7b in poll () at /usr/lib/libc.so.6
#1  0x7f1d6caf4ed3 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f1d6caf4fae in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f1d72b3bcf4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f1d72adf48b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f1d728f827e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f1d7661929b in  () at /usr/lib/libQt5Quick.so.5
#7  0x7f1d728fcfcb in  () at /usr/lib/libQt5Core.so.5
#8  0x7f1d71ab508a in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f1d7220847f in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f1d5239b700 (LWP 1934)):
#0  0x7f1d71abb38d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f1d78342ef7 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f1d78342f39 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f1d71ab508a in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f1d7220847f in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f1d53fff700 (LWP 1933)):
#0  0x7f1d721fdf7b in poll () at /usr/lib/libc.so.6
#1  0x7f1d6caf4ed3 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f1d6caf4fae in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f1d72b3bcf4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f1d72adf48b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f1d728f827e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f1d75a6cc09 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f1d728fcfcb in  () at /usr/lib/libQt5Core.so.5
#8  0x7f1d71ab508a in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f1d7220847f in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f1d5a9e0700 (LWP 1932)):
#0  0x7f1d721f9a98 in read () at /usr/lib/libc.so.6
#1  0x7f1d6cb1c521 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f1d6caf390b in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7f1d6caf4e76 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7f1d6caf4fae in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7f1d72b3bcf4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7f1d72adf48b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7f1d728f827e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7f1d75a6cc09 in  () at /usr/lib/libQt5Qml.so.5
#9  0x7f1d728fcfcb in  () at /usr/lib/libQt5Core.so.5
#10 0x7f1d71ab508a in start_thread () at /usr/lib/libpthread.so.0
#11 0x7f1d7220847f in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f1d5bfff700 (LWP 1931)):
#0  0x7f1d721fdf7b in poll () at /usr/lib/libc.so.6
#1  0x7f1d6caf4ed3 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f1d6caf4fae in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f1d72b3bcf4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f1d72adf48b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f1d728f827e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f1d72f57376 in  () at /usr/lib/libQt5DBus.so.5
#7  0x7f1d728fcfcb in  () at /usr/lib/libQt5Core.so.5
#8  0x7f1d71ab508a in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f1d7220847f in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f1d78c86800 (LWP 1929)):
[KCrash Handler]
#5  0x7f1d581b3c40 in  ()
#6  0x7f1d759222f7 in
QV4::PersistentValueStorage::mark(QV4::ExecutionEngine*) () at
/usr/lib/libQt5Qml.so.5
#7  0x7f1d758319f0 in QV4::MemoryManager::mark() () at

[kmail2] [Bug 387018] New: Crashed while adding a To-Do item

2017-11-16 Thread Arnfinn
https://bugs.kde.org/show_bug.cgi?id=387018

Bug ID: 387018
   Summary: Crashed while adding a To-Do item
   Product: kmail2
   Version: 5.5.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: eiel...@fastmail.fm
  Target Milestone: ---

Application: kmail (5.5.2)

Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.4.92-31-default x86_64
Distribution: "openSUSE Leap 42.3"

-- Information about the crash:
Just started using KMail, added an account, then went on to try to add a To-Do
list item. KMail was syncing 'Sent Items' while I was doing this. Crashed when
when hitting 'Finish' or equivalent to add To-Do item.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f673ea2e940 (LWP 20229))]

Thread 24 (Thread 0x7f65d2fa2700 (LWP 20325)):
#0  0x7f67318f40bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f6728d375d9 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f6728d37d9d in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f6728d385c0 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f6728d3531e in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f67318ef744 in start_thread () at /lib64/libpthread.so.0
#6  0x7f673bb7daad in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7f6657fff700 (LWP 20317)):
#0  0x7f67318f40bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f672454f93b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f672454f969 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f67318ef744 in start_thread () at /lib64/libpthread.so.0
#4  0x7f673bb7daad in clone () at /lib64/libc.so.6

Thread 22 (Thread 0x7f66937fd700 (LWP 20275)):
#0  0x7f67318f40bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f6728b93160 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f6728b80c0b in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f6728b80e85 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f6728b7d777 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f672a327a4a in  () at /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7f672a327d61 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7f672a327e52 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#8  0x7f6728d21062 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#9  0x7f6728d0cb05 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#10 0x7f6728d38940 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#11 0x7f6728d3531e in  () at /usr/lib64/libQt5WebEngineCore.so.5
#12 0x7f67318ef744 in start_thread () at /lib64/libpthread.so.0
#13 0x7f673bb7daad in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7f6693ffe700 (LWP 20274)):
#0  0x7f67318f40bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f6728d375d9 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f6728d37d9d in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f6728d385c0 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f6728d3531e in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f67318ef744 in start_thread () at /lib64/libpthread.so.0
#6  0x7f673bb7daad in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7f66b8ff9700 (LWP 20273)):
#0  0x7f673bb7520d in poll () at /lib64/libc.so.6
#1  0x7f672138f0a1 in  () at /usr/lib64/libpulse.so.0
#2  0x7f672138076c in pa_mainloop_poll () at /usr/lib64/libpulse.so.0
#3  0x7f6721380dde in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0
#4  0x7f6721380e90 in pa_mainloop_run () at /usr/lib64/libpulse.so.0
#5  0x7f672138f006 in  () at /usr/lib64/libpulse.so.0
#6  0x7f671a855408 in  () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so
#7  0x7f67318ef744 in start_thread () at /lib64/libpthread.so.0
#8  0x7f673bb7daad in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7f66b97fa700 (LWP 20272)):
#0  0x7f67318f40bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f6728d2e10f in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f6728d2e1e4 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f6728d10a7b in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f6728d21062 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f6728d0cb05 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7f6728d38940 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7f6728d3531e in  () at /usr/lib64/libQt5WebEngineCore.so.5
#8  0x7f67318ef744 in start_thread () at /lib64/libpthread.so.0
#9  0x7f673bb7daad in clone () at /lib64/libc.so.6

Thread 18 (Thread 0x7f66b9ffb700 (LWP 20271)):
#0  0x7f67318f40bf in 

[amarok] [Bug 386894] Amarok crashes upon start

2017-11-16 Thread Myriam Schweingruber
https://bugs.kde.org/show_bug.cgi?id=386894

Myriam Schweingruber  changed:

   What|Removed |Added

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

--- Comment #1 from Myriam Schweingruber  ---
Unfortunately your backtrace doesn't have debugging symbols for amarok. please
install those for Amarok and its dependencies (e.g. Phonon and its backends as
well as kdelibs and provide a new backtrace. See also
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

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

[amarok] [Bug 386765] missing information

2017-11-16 Thread Myriam Schweingruber
https://bugs.kde.org/show_bug.cgi?id=386765

Myriam Schweingruber  changed:

   What|Removed |Added

   Platform|Other   |Kubuntu Packages

--- Comment #3 from Myriam Schweingruber  ---
Since we didn't change anything on our side in that code, I fear it is caused
by either the theme or Plasma. I presume these tracks are part of your local
collection, aren't they?

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

[kdevelop] [Bug 386857] next window shortcut picks a random tab

2017-11-16 Thread LtWorf
https://bugs.kde.org/show_bug.cgi?id=386857

--- Comment #4 from Salvo "LtWorf" Tomaselli  ---
What do you mean by that?

I did change the default shortcut for those menu entries…

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

[kmymoney] [Bug 351892] online banking passwords not stored/remembered

2017-11-16 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=351892

--- Comment #7 from Ralf Habacker  ---
(In reply to Ralf Habacker from comment #6)
> Add ofx test web service to www.kmymoney.org
> 
Service does not work on public kde server - filed a sysadmin request
https://phabricator.kde.org/T7461

Assigning an ofx online account using this service running on a local host with
kmymoney 4.8.1 on Windows 10 showed that the passwords is indeed saved in the
kmymoney file.

Unfortunally this does not explain why the passwords are lost on an update to
Windows 10.

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

[Heaptrack] [Bug 386923] heaptrack stalls forever in LineReader::getLine

2017-11-16 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=386923

--- Comment #5 from Milian Wolff  ---
@Giuseppe: If possible, please compile heaptrack from current git master and
enable extended log output by setting s_debugVerbosity in libheaptrack.cpp to:

constexpr const DebugVerbosity s_debugVerbosity = VeryVerboseOutput;

I cannot figure out how your deadlock could arise. It does look like all
threads except the main thread are blocked in free(), but it's unclear which
thread is holding the lock :-/ It shouldn't be any of them, looking at the
code...

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

[kdevelop] [Bug 386857] next window shortcut picks a random tab

2017-11-16 Thread Kevin Funk
https://bugs.kde.org/show_bug.cgi?id=386857

--- Comment #3 from Kevin Funk  ---
I can't reproduce that here, even after shuffling around some tabs.

Do you have a more complex setup maybe?

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

[LabPlot2] [Bug 387017] New: function override warnings in column/Column.h and core/AbstractColumn.h

2017-11-16 Thread Uwe Stöhr
https://bugs.kde.org/show_bug.cgi?id=387017

Bug ID: 387017
   Summary: function override warnings in column/Column.h and
core/AbstractColumn.h
   Product: LabPlot2
   Version: latest
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: backend
  Assignee: alexander.se...@web.de
  Reporter: uwesto...@web.de
  Target Milestone: ---

I get:

2>C:\CraftRoot\labplot\src\backend/core/column/Column.h(80): warning C4373:
'Column::formula': virtual function overrides 'AbstractColumn::formula',
previous versions of the compiler did not override when parameters only
differed by const/volatile qualifiers
2>  C:\CraftRoot\labplot\src\backend/core/AbstractColumn.h(166): note: see
declaration of 'AbstractColumn::formula'
2>C:\CraftRoot\labplot\src\backend/core/column/Column.h(89): warning C4373:
'Column::textAt': virtual function overrides 'AbstractColumn::textAt', previous
versions of the compiler did not override when parameters only differed by
const/volatile qualifiers
2>  C:\CraftRoot\labplot\src\backend/core/AbstractColumn.h(172): note: see
declaration of 'AbstractColumn::textAt'
2>C:\CraftRoot\labplot\src\backend/core/column/Column.h(90): warning C4373:
'Column::setTextAt': virtual function overrides 'AbstractColumn::setTextAt',
previous versions of the compiler did not override when parameters only
differed by const/volatile qualifiers
2>  C:\CraftRoot\labplot\src\backend/core/AbstractColumn.h(173): note: see
declaration of 'AbstractColumn::setTextAt'
2>C:\CraftRoot\labplot\src\backend/core/column/Column.h(91): warning C4373:
'Column::replaceTexts': virtual function overrides
'AbstractColumn::replaceTexts', previous versions of the compiler did not
override when parameters only differed by const/volatile qualifiers
2>  C:\CraftRoot\labplot\src\backend/core/AbstractColumn.h(174): note: see
declaration of 'AbstractColumn::replaceTexts'
2>C:\CraftRoot\labplot\src\backend/core/column/Column.h(92): warning C4373:
'Column::dateAt': virtual function overrides 'AbstractColumn::dateAt', previous
versions of the compiler did not override when parameters only differed by
const/volatile qualifiers
2>  C:\CraftRoot\labplot\src\backend/core/AbstractColumn.h(175): note: see
declaration of 'AbstractColumn::dateAt'
2>C:\CraftRoot\labplot\src\backend/core/column/Column.h(93): warning C4373:
'Column::setDateAt': virtual function overrides 'AbstractColumn::setDateAt',
previous versions of the compiler did not override when parameters only
differed by const/volatile qualifiers
2>  C:\CraftRoot\labplot\src\backend/core/AbstractColumn.h(176): note: see
declaration of 'AbstractColumn::setDateAt'
2>C:\CraftRoot\labplot\src\backend/core/column/Column.h(94): warning C4373:
'Column::timeAt': virtual function overrides 'AbstractColumn::timeAt', previous
versions of the compiler did not override when parameters only differed by
const/volatile qualifiers
2>  C:\CraftRoot\labplot\src\backend/core/AbstractColumn.h(177): note: see
declaration of 'AbstractColumn::timeAt'
2>C:\CraftRoot\labplot\src\backend/core/column/Column.h(95): warning C4373:
'Column::setTimeAt': virtual function overrides 'AbstractColumn::setTimeAt',
previous versions of the compiler did not override when parameters only
differed by const/volatile qualifiers
2>  C:\CraftRoot\labplot\src\backend/core/AbstractColumn.h(178): note: see
declaration of 'AbstractColumn::setTimeAt'
2>C:\CraftRoot\labplot\src\backend/core/column/Column.h(96): warning C4373:
'Column::dateTimeAt': virtual function overrides 'AbstractColumn::dateTimeAt',
previous versions of the compiler did not override when parameters only
differed by const/volatile qualifiers
2>  C:\CraftRoot\labplot\src\backend/core/AbstractColumn.h(179): note: see
declaration of 'AbstractColumn::dateTimeAt'
2>C:\CraftRoot\labplot\src\backend/core/column/Column.h(97): warning C4373:
'Column::setDateTimeAt': virtual function overrides
'AbstractColumn::setDateTimeAt', previous versions of the compiler did not
override when parameters only differed by const/volatile qualifiers
2>  C:\CraftRoot\labplot\src\backend/core/AbstractColumn.h(180): note: see
declaration of 'AbstractColumn::setDateTimeAt'
2>C:\CraftRoot\labplot\src\backend/core/column/Column.h(98): warning C4373:
'Column::replaceDateTimes': virtual function overrides
'AbstractColumn::replaceDateTimes', previous versions of the compiler did not
override when parameters only differed by const/volatile qualifiers
2>  C:\CraftRoot\labplot\src\backend/core/AbstractColumn.h(181): note: see
declaration of 'AbstractColumn::replaceDateTimes'
2>C:\CraftRoot\labplot\src\backend/core/column/Column.h(99): warning C4373:
'Column::valueAt': virtual function overrides 'AbstractColumn::valueAt',
previous versions of the compiler did not override when parameters only
differed by const/volatile qualifiers
2>  

[Heaptrack] [Bug 386923] heaptrack stalls forever in LineReader::getLine

2017-11-16 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=386923

--- Comment #4 from Milian Wolff  ---
Also works fine with the NVidia backend which I could actually use on my
machine:

$ primusrun heaptrack clinfo
heaptrack output will be written to "/home/milian/heaptrack.clinfo.2262.gz"
starting application, this might take some time...
Number of platforms   1
  Platform Name   NVIDIA CUDA
  Platform Vendor NVIDIA Corporation
  Platform VersionOpenCL 1.2 CUDA 9.1.75
  Platform ProfileFULL_PROFILE
  Platform Extensions
cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics
cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64
cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing
cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll
cl_nv_copy_opts cl_nv_create_buffer
  Platform Extensions function suffix NV

  Platform Name   NVIDIA CUDA
Number of devices 1
  Device Name GeForce 940M
  Device Vendor   NVIDIA Corporation
  Device Vendor ID0x10de
  Device Version  OpenCL 1.2 CUDA
  Driver Version  387.22
  Device OpenCL C Version OpenCL C 1.2 
  Device Type GPU
  Device AvailableYes
  Device Profile  FULL_PROFILE
  Device Topology (NV)PCI-E, 04:00.0
  Max compute units   3
  Max clock frequency 980MHz
  Compute Capability (NV) 5.0
  Device Partition(core)
Max number of sub-devices 1
Supported partition types None
  Max work item dimensions3
  Max work item sizes 1024x1024x64
  Max work group size 1024
  Compiler Available  Yes
  Linker AvailableYes
  Preferred work group size multiple  32
  Warp size (NV)  32
  Preferred / native vector sizes 
char 1 / 1   
short1 / 1   
int  1 / 1   
long 1 / 1   
half 0 / 0(n/a)
float1 / 1   
double   1 / 1   
(cl_khr_fp64)
  Half-precision Floating-point support   (n/a)
  Single-precision Floating-point support (core)
Denormals Yes
Infinity and NANs Yes
Round to nearest  Yes
Round to zero Yes
Round to infinity Yes
IEEE754-2008 fused multiply-add   Yes
Support is emulated in software   No
Correctly-rounded divide and sqrt operations  Yes
  Double-precision Floating-point support (cl_khr_fp64)
Denormals Yes
Infinity and NANs Yes
Round to nearest  Yes
Round to zero Yes
Round to infinity Yes
IEEE754-2008 fused multiply-add   Yes
Support is emulated in software   No
Correctly-rounded divide and sqrt operations  No
  Address bits64, Little-Endian
  Global memory size  1029832704 (982.1MiB)
  Error Correction supportNo
  Max memory allocation   257458176 (245.5MiB)
  Unified memory for Host and Device  No
  Integrated memory (NV)  No
  Minimum alignment for any data type 128 bytes
  Alignment of base address   4096 bits (512 bytes)
  Global Memory cache typeRead/Write
  Global Memory cache size49152 (48KiB)
  Global Memory cache line128 bytes
  Image support   Yes
Max number of samplers per kernel 32
Max size for 1D images from buffer134217728 pixels
Max 1D or 2D image 

[LabPlot2] [Bug 387016] New: macro redefinition warning

2017-11-16 Thread Uwe Stöhr
https://bugs.kde.org/show_bug.cgi?id=387016

Bug ID: 387016
   Summary: macro redefinition warning
   Product: LabPlot2
   Version: latest
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: backend
  Assignee: alexander.se...@web.de
  Reporter: uwesto...@web.de
  Target Milestone: ---

I get.

2>C:\CraftRoot\labplot\src\backend/lib/macros.h(39): warning C4005: 'WARNING':
macro redefinition
2>  C:\CraftRoot\include\kdewin_export.h(84): note: see previous definition of
'WARNING'

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

[LabPlot2] [Bug 387015] implicitly defined as deleted warnings in src\backend/core

2017-11-16 Thread Uwe Stöhr
https://bugs.kde.org/show_bug.cgi?id=387015

--- Comment #1 from Uwe Stöhr  ---
Here some more:

2>C:\CraftRoot\labplot\src\backend/core/AbstractPart.h(66): warning C4625:
'AbstractPart': copy constructor was implicitly defined as deleted
2>C:\CraftRoot\labplot\src\backend/core/AbstractPart.h(66): warning C4626:
'AbstractPart': assignment operator was implicitly defined as deleted
2>C:\CraftRoot\labplot\src\backend/core/AbstractScriptingEngine.h(84): warning
C4820: 'AbstractScriptingEngine': '3' bytes padding added after data member
'AbstractScriptingEngine::m_initialized'
2>C:\CraftRoot\labplot\src\backend/core/AbstractScriptingEngine.h(85): warning
C4625: 'AbstractScriptingEngine': copy constructor was implicitly defined as
deleted
2>C:\CraftRoot\labplot\src\backend/core/AbstractScriptingEngine.h(85): warning
C5026: 'AbstractScriptingEngine': move constructor was implicitly defined as
deleted
2>C:\CraftRoot\labplot\src\backend/core/AbstractScriptingEngine.h(85): warning
C4626: 'AbstractScriptingEngine': assignment operator was implicitly defined as
deleted
2>C:\CraftRoot\labplot\src\backend/core/AbstractScriptingEngine.h(85): warning
C5027: 'AbstractScriptingEngine': move assignment operator was implicitly
defined as deleted
2>C:\CraftRoot\labplot\src\backend/datasources/AbstractDataSource.h(51):
warning C4625: 'AbstractDataSource': copy constructor was implicitly defined as
deleted
2>C:\CraftRoot\labplot\src\backend/datasources/AbstractDataSource.h(51):
warning C4626: 'AbstractDataSource': assignment operator was implicitly defined
as deleted
2>c:\craftroot\labplot\src\backend\core\AbstractFilter.h(97): warning C4625:
'AbstractFilter': copy constructor was implicitly defined as deleted
2>c:\craftroot\labplot\src\backend\core\AbstractFilter.h(97): warning C4626:
'AbstractFilter': assignment operator was implicitly defined as deleted
2>C:\CraftRoot\labplot\src\backend/worksheet/WorksheetElement.h(84): warning
C4625: 'WorksheetElement': copy constructor was implicitly defined as deleted
2>C:\CraftRoot\labplot\src\backend/worksheet/WorksheetElement.h(84): warning
C4626: 'WorksheetElement': assignment operator was implicitly defined as
deleted
2>C:\CraftRoot\labplot\src\backend/worksheet/WorksheetElementContainer.h(77):
warning C4625: 'WorksheetElementContainer': copy constructor was implicitly
defined as deleted
2>C:\CraftRoot\labplot\src\backend/worksheet/WorksheetElementContainer.h(77):
warning C4626: 'WorksheetElementContainer': assignment operator was implicitly
defined as deleted

and:

2>C:\CraftRoot\labplot\src\backend/worksheet/plots/AbstractPlot.h(67): warning
C4625: 'AbstractPlot': copy constructor was implicitly defined as deleted
2>C:\CraftRoot\labplot\src\backend/worksheet/plots/AbstractPlot.h(67): warning
C4626: 'AbstractPlot': assignment operator was implicitly defined as deleted
2>  C:\CraftRoot\labplot\src\backend/lib/IntervalAttribute.h(206): note: see
reference to class template instantiation
'QtPrivate::QForeachContainer>' being compiled
2>C:\CraftRoot\labplot\src\backend/core/AbstractSimpleFilter.h(82): warning
C4625: 'AbstractSimpleFilter': copy constructor was implicitly defined as
deleted
2>C:\CraftRoot\labplot\src\backend/core/AbstractSimpleFilter.h(82): warning
C5026: 'AbstractSimpleFilter': move constructor was implicitly defined as
deleted
2>C:\CraftRoot\labplot\src\backend/core/AbstractSimpleFilter.h(82): warning
C4626: 'AbstractSimpleFilter': assignment operator was implicitly defined as
deleted
2>C:\CraftRoot\labplot\src\backend/core/AbstractSimpleFilter.h(82): warning
C5027: 'AbstractSimpleFilter': move assignment operator was implicitly defined
as deleted
2>C:\CraftRoot\labplot\src\backend/core/AbstractSimpleFilter.h(105): warning
C4625: 'SimpleFilterColumn': copy constructor was implicitly defined as deleted
2>C:\CraftRoot\labplot\src\backend/core/AbstractSimpleFilter.h(105): warning
C5026: 'SimpleFilterColumn': move constructor was implicitly defined as deleted
2>C:\CraftRoot\labplot\src\backend/core/AbstractSimpleFilter.h(105): warning
C4626: 'SimpleFilterColumn': assignment operator was implicitly defined as
deleted
2>C:\CraftRoot\labplot\src\backend/core/AbstractSimpleFilter.h(105): warning
C5027: 'SimpleFilterColumn': move assignment operator was implicitly defined as
deleted

and many more. Maybe one can ignore them?

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

[kdevelop] [Bug 368449] KDevelop crashed when opening a file that changed on disk [clang::comments::Lexer::lex, clang_Cursor_getParsedComment]

2017-11-16 Thread Kevin Funk
https://bugs.kde.org/show_bug.cgi?id=368449

Kevin Funk  changed:

   What|Removed |Added

Summary|KDevelop crashed when   |KDevelop crashed when
   |opening a file that changed |opening a file that changed
   |on disk |on disk
   |[clang::comments::Lexer::le |[clang::comments::Lexer::le
   |x, LLVM 3.8]|x,
   ||clang_Cursor_getParsedComme
   ||nt]

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

[LabPlot2] [Bug 387015] New: implicitly defined as deleted warnings in src\backend/core

2017-11-16 Thread Uwe Stöhr
https://bugs.kde.org/show_bug.cgi?id=387015

Bug ID: 387015
   Summary: implicitly defined as deleted warnings in
src\backend/core
   Product: LabPlot2
   Version: latest
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: backend
  Assignee: alexander.se...@web.de
  Reporter: uwesto...@web.de
  Target Milestone: ---

I get:

2>C:\CraftRoot\labplot\src\backend/core/AbstractAspect.h(217): warning C4625:
'AbstractAspect': copy constructor was implicitly defined as deleted
2>C:\CraftRoot\labplot\src\backend/core/AbstractAspect.h(217): warning C4626:
'AbstractAspect': assignment operator was implicitly defined as deleted
2>C:\CraftRoot\labplot\src\backend/core/AbstractColumn.h(218): warning C4625:
'AbstractColumn': copy constructor was implicitly defined as deleted
2>C:\CraftRoot\labplot\src\backend/core/AbstractColumn.h(218): warning C4626:
'AbstractColumn': assignment operator was implicitly defined as deleted

and:

2>C:\CraftRoot\labplot\src\backend/datasources/filters/AbstractFileFilter.h(67):
warning C4625: 'AbstractFileFilter': copy constructor was implicitly defined as
deleted
2>C:\CraftRoot\labplot\src\backend/datasources/filters/AbstractFileFilter.h(67):
warning C4626: 'AbstractFileFilter': assignment operator was implicitly defined
as deleted
2>C:\CraftRoot\labplot\src\backend/datasources/filters/HDFFilter.h(71): warning
C4625: 'HDFFilter': copy constructor was implicitly defined as deleted
2>C:\CraftRoot\labplot\src\backend/datasources/filters/HDFFilter.h(71): warning
C4626: 'HDFFilter': assignment operator was implicitly defined as deleted

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

[Heaptrack] [Bug 386923] heaptrack stalls forever in LineReader::getLine

2017-11-16 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=386923

--- Comment #3 from Milian Wolff  ---
disabling the unsetenv calls in heaptrack_preload.cpp and then using `valgrind
--trace-children=yes --track-origins=yes` we eventually see something like
this:

==11099== Invalid read of size 8
==11099==at 0x723EE81: ??? (in
/opt/intel/opencl-runtime/lib64/libintelocl.so)
==11099==by 0x71A13FD: clGetPlatformInfo (in
/opt/intel/opencl-runtime/lib64/libintelocl.so)
==11099==by 0x4E3DE4C: ??? (in /usr/lib/libOpenCL.so.1.0.0)
==11099==by 0x4E3F21E: ??? (in /usr/lib/libOpenCL.so.1.0.0)
==11099==by 0x4E3FE83: clGetPlatformIDs (in /usr/lib/libOpenCL.so.1.0.0)
==11099==by 0x401277: ??? (in /usr/bin/clinfo)
==11099==by 0x527CF69: (below main) (in /usr/lib/libc-2.26.so)
==11099==  Address 0x8 is not stack'd, malloc'd or (recently) free'd
==11099== 
==11099== 
==11099== Process terminating with default action of signal 11 (SIGSEGV):
dumping core
==11099==  Access not within mapped region at address 0x8
==11099==at 0x723EE81: ??? (in
/opt/intel/opencl-runtime/lib64/libintelocl.so)
==11099==by 0x71A13FD: clGetPlatformInfo (in
/opt/intel/opencl-runtime/lib64/libintelocl.so)
==11099==by 0x4E3DE4C: ??? (in /usr/lib/libOpenCL.so.1.0.0)
==11099==by 0x4E3F21E: ??? (in /usr/lib/libOpenCL.so.1.0.0)
==11099==by 0x4E3FE83: clGetPlatformIDs (in /usr/lib/libOpenCL.so.1.0.0)
==11099==by 0x401277: ??? (in /usr/bin/clinfo)
==11099==by 0x527CF69: (below main) (in /usr/lib/libc-2.26.so)
==11099==  If you believe this happened as a result of a stack
==11099==  overflow in your program's main thread (unlikely but
==11099==  possible), you can try to increase the size of the
==11099==  main thread stack using the --main-stacksize= flag.
==11099==  The main thread stack size used in this run was 8388608.

which matches what I see in GDB:

Thread 1 "clinfo" received signal SIGSEGV, Segmentation fault.
0x75c3fe81 in ?? () from /opt/intel/opencl-runtime/lib64/libintelocl.so
(gdb) bt
#0  0x75c3fe81 in ?? () from
/opt/intel/opencl-runtime/lib64/libintelocl.so
#1  0x75ba23fe in clGetPlatformInfo () from
/opt/intel/opencl-runtime/lib64/libintelocl.so
#2  0x77bbde4d in ?? () from /usr/lib/libOpenCL.so.1
#3  0x77bbf21f in ?? () from /usr/lib/libOpenCL.so.1
#4  0x77bbfe84 in clGetPlatformIDs () from /usr/lib/libOpenCL.so.1
#5  0x00401278 in ?? ()
#6  0x7761df6a in __libc_start_main () from /usr/lib/libc.so.6
#7  0x0040150a in ?? ()

Running clinfo without heaptrack doesn't show these issues. I still have no
clue what is going on... Is one of the dlopened opencl libs maybe also messing
around with malloc & friends? I see e.g.
/opt/intel/opencl-runtime/lib64/libtbbmalloc.so.2 hmmm but just dlopening that
lib or some of the others doesn't trigger that crash for me. Seems like I'll
have to compile libintelocl.so from sources with debug symbols.

@Giuseppe: What opencl backends do you have? Only the mesa one? 

If I uninstall the intel backend, heaptrack works fine for me on clinfo:

└$ heaptrack clinfo
heaptrack output will be written to "/tmp/heaptrack.clinfo.22644.gz"
starting application, this might take some time...
Number of platforms   1
  Platform Name   Clover
  Platform Vendor Mesa
  Platform VersionOpenCL 1.1 Mesa 17.2.5
  Platform ProfileFULL_PROFILE
  Platform Extensions cl_khr_icd
  Platform Extensions function suffix MESA

  Platform Name   Clover
Number of devices 0

NULL platform behavior
  clGetPlatformInfo(NULL, CL_PLATFORM_NAME, ...)  Clover
  clGetDeviceIDs(NULL, CL_DEVICE_TYPE_ALL, ...)   Clover
  clCreateContext(NULL, ...) [default]No devices found in platform
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_CPU)  No devices found in
platform
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_GPU)  No devices found in
platform
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_ACCELERATOR)  No devices found
in platform
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_CUSTOM)  No devices found in
platform
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_ALL)  No devices found in
platform

ICD loader properties
  ICD loader Name OpenCL ICD Loader
  ICD loader Vendor   OCL Icd free software
  ICD loader Version  2.2.11
  ICD loader Profile  OpenCL 2.1
heaptrack stats:
allocations:1512
leaked allocations: 1102
temporary allocations:  80
Heaptrack finished! Now run the following to investigate the data:

  heaptrack --analyze "/tmp/heaptrack.clinfo.22644.gz"

-- 
You are receiving this mail because:
You 

[kdevelop] [Bug 386857] next window shortcut picks a random tab

2017-11-16 Thread LtWorf
https://bugs.kde.org/show_bug.cgi?id=386857

--- Comment #2 from Salvo "LtWorf" Tomaselli  ---
I use menus, they are called "Previous window" and "next window"

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

[LabPlot2] [Bug 387014] New: no function warnings for gsl\parser.h

2017-11-16 Thread Uwe Stöhr
https://bugs.kde.org/show_bug.cgi?id=387014

Bug ID: 387014
   Summary: no function warnings for gsl\parser.h
   Product: LabPlot2
   Version: latest
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: backend
  Assignee: alexander.se...@web.de
  Reporter: uwesto...@web.de
  Target Milestone: ---

I get:

2>C:\CraftRoot\labplot\src\backend\gsl\parser.h(42): warning C4255: 'fnct': no
function prototype given: converting '()' to '(void)'
2>C:\CraftRoot\labplot\src\backend\gsl\parser.h(49): warning C4820:
'parser_var': '6' bytes padding added after data member 'name'
2>C:\CraftRoot\labplot\src\backend\gsl\parser.h(53): warning C4255: 'func_t':
no function prototype given: converting '()' to '(void)'
2>C:\CraftRoot\labplot\src\backend\gsl\parser.h(62): warning C4820: 'symrec':
'4' bytes padding added after data member 'type'
2>C:\CraftRoot\labplot\src\backend\gsl\parser.h(66): warning C4255:
'init_table': no function prototype given: converting '()' to '(void)'
2>C:\CraftRoot\labplot\src\backend\gsl\parser.h(67): warning C4255:
'delete_table': no function prototype given: converting '()' to '(void)'
2>C:\CraftRoot\labplot\src\backend\gsl\parser.h(68): warning C4255:
'parse_errors': no function prototype given: converting '()' to '(void)'

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

[LabPlot2] [Bug 387013] New: loss of data warnings for nsl_fit.c

2017-11-16 Thread Uwe Stöhr
https://bugs.kde.org/show_bug.cgi?id=387013

Bug ID: 387013
   Summary: loss of data warnings for  nsl_fit.c
   Product: LabPlot2
   Version: latest
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: backend
  Assignee: alexander.se...@web.de
  Reporter: uwesto...@web.de
  Target Milestone: ---

I get:

2>C:\CraftRoot\labplot\src\backend\nsl\nsl_fit.c(576): warning C4244:
'function': conversion from 'double' to 'const unsigned int', possible loss of
data
2>C:\CraftRoot\labplot\src\backend\nsl\nsl_fit.c(582): warning C4244:
'function': conversion from 'double' to 'const unsigned int', possible loss of
data
2>C:\CraftRoot\labplot\src\backend\nsl\nsl_fit.c(596): warning C4244:
'function': conversion from 'double' to 'const unsigned int', possible loss of
data
2>C:\CraftRoot\labplot\src\backend\nsl\nsl_fit.c(607): warning C4244:
'function': conversion from 'double' to 'const unsigned int', possible loss of
data
2>C:\CraftRoot\labplot\src\backend\nsl\nsl_fit.c(615): warning C4244:
'function': conversion from 'double' to 'const unsigned int', possible loss of
data
2>C:\CraftRoot\labplot\src\backend\nsl\nsl_fit.c(615): warning C4244:
'function': conversion from 'double' to 'unsigned int', possible loss of data
2>C:\CraftRoot\labplot\src\backend\nsl\nsl_fit.c(631): warning C4244:
'function': conversion from 'double' to 'const unsigned int', possible loss of
data
2>C:\CraftRoot\labplot\src\backend\nsl\nsl_fit.c(647): warning C4710: 'int
printf(const char *const ,...)': function not inlined

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

[LabPlot2] [Bug 387011] New: loss of data warnings for nsl_sf_basic.h

2017-11-16 Thread Uwe Stöhr
https://bugs.kde.org/show_bug.cgi?id=387011

Bug ID: 387011
   Summary: loss of data warnings for nsl_sf_basic.h
   Product: LabPlot2
   Version: latest
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: backend
  Assignee: alexander.se...@web.de
  Reporter: uwesto...@web.de
  Target Milestone: ---

I get:

2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(36): warning C4255:
'nsl_sf_rand': no function prototype given: converting '()' to '(void)'
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(37): warning C4255:
'nsl_sf_random': no function prototype given: converting '()' to '(void)'
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(38): warning C4255:
'nsl_sf_drand': no function prototype given: converting '()' to '(void)'
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(82): warning C4244:
'function': conversion from 'double' to 'const int', possible loss of data
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(83): warning C4244:
'function': conversion from 'double' to 'const int', possible loss of data
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(93): warning C4244:
'function': conversion from 'double' to 'unsigned int', possible loss of data
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(94): warning C4244:
'function': conversion from 'double' to 'unsigned int', possible loss of data
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(95): warning C4244:
'function': conversion from 'double' to 'unsigned int', possible loss of data
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(96): warning C4244:
'function': conversion from 'double' to 'unsigned int', possible loss of data
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(98): warning C4244:
'function': conversion from 'double' to 'const int', possible loss of data
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(99): warning C4244:
'function': conversion from 'double' to 'const int', possible loss of data
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(100): warning C4244:
'function': conversion from 'double' to 'const int', possible loss of data
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(101): warning C4244:
'function': conversion from 'double' to 'const int', possible loss of data
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(102): warning C4244:
'function': conversion from 'double' to 'const int', possible loss of data
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(103): warning C4244:
'function': conversion from 'double' to 'const int', possible loss of data
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(104): warning C4244:
'function': conversion from 'double' to 'const int', possible loss of data
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(105): warning C4244:
'function': conversion from 'double' to 'const int', possible loss of data
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(106): warning C4244:
'function': conversion from 'double' to 'const int', possible loss of data
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(107): warning C4244:
'function': conversion from 'double' to 'const int', possible loss of data
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(108): warning C4244:
'function': conversion from 'double' to 'unsigned int', possible loss of data
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(109): warning C4244:
'function': conversion from 'double' to 'unsigned int', possible loss of data
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(110): warning C4244:
'function': conversion from 'double' to 'unsigned int', possible loss of data
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(112): warning C4244:
'function': conversion from 'double' to 'const int', possible loss of data
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(132): warning C4244:
'function': conversion from 'double' to 'const int', possible loss of data
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(133): warning C4244:
'function': conversion from 'double' to 'const int', possible loss of data
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(135): warning C4244:
'function': conversion from 'double' to 'const unsigned int', possible loss of
data
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(136): warning C4244:
'function': conversion from 'double' to 'const unsigned int', possible loss of
data
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(137): warning C4244:
'function': conversion from 'double' to 'const unsigned int', possible loss of
data
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(138): warning C4244:
'function': conversion from 'double' to 'const unsigned int', possible loss of
data
2>C:\CraftRoot\labplot\src\backend/nsl/nsl_sf_basic.h(139): warning C4244:
'function': conversion from 'double' to 'unsigned int', 

[frameworks-kwindowsystem] [Bug 387012] New: Failing tests in master

2017-11-16 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=387012

Bug ID: 387012
   Summary: Failing tests in master
   Product: frameworks-kwindowsystem
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mgraess...@kde.org
  Reporter: christo...@krop.fr
CC: kdelibs-b...@kde.org
  Target Milestone: ---

With a fresh build and Qt 5.10 beta 3 :

The following tests FAILED:
  2 - kwindowsystem-kmanagerselectiontest (Failed)
  5 - kwindowsystem-kkeyserver_x11_unittest (Failed)
  7 - kwindowsystem-kwindowinfox11test (Failed)
  8 - kwindowsystem-kwindowsystemx11test (Failed)

2/14 Testing: kwindowsystem-kmanagerselectiontest :
PASS   : KManagerSelectionTest::initTestCase()
FAIL!  : KManagerSelectionTest::testAcquireRelease() 'newOwnerSpy.wait()'
returned FALSE. ()
   Loc:
[/kde/src/5/frameworks/kwindowsystem/autotests/kmanagerselectiontest.cpp(63)]
PASS   : KManagerSelectionTest::testInitiallyOwned()
XFAIL  : KManagerSelectionTest::testLostOwnership() selectionClear event is not
sent to the same X client
   Loc:
[/kde/src/5/frameworks/kwindowsystem/autotests/kmanagerselectiontest.cpp(100)]
PASS   : KManagerSelectionTest::testLostOwnership()

---
5/14 Testing: kwindowsystem-kkeyserver_x11_unittest

QDEBUG : KKeyServerTest::decodeXcbEvent(CTRL_1) 0:07:43 -
kkeyserver_x11_unittest(2189) -  KKeyServerTest::decodeXcbEvent: given modX= 4
keySymX=0x "31" I expected keyQt=0x "431" "Ctrl+1" got "426" "Ctrl+&"
FAIL!  : KKeyServerTest::decodeXcbEvent(CTRL_1) Compared values are not the
same
   Actual   (decodedKeyQt): 67108902
   Expected (keyQt)   : 67108913
   Loc:
[/kde/src/5/frameworks/kwindowsystem/autotests/kkeyserver_x11_unittest.cpp(131)]

[...]

QDEBUG : KKeyServerTest::decodeXcbEvent(CTRL_ampersand) 0:07:43 -
kkeyserver_x11_unittest(2189) -  KKeyServerTest::decodeXcbEvent: given modX= 4
keySymX=0x "26" I expected keyQt=0x "426" "Ctrl+&" got "431" "Ctrl+1"
FAIL!  : KKeyServerTest::decodeXcbEvent(CTRL_ampersand) Compared values are not
the same
   Actual   (decodedKeyQt): 67108913
   Expected (keyQt)   : 67108902
   Loc:
[/kde/src/5/frameworks/kwindowsystem/autotests/kkeyserver_x11_unittest.cpp(131)]

---
7/14 Testing: kwindowsystem-kwindowinfox11test

Config: Using QtTest library 5.10.0, Qt 5.10.0 (x86_64-little_endian-lp64
shared (dynamic) release build; by GCC 7.2.1 20171020 [gcc-7-branch revision
253932])
PASS   : KWindowInfoX11Test::initTestCase()
QDEBUG : KWindowInfoX11Test::testState(max) 0:07:43 - kwindowinfox11test(2190)
- org.kde.kwindowsystem: loadPlugin: Loaded plugin
"/kde/inst/5/lib64/plugins/kf5/org.kde.kwindowsystem.platforms/KF5WindowSystemX11Plugin.so"
for platform "xcb"
QWARN  : KWindowInfoX11Test::testState(max) 0:07:43 - kwindowinfox11test(2190)
-  : QXcbConnection: XCB error: 3 (BadWindow), sequence: 696, resource id:
169869326, major code: 3 (GetWindowAttributes), minor code: 0
QWARN  : KWindowInfoX11Test::testState(max) 0:07:43 - kwindowinfox11test(2190)
-  : QXcbConnection: XCB error: 3 (BadWindow), sequence: 697, resource id:
169869326, major code: 2 (ChangeWindowAttributes), minor code: 0
PASS   : KWindowInfoX11Test::testState(max)
PASS   : KWindowInfoX11Test::testState(maxHoriz)
PASS   : KWindowInfoX11Test::testState(shaded)
FAIL!  : KWindowInfoX11Test::testState(skipTaskbar)
'!info.hasState(NET::States(1 << i))' returned FALSE. ()
   Loc:
[/kde/src/5/frameworks/kwindowsystem/autotests/kwindowinfox11test.cpp(217)]
PASS   : KWindowInfoX11Test::testState(skipPager)
PASS   : KWindowInfoX11Test::testState(keep above)
[...]
FAIL!  : KWindowInfoX11Test::testActivities() 'info4.activities().size() == 2'
returned FALSE. ()
   Loc:
[/kde/src/5/frameworks/kwindowsystem/autotests/kwindowinfox11test.cpp(541)]

---
8/14 Testing: kwindowsystem-kwindowsystemx11test

PASS   : KWindowSystemX11Test::initTestCase()
QDEBUG : KWindowSystemX11Test::testActiveWindowChanged() 0:07:43 -
kwindowsystemx11test(2191) - org.kde.kwindowsystem: loadPlugin: Loaded plugin
"/kde/inst/5/lib64/plugins/kf5/org.kde.kwindowsystem.platforms/KF5WindowSystemX11Plugin.so"
for platform "xcb"
FAIL!  : KWindowSystemX11Test::testActiveWindowChanged() Compared values are
not the same
   Actual   (spy.first().at(0).toULongLong()): 171966469
   Expected (widget->winId()): 169869317
   Loc:
[/kde/src/5/frameworks/kwindowsystem/autotests/kwindowsystemx11test.cpp(65)]
FAIL!  : KWindowSystemX11Test::testWindowAdded() 'spy.count() > 0' returned
FALSE. ()
   Loc:
[/kde/src/5/frameworks/kwindowsystem/autotests/kwindowsystemx11test.cpp(77)]
PASS   : KWindowSystemX11Test::testWindowRemoved()

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

[LabPlot2] [Bug 387010] New: loss of data warnings for parser.y

2017-11-16 Thread Uwe Stöhr
https://bugs.kde.org/show_bug.cgi?id=387010

Bug ID: 387010
   Summary: loss of data warnings for parser.y
   Product: LabPlot2
   Version: latest
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: backend
  Assignee: alexander.se...@web.de
  Reporter: uwesto...@web.de
  Target Milestone: ---

I get:

2>backend/gsl/parser.y(53): warning C4820: 'param': '4' bytes padding added
after data member 'pos'
2>D:/LabPlot/src/gsl_parser.c(1086): warning C4242: '=': conversion from 'int'
to 'yytype_int16', possible loss of data
2>backend/gsl/parser.y(114): warning C4255: 'parse_errors': no function
prototype given: converting '()' to '(void)'
2>backend/gsl/parser.y(305): warning C4267: '+=': conversion from 'size_t' to
'unsigned int', possible loss of data
2>backend/gsl/parser.y(327): warning C4242: '=': conversion from 'int' to
'char', possible loss of data

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

[LabPlot2] [Bug 387009] New: compilation of fittest fails

2017-11-16 Thread Uwe Stöhr
https://bugs.kde.org/show_bug.cgi?id=387009

Bug ID: 387009
   Summary: compilation of fittest fails
   Product: LabPlot2
   Version: latest
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: backend
  Assignee: alexander.se...@web.de
  Reporter: uwesto...@web.de
  Target Milestone: ---

Compiling the target "fittest" with MSVC 2015 fails because of this error:

2>C:\CraftRoot\labplot\src\backend\gsl\functions.h(47): error C2099:
initializer is not a constant

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

[frameworks-kwayland] [Bug 387008] Failing tests in master

2017-11-16 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=387008

--- Comment #1 from Christophe Giboudeaux  ---
with the wayland debug package installed :
#2  0x7f577dc070bf in wl_abort (fmt=fmt@entry=0x7f577dc0728e "Error sending
request: %s\n") at src/wayland-util.c:419
#3  0x7f577dc0313d in wl_proxy_marshal_array_constructor_versioned
(proxy=proxy@entry=0x214eed0, opcode=opcode@entry=0,
args=args@entry=0x7ffdd7c9dee0, interface=interface@entry=0x0, version=1)
at src/wayland-client.c:659
#4  0x7f577dc03199 in wl_proxy_marshal_array_constructor
(proxy=proxy@entry=0x214eed0, opcode=opcode@entry=0,
args=args@entry=0x7ffdd7c9dee0, interface=interface@entry=0x0) at
src/wayland-client.c:599
#5  0x7f577dc0328c in wl_proxy_marshal (proxy=0x214eed0, opcode=0) at
src/wayland-client.c:696
#6  0x7f577fd14ad9 in zxdg_exported_v2_destroy (zxdg_exported_v2=0x214eed0)
at
/kde/build/5/frameworks/kwayland/src/client/wayland-xdg-foreign-unstable-v2-client-protocol.h:371

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

[kscreenlocker] [Bug 346741] bring back "auto-lock screen on login" option from KDM/Plasma 4

2017-11-16 Thread Mircea Kitsune
https://bugs.kde.org/show_bug.cgi?id=346741

--- Comment #8 from Mircea Kitsune  ---
The screen locker you activate on demand isn't encrypted either. I don't see
why this is relevant to auto-lock on startup: Your computer is as secure with
auto-lock as it is when you leave it running after you've manually locked it.

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

[frameworks-kwayland] [Bug 387008] New: Failing tests in master

2017-11-16 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=387008

Bug ID: 387008
   Summary: Failing tests in master
   Product: frameworks-kwayland
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mgraess...@kde.org
  Reporter: christo...@krop.fr
  Target Milestone: ---

Using master and Qt 5.10 beta 3.

The following tests FAILED:
  7 - kwayland-testWaylandSurface (OTHER_FAULT)
 33 - kwayland-testXdgForeign (OTHER_FAULT)

The failure seems to happen *after* the test.
eg :

PASS   : TestForeign::testImportTwoTimes()
PASS   : TestForeign::cleanupTestCase()
Totals: 9 passed, 0 failed, 0 skipped, 0 blacklisted, 101ms
* Finished testing of TestForeign *
Error sending request: Bad file descriptor
[1]1943 abort (core dumped)  ./testXdgForeign


#1  0x7f577ee476b1 in __GI_abort () at abort.c:79
#2  0x7f577dc070bf in ?? ()
#3  0x7f577dc0313d in wl_proxy_marshal_array_constructor_versioned () from
/usr/lib64/libwayland-client.so.0
#4  0x7f577dc0328c in wl_proxy_marshal () from
/usr/lib64/libwayland-client.so.0
#5  0x7f577fd14ad9 in zxdg_exported_v2_destroy (zxdg_exported_v2=0x214eed0)
at
/kde/build/5/frameworks/kwayland/src/client/wayland-xdg-foreign-unstable-v2-client-protocol.h:371
#6  0x7f577fd13f6f in KWayland::Client::WaylandPointer::release (this=0x214aae8) at
/kde/src/5/frameworks/kwayland/src/client/wayland_pointer_p.h:53
#7  0x7f577fd13f29 in
KWayland::Client::XdgExportedUnstableV2::Private::release (this=0x214aad0) at
/kde/src/5/frameworks/kwayland/src/client/xdgforeign_v2.cpp:201
#8  0x7f577fd1574a in KWayland::Client::XdgExported::release
(this=0x2151f20) at
/kde/src/5/frameworks/kwayland/src/client/xdgforeign.cpp:188
#9  0x7f577fd156f7 in KWayland::Client::XdgExported::~XdgExported
(this=0x2151f20) at
/kde/src/5/frameworks/kwayland/src/client/xdgforeign.cpp:178
#10 0x7f577fd143a5 in
KWayland::Client::XdgExportedUnstableV2::~XdgExportedUnstableV2
(this=0x2151f20) at
/kde/src/5/frameworks/kwayland/src/client/xdgforeign_v2.cpp:248
#11 0x7f577fd143c9 in
KWayland::Client::XdgExportedUnstableV2::~XdgExportedUnstableV2
(this=0x2151f20) at
/kde/src/5/frameworks/kwayland/src/client/xdgforeign_v2.cpp:247
#12 0x7f577f806cbb in QObjectPrivate::deleteChildren() () from
/usr/lib64/libQt5Core.so.5
#13 0x7f577f81000b in QObject::~QObject() () from
/usr/lib64/libQt5Core.so.5
#14 0x0040a3b3 in TestForeign::~TestForeign (this=0x7ffdd7c9e248) at
/kde/src/5/frameworks/kwayland/autotests/client/test_xdg_foreign.cpp:38
#15 0x00407e79 in main (argc=1, argv=0x7ffdd7c9e408) at
/kde/src/5/frameworks/kwayland/autotests/client/test_xdg_foreign.cpp:400

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

[Breeze] [Bug 380508] Using the Breeze icon theme for LibreOffice results in small icons always being used even when large ones should be used--and are available (visible in Task Switcher with Large I

2017-11-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=380508

Nate Graham  changed:

   What|Removed |Added

URL||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=65
   ||754

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

[kmymoney] [Bug 351892] online banking passwords not stored/remembered

2017-11-16 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=351892

--- Comment #6 from Ralf Habacker  ---
Git commit 704ef3376ca9889b6ceab3cbf9166b407a7133fa by Ralf Habacker.
Committed on 16/11/2017 at 22:46.
Pushed by habacker into branch 'master'.

Add ofx test web service to www.kmymoney.org

A  +154  -0ofxtest.php

https://commits.kde.org/websites/kmymoney-org/704ef3376ca9889b6ceab3cbf9166b407a7133fa

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

[Breeze] [Bug 380508] Using the Breeze icon theme for LibreOffice results in small icons always being used even when large ones should be used--and are available (visible in Task Switcher with Large I

2017-11-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=380508

--- Comment #5 from Nate Graham  ---
The upstream bug for LibreOffice is
https://bugs.documentfoundation.org/show_bug.cgi?id=65754

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

[yakuake] [Bug 387007] New: sudo apt-get upgrade aborts automatically after displaying prompt

2017-11-16 Thread Hamidreza Jafari
https://bugs.kde.org/show_bug.cgi?id=387007

Bug ID: 387007
   Summary: sudo apt-get upgrade aborts automatically after
displaying prompt
   Product: yakuake
   Version: 3.0.4
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: hamidrjaf...@gmail.com
  Target Milestone: ---

Hello,

Recently it is not possible to upgrade using Yakuake command prompt. After
issuing the command:

$ sudo apt-get upgrade

it displays the usual information and the prompt to press Y to proceed. Alas it
aborts without waiting for user input. Seems some other process is feeding
input or the wiring is tampered. This phenomenon does not appear in Konsole or
mlterm. A similar report resides:
https://askubuntu.com/questions/509852/why-does-apt-get-abort-by-itself-as-though-id-pressed-n

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

[valgrind] [Bug 386425] running valgrind + wine on armv7l gives illegal opcode

2017-11-16 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=386425

--- Comment #13 from Austin English  ---
Created attachment 108909
  --> https://bugs.kde.org/attachment.cgi?id=108909=edit
output with patch

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

[valgrind] [Bug 386425] running valgrind + wine on armv7l gives illegal opcode

2017-11-16 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=386425

--- Comment #12 from Austin English  ---
Created attachment 108908
  --> https://bugs.kde.org/attachment.cgi?id=108908=edit
output without patch

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

[valgrind] [Bug 386425] running valgrind + wine on armv7l gives illegal opcode

2017-11-16 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=386425

--- Comment #11 from Austin English  ---
(In reply to Julian Seward from comment #10)
> Created attachment 108896 [details]
> TPIDRURW support for 32-bit arm
> 
> This runs the test program shown in comment 6, correctly, both for
> Thumb and ARM encodings.  For 32 bit only.  Austin, can you test this?

Seems to work for me, thanks!

I'm going to attach logs with/without the patch. I used --verbose instead of
-q, which then showed the missing info:
disInstr(arm): unhandled instruction: 0xEE0D4F50
 cond=14(0xE) 27:20=224(0xE0) 4:4=1 3:0=0(0x0)
==4434== valgrind: Unrecognised instruction at address 0x4fc3bb4.
==4434==at 0x4FC3BB4: signal_init_thread (signal_arm.c:974)
==4434==by 0x4FCACF7: thread_init (thread.c:354)
==4434==by 0x4FA1433: __wine_process_init (loader.c:3341)
==4434==by 0x485FBC3: wine_init (loader.c:979)
==4434==by 0x108A27: main (main.c:258)

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

[plasmashell] [Bug 386441] Plasma crash while minimizing all windows and using Hue Plasmoid

2017-11-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=386441

--- Comment #7 from weltq...@gmail.com ---
Created attachment 108907
  --> https://bugs.kde.org/attachment.cgi?id=108907=edit
another backtrace

Bug pertains in latest Version of Frameworks.

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

[korganizer] [Bug 386988] Schedule > Publish Item Information - Error: Unable to publish the item '...'

2017-11-16 Thread Allen Winter
https://bugs.kde.org/show_bug.cgi?id=386988

Allen Winter  changed:

   What|Removed |Added

 CC||win...@kde.org

--- Comment #2 from Allen Winter  ---
do you see a message in your console?
there should be a critical string printed in your console "Publish failed.
Unable to publish the item ... "

can you show me that entire string?

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

[Discover] [Bug 386999] Discover crash

2017-11-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=386999

Nate Graham  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE
 CC||pointedst...@zoho.com

--- Comment #1 from Nate Graham  ---


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

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

[Discover] [Bug 385679] Discover crashes in QObjectPrivate::addConnection() while searching

2017-11-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=385679

Nate Graham  changed:

   What|Removed |Added

 CC||nnc@gmail.com

--- Comment #4 from Nate Graham  ---
*** Bug 386999 has been marked as a duplicate of this bug. ***

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

[frameworks-kcoreaddons] [Bug 387006] New: Failing tests in master

2017-11-16 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=387006

Bug ID: 387006
   Summary: Failing tests in master
   Product: frameworks-kcoreaddons
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mp...@kde.org
  Reporter: christo...@krop.fr
CC: kdelibs-b...@kde.org
  Target Milestone: ---

Maybe that started earlier, I don't run tests often.
23/24 Test #24: kdirwatch_qfswatch_unittest ..***Failed   25.40 sec
24/24 Test #22: kdirwatch_stat_unittest ..***Failed   28.36 sec

# ./kdirwatch_qfswatch_unittest 
23:04:29 - kdirwatch_qfswatch_unittest(19844) - 
KDirWatch_UnitTest::KDirWatch_UnitTest: Using method QFSWatch
* Start testing of KDirWatch_UnitTest *
Config: Using QtTest library 5.10.0, Qt 5.10.0 (x86_64-little_endian-lp64
shared (dynamic) release build; by GCC 7.2.1 20171020 [gcc-7-branch revision
253932])

[...]

QDEBUG : KDirWatch_UnitTest::testHardlinkChange() 23:04:51 -
kdirwatch_qfswatch_unittest(19844) - kf5.kcoreaddons.kdirwatch:
KDirWatchPrivate::useQFSWatch: fsWatcher->addPath
"/tmp/kdirwatch_qfswatch_unittest-uaIYOw/ExistingFile"
QDEBUG : KDirWatch_UnitTest::testHardlinkChange() 23:04:51 -
kdirwatch_qfswatch_unittest(19844) - kf5.kcoreaddons.kdirwatch:
KDirWatch::setDeleted: "KDirWatch-2" emitting deleted
"/tmp/kdirwatch_qfswatch_unittest-uaIYOw/ExistingFile"
QDEBUG : KDirWatch_UnitTest::testHardlinkChange() 23:04:51 -
kdirwatch_qfswatch_unittest(19844) - kf5.kcoreaddons.kdirwatch:
KDirWatch::setCreated: "KDirWatch-2" emitting created
"/tmp/kdirwatch_qfswatch_unittest-uaIYOw/ExistingFile"
QDEBUG : KDirWatch_UnitTest::testHardlinkChange() 23:04:51 -
kdirwatch_qfswatch_unittest(19844) - kf5.kcoreaddons.kdirwatch:
KDirWatch::setDeleted: "KDirWatch-13" emitting deleted
"/tmp/kdirwatch_qfswatch_unittest-uaIYOw/ExistingFile"
QDEBUG : KDirWatch_UnitTest::testHardlinkChange() 23:04:51 -
kdirwatch_qfswatch_unittest(19844) - kf5.kcoreaddons.kdirwatch:
KDirWatch::setCreated: "KDirWatch-13" emitting created
"/tmp/kdirwatch_qfswatch_unittest-uaIYOw/ExistingFile"
QDEBUG : KDirWatch_UnitTest::testHardlinkChange() 23:04:51 -
kdirwatch_qfswatch_unittest(19844) -  KDirWatch_UnitTest::waitUntilAfter:
Waited 0 ms so that now "2017-11-16T23:04:51" is > "2017-11-16T23:04:29"
QWARN  : KDirWatch_UnitTest::testHardlinkChange() 23:04:53 -
kdirwatch_qfswatch_unittest(19844) -  : Timeout waiting for KDirWatch signal
"dirty(QString)" ( "/tmp/kdirwatch_qfswatch_unittest-uaIYOw/ExistingFile" )
FAIL!  : KDirWatch_UnitTest::testHardlinkChange() 'waitForOneSignal(watch,
SIGNAL(dirty(QString)), existingFile)' returned FALSE. ()
   Loc:
[/kde/src/5/frameworks/kcoreaddons/autotests/kdirwatch_unittest.cpp(704)]

same failure with kdirwatch_stat_unittest.

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

[konqueror] [Bug 386996] konqueror fails to load http on Mac

2017-11-16 Thread RJVB
https://bugs.kde.org/show_bug.cgi?id=386996

--- Comment #2 from RJVB  ---
Maybe this log message gives a beginning of an explanation?

kf5.kio.widgets: KonqRun(0x7faaee8ceae0) ERROR (stat): 111   "The file or
folder http://www.kde.org/ does not exist."
kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "error"

I'm not seeing either of those on Linux where Konqueror5 works fine.

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

[konversation] [Bug 385959] QCA-QT5.DLL is missing.

2017-11-16 Thread Mike Lothian
https://bugs.kde.org/show_bug.cgi?id=385959

--- Comment #10 from Mike Lothian  ---
The only reason I upgraded was because of the CVE that was announced today

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

[frameworks-kimageformats] [Bug 380382] kimageformats-read-xcf test fails with Qt 5.9

2017-11-16 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=380382

Christophe Giboudeaux  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Christophe Giboudeaux  ---
Same failure with Qt 5.10. and kimageformats from master.

9/14 Testing: kimageformats-read-xcf
9/14 Test: kimageformats-read-xcf
Command: "/kde/build/5/frameworks/kimageformats/bin/readtest" "-f" "1" "xcf"
Directory: /kde/build/5/frameworks/kimageformats/autotests
"kimageformats-read-xcf" start time: Nov 16 22:43 CET
Output:
--
* Starting basic read tests for xcf images *
INFO : simple-bw-gimp-2.8.10.xcf: converting simple-bw-gimp-2.8.10.xcf from
RGB32 to ARGB32
INFO : simple-bw-gimp-2.8.10.xcf: converting simple-bw-gimp-2.8.10.png from
RGB32 to ARGB32
PASS : simple-bw-gimp-2.8.10.xcf
PASS : simple-bwa-gimp-2.8.10.xcf
INFO : simple-rgb-gimp-2.8.10.xcf: converting simple-rgb-gimp-2.8.10.xcf from
RGB32 to ARGB32
INFO : simple-rgb-gimp-2.8.10.xcf: converting simple-rgb-gimp-2.8.10.png from
RGB32 to ARGB32
PASS : simple-rgb-gimp-2.8.10.xcf
FAIL : simple-rgba-gimp-2.8.10.xcf: differs from simple-rgba-gimp-2.8.10.png
   expected data written to simple-rgba-gimp-2.8.10.xcf-expected.data
   actual data written to simple-rgba-gimp-2.8.10.xcf-actual.data
Totals: 3 passed, 1 failed
* Finished basic read tests for xcf images *

Test time =   0.01 sec
--
Test Failed.
"kimageformats-read-xcf" end time: Nov 16 22:43 CET
"kimageformats-read-xcf" time elapsed: 00:00:00
--

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

[frameworks-knewstuff] [Bug 385516] Loading Preview icon stuck

2017-11-16 Thread Rog131
https://bugs.kde.org/show_bug.cgi?id=385516

Rog131  changed:

   What|Removed |Added

 CC||samrog...@hotmail.com

--- Comment #10 from Rog131  ---
(In reply to Robin from comment #9)
> Can I ask when this fix is due to be rolled out please? and if out already
> how do I apply it. Many Thanks in advance

Comment #7: https://bugs.kde.org/show_bug.cgi?id=385516#c7

Fixed with
https://cgit.kde.org/knewstuff.git/commit/?id=c32c8d002e1216373560c94738841a7a5e1b976b

Part of The KDE Frameworks 5.40 - released: https://community.kde.org/Schedules
-> https://community.kde.org/Schedules/Frameworks -> "Sat November 11th, 2017"

Upgrade to the KDE Frameworks 5.40.

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

[kscreenlocker] [Bug 346741] bring back "auto-lock screen on login" option from KDM/Plasma 4

2017-11-16 Thread Holger
https://bugs.kde.org/show_bug.cgi?id=346741

--- Comment #7 from Holger  ---
(In reply to Claus Appel from comment #6)
> Could you please elaborate on why this is not secure? It is not clear to me.

Sure. An unencrypted HDD can either be physically extracted and read / modified
in another PC, that is running it's own operating system. To that other
computer everything on your HDD is just data, no restrictions apply.

The second even easier possibility is, to boot your device from a USB-Stick, in
case you didn't deny this in the BIOS. So the foreign OS is running directly on
your hardware and considers your HDD as plain data.

You can copy *anything* you like, modify it, destroy it. You could leave a
backdoor, change root passwords or create new accounts with root privileges.
You get *full* control over every bit of data written on that disk.

Encryption will protect you: Nobody can read your data and they cannot modify
it or create backdoors. Sure, they can still destroy everything. Encryption
does not replace a regular backup.

At your desktop at home you usually tolerate this kind of thread. You rely on
the security of your house, though an adversary may intrude without you
noticing (got a cleaning lady?). On the other hand a laptop staying behind in a
classroom with 30 bored pupils, while you visit the bathroom ... I wouldn't
take the risk.

A lock screen alone is only a minor deterrent like a sign to plead you, not to
tread on the grass. Encryption can be a nasty fence with barbwire to keep the
evil outside.

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

[kio-extras] [Bug 369850] Can't browse samba workgroups

2017-11-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=369850

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #12 from Nate Graham  ---
Excellent, so glad to hear it! I can't reproduce it, either.

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

[konversation] [Bug 386998] [Wayland] Konversation crash

2017-11-16 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=386998

Christoph Feck  changed:

   What|Removed |Added

Version|1.7.2   |1.6.2

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

[kio-extras] [Bug 369850] Can't browse samba workgroups

2017-11-16 Thread Martin Kostolný
https://bugs.kde.org/show_bug.cgi?id=369850

--- Comment #11 from Martin Kostolný  ---
My comment was actually about inability to connect to some shares (even when
using IP address) after upgrading to samba 4.7.0. That issue got fixed probably
in KDE Apps 17.08.3, and probably by You, Nate, thanks!

So I guess this ticket is about something else and I'm unable to replicate this
particular issue. I should have made my comment here:
https://bugs.kde.org/show_bug.cgi?id=385708/

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

[valgrind] [Bug 386945] Bogus memcheck errors on ppc64(le) when using strcmp() with gcc-7

2017-11-16 Thread Markus Trippelsdorf
https://bugs.kde.org/show_bug.cgi?id=386945

--- Comment #5 from Markus Trippelsdorf  ---
(In reply to Julian Seward from comment #2)
> This is caused by insufficiently precise definedness analysis for
> (1) count leading zero operations (Iop_Clz32, Iop_Clz64)
> (2) PPC integer compares (Iop_CmpORD family)
> (3) integer subtract
> 
> Here's an initial, hacky patch that fixes (1) and (2).  Along with
> use of the flag --expensive-definedness-checks=yes, which fixes (3),
> it makes the test case run quiet.
> 
> Can you give it a try on something larger?

Unfortunately it does't work yet.
I still get "Invalid read of size 4" and "Conditional jump or move depends on
uninitialised value(s)" on many strcmp() invokations.
Plus the patch corrupts memory and gcc ICEs now.
(Testcase is running g++ under valgrind when compiling a small C++ program.)

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

[kdevelop] [Bug 387005] Qt headers fail to parse in some setups, causing errors everywhere

2017-11-16 Thread Sven Brauch
https://bugs.kde.org/show_bug.cgi?id=387005

Sven Brauch  changed:

   What|Removed |Added

  Component|Problem reporter|Language Support: CPP
   ||(Clang-based)

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

[kdevelop] [Bug 387005] Qt headers fail to parse in some setups, causing errors everywhere

2017-11-16 Thread Sven Brauch
https://bugs.kde.org/show_bug.cgi?id=387005

--- Comment #1 from Sven Brauch  ---
Reportedly, changing from "clang" to "gcc" in the "compiler for path" combo box
in the project settings fixes the issue. Anybody knows why?

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

[frameworks-kguiaddons] [Bug 365894] KMail(2) documentation not available

2017-11-16 Thread Colin J Thomson
https://bugs.kde.org/show_bug.cgi?id=365894

Colin J Thomson  changed:

   What|Removed |Added

 CC|colin.thom...@g6avk.co.uk   |

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

[kdevelop] [Bug 387005] Qt headers fail to parse in some setups, causing errors everywhere

2017-11-16 Thread Sven Brauch
https://bugs.kde.org/show_bug.cgi?id=387005

Sven Brauch  changed:

   What|Removed |Added

Summary|Problems in Semantic|Qt headers fail to parse in
   |analysis since version 5.2  |some setups, causing errors
   ||everywhere
 CC||m...@svenbrauch.de

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

[kdevelop] [Bug 387005] New: Problems in Semantic analysis since version 5.2

2017-11-16 Thread Luca Weiss
https://bugs.kde.org/show_bug.cgi?id=387005

Bug ID: 387005
   Summary: Problems in Semantic analysis since version 5.2
   Product: kdevelop
   Version: 5.2.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Problem reporter
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: l...@z3ntu.xyz
  Target Milestone: ---

I get the error

Problem in Semantic analysis
Cannot initialize object parameter of type 'QBoxLayout' with an expression of
type 'QVBoxLayout'

for the line "boxLayout->setAlignment(Qt::AlignTop);" (and many other examples)
in my code.

I'm using cmake if that makes any difference. Source code is located at
https://github.com/z3ntu/RazerGenie, if needed.

Maybe related, but 5.2 also doesn't find "iostream" anymore:

Problem in Semantic analysis
'iostream' file not found

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

[digikam] [Bug 387004] New: Rename on import is inconsistent jpg to raw

2017-11-16 Thread Mick Sulley
https://bugs.kde.org/show_bug.cgi?id=387004

Bug ID: 387004
   Summary: Rename on import is inconsistent jpg to raw
   Product: digikam
   Version: 5.7.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Import-Rename
  Assignee: digikam-bugs-n...@kde.org
  Reporter: m...@sulley.info
  Target Milestone: ---

Running 5.7.0 app bundle on Linux Mint
I have import set to rename on date and time
When I import pictures from my Canon EOS 550D the jpg seem to rename as
expected but the .CR2 files get a different name.
During British Summer Time the difference is one hour and a few seconds, now we
are back on GMT it is just a few seconds.
If I select the .CR2 files which have been imported and select rename, it
renames them to what I expected.  
It would seem that the rename logic is different between .JPG and .CR2
Happy to provide more info or test stuff if it helps
Thanks
Mick

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

[kwin] [Bug 385956] Support idle-inhibit-unstable-v1 protocol

2017-11-16 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=385956

Martin Flöser  changed:

   What|Removed |Added

  Flags||Wayland+, X11-,
   ||ReviewRequest+
URL||https://phabricator.kde.org
   ||/D8856

--- Comment #4 from Martin Flöser  ---
And implementation for KWin in: https://phabricator.kde.org/D8856

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

[krita] [Bug 387003] New: slow

2017-11-16 Thread Elliot Davey
https://bugs.kde.org/show_bug.cgi?id=387003

Bug ID: 387003
   Summary: slow
   Product: krita
   Version: 3.3.2
  Platform: Windows CE
OS: Windows CE
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: elliotuk2...@gmail.com
  Target Milestone: ---

HI there, I am getting into the art industry and found that krita was perfect
for me to start off digital art, but there is a bug that I was hoping that you
could fix. Basically, when I create a new canvas on either animation or paint,
the courser doesn't appear and neither does the sketch until I click one of the
layers. I have uninstalled the program and reinstalled it but the same thing
occurs.

thank you for your time,
Elliot Davey

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

[systemsettings] [Bug 380972] Overlapping labels on front page

2017-11-16 Thread Fabian Vogt
https://bugs.kde.org/show_bug.cgi?id=380972

Fabian Vogt  changed:

   What|Removed |Added

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

--- Comment #5 from Fabian Vogt  ---
Now this is broken for english as well:
https://openqa.opensuse.org/tests/533949#step/systemsettings5/4

User
Manag
er

Screen
lockin
g

...

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

[digikam] [Bug 387000] GPS Longitude Decimalisation Appears Incorrect In Map

2017-11-16 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=387000

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
Send me the image by email.

Maik

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

[digikam] [Bug 385471] Geolocation Editor Opens Map To A Random Location

2017-11-16 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=385471

Maik Qualmann  changed:

   What|Removed |Added

   Version Fixed In||5.8.0

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

[Kubuntu Debug Installer] [Bug 387001] KDE crashes and screen blacks out

2017-11-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=387001

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #1 from Nate Graham  ---
I'm sorry to hear that. However, this is a bug tracker, not a support forum,
and there's no information in this bug that we could use to even troubleshoot
the issue, let alone pinpoint a fixable bug. I would recommend submitting your
question to a support forum such as https://forum.kde.org/ and seek out
assistance there. Once the issue is resolved, you can work with the folks
who've helped you fix it to do some digging and uncover the bug that caused the
problem, if any. If such a bug is revealed, and it's a bug in a product tracked
here in the KDE bug tracker, please don't hesitate to file a new bug report.

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

[Akonadi] [Bug 364802] Kmail stops syncing with an IMAP account

2017-11-16 Thread Michael D
https://bugs.kde.org/show_bug.cgi?id=364802

Michael D  changed:

   What|Removed |Added

 CC||nortex...@gmail.com

--- Comment #9 from Michael D  ---
I had this happen after resuming from suspend sometimes, but now it's happening
much more frequently, to the point of being unusable. Running "akonadictl
restart" fixes it, but only temporarily.

I'm running kmail2 5.6.3.

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

[plasmashell] [Bug 387002] New: Plasma crash on using contact request menu

2017-11-16 Thread André Johansen
https://bugs.kde.org/show_bug.cgi?id=387002

Bug ID: 387002
   Summary: Plasma crash on using contact request menu
   Product: plasmashell
   Version: 5.10.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: andre...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.5)

Qt Version: 5.7.1
Frameworks Version: 5.38.0
Operating System: Linux 4.13.11-200.fc26.i686 i686
Distribution: "Fedora release 26 (Twenty Six)"

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

Had just logged in with the Plasma IM, had some contact requests.  Deleted one,
then tried to open the menu again to delete the others.  Plasma crashed.

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

Thread 11 (Thread 0x8ec9db40 (LWP 1643)):
#0  0xb2a5a056 in g_thread_self () from /lib/libglib-2.0.so.0
#1  0xb2a2d003 in g_main_context_acquire () from /lib/libglib-2.0.so.0
#2  0xb2a2e1da in g_main_context_iterate.isra () from /lib/libglib-2.0.so.0
#3  0xb2a2e7a1 in g_main_loop_run () from /lib/libglib-2.0.so.0
#4  0xb11e319a in gdbus_shared_thread_func () from /lib/libgio-2.0.so.0
#5  0xb2a59a64 in g_thread_proxy () from /lib/libglib-2.0.so.0
#6  0xb4fd22d9 in start_thread () from /lib/libpthread.so.0
#7  0xb527f316 in clone () from /lib/libc.so.6

Thread 10 (Thread 0x8f49eb40 (LWP 1642)):
#0  0xb2a7a3b0 in g_wakeup_acknowledge () from /lib/libglib-2.0.so.0
#1  0xb2a2dde3 in g_main_context_check () from /lib/libglib-2.0.so.0
#2  0xb2a2e2e5 in g_main_context_iterate.isra () from /lib/libglib-2.0.so.0
#3  0xb2a2e4ab in g_main_context_iteration () from /lib/libglib-2.0.so.0
#4  0xb2a2e517 in glib_worker_main () from /lib/libglib-2.0.so.0
#5  0xb2a59a64 in g_thread_proxy () from /lib/libglib-2.0.so.0
#6  0xb4fd22d9 in start_thread () from /lib/libpthread.so.0
#7  0xb527f316 in clone () from /lib/libc.so.6

Thread 9 (Thread 0x9e469b40 (LWP 1596)):
#0  0xb7ef8cd9 in __kernel_vsyscall ()
#1  0xb5273c8f in poll () from /lib/libc.so.6
#2  0xb2a3e91b in g_poll () from /lib/libglib-2.0.so.0
#3  0xb2a2e34e in g_main_context_iterate.isra () from /lib/libglib-2.0.so.0
#4  0xb2a2e4ab in g_main_context_iteration () from /lib/libglib-2.0.so.0
#5  0xb57f32af in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/libQt5Core.so.5
#6  0xb5795880 in QEventLoop::exec(QFlags) ()
from /lib/libQt5Core.so.5
#7  0xb55c3b08 in QThread::exec() () from /lib/libQt5Core.so.5
#8  0x9ebd694e in KCupsConnection::run() () from /lib/libkcupslib.so
#9  0xb55c8eaa in QThreadPrivate::start(void*) () from /lib/libQt5Core.so.5
#10 0xb4fd22d9 in start_thread () from /lib/libpthread.so.0
#11 0xb527f316 in clone () from /lib/libc.so.6

Thread 8 (Thread 0xa622db40 (LWP 1518)):
#0  0xb7ef8cd9 in __kernel_vsyscall ()
#1  0xb7ef8953 in __vdso_clock_gettime ()
#2  0xb528e071 in clock_gettime () from /lib/libc.so.6
#3  0xb565875a in qt_gettime() () from /lib/libQt5Core.so.5
#4  0xb57f15aa in QTimerInfoList::updateCurrentTime() () from
/lib/libQt5Core.so.5
#5  0xb57f1a26 in QTimerInfoList::timerWait(timespec&) () from
/lib/libQt5Core.so.5
#6  0xb57f2ef3 in timerSourcePrepareHelper(GTimerSource*, int*) () from
/lib/libQt5Core.so.5
#7  0xb57f2f87 in timerSourcePrepare(_GSource*, int*) () from
/lib/libQt5Core.so.5
#8  0xb2a2d74d in g_main_context_prepare () from /lib/libglib-2.0.so.0
#9  0xb2a2e242 in g_main_context_iterate.isra () from /lib/libglib-2.0.so.0
#10 0xb2a2e4ab in g_main_context_iteration () from /lib/libglib-2.0.so.0
#11 0xb57f32af in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/libQt5Core.so.5
#12 0xb5795880 in QEventLoop::exec(QFlags) ()
from /lib/libQt5Core.so.5
#13 0xb55c3b08 in QThread::exec() () from /lib/libQt5Core.so.5
#14 0xb7432968 in QQuickPixmapReader::run() () from /lib/libQt5Quick.so.5
#15 0xb55c8eaa in QThreadPrivate::start(void*) () from /lib/libQt5Core.so.5
#16 0xb4fd22d9 in start_thread () from /lib/libpthread.so.0
#17 0xb527f316 in clone () from /lib/libc.so.6

Thread 7 (Thread 0xa83f2b40 (LWP 1465)):
#0  0xb7ef8cd9 in __kernel_vsyscall ()
#1  0xb4fd89dd in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xac245ccc in thread_function () from /usr/lib/dri/swrast_dri.so
#3  0xb4fd22d9 in start_thread () from /lib/libpthread.so.0
#4  0xb527f316 in clone () from /lib/libc.so.6

Thread 6 (Thread 0xa8bf3b40 (LWP 1464)):
#0  0xb7ef8cd9 in __kernel_vsyscall ()
#1  0xb4fd89dd in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xac245ccc in thread_function () from /usr/lib/dri/swrast_dri.so
#3  0xb4fd22d9 in start_thread () from /lib/libpthread.so.0
#4  0xb527f316 in 

[valgrind] [Bug 386945] Bogus memcheck errors on ppc64(le) when using strcmp() with gcc-7

2017-11-16 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=386945

Julian Seward  changed:

   What|Removed |Added

 Attachment #108905|0   |1
is obsolete||

--- Comment #4 from Julian Seward  ---
Created attachment 108906
  --> https://bugs.kde.org/attachment.cgi?id=108906=edit
Initial attempt at a fix

Second attempt, attaching the correct patch this time.

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

[valgrind] [Bug 386945] Bogus memcheck errors on ppc64(le) when using strcmp() with gcc-7

2017-11-16 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=386945

--- Comment #3 from Julian Seward  ---
Created attachment 108905
  --> https://bugs.kde.org/attachment.cgi?id=108905=edit
Initial attempt at a fix

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

[Kubuntu Debug Installer] [Bug 387001] New: KDE crashes and screen blacks out

2017-11-16 Thread Exoalexander
https://bugs.kde.org/show_bug.cgi?id=387001

Bug ID: 387001
   Summary: KDE crashes and screen blacks out
   Product: Kubuntu Debug Installer
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: sit...@kde.org
  Reporter: asv.infin...@icloud.com
  Target Milestone: ---

i just logged into my Laptop and then the sreen goes out and restarts the KDE
Desktop

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

[valgrind] [Bug 386945] Bogus memcheck errors on ppc64(le) when using strcmp() with gcc-7

2017-11-16 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=386945

--- Comment #2 from Julian Seward  ---
This is caused by insufficiently precise definedness analysis for
(1) count leading zero operations (Iop_Clz32, Iop_Clz64)
(2) PPC integer compares (Iop_CmpORD family)
(3) integer subtract

Here's an initial, hacky patch that fixes (1) and (2).  Along with
use of the flag --expensive-definedness-checks=yes, which fixes (3),
it makes the test case run quiet.

Can you give it a try on something larger?

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

[digikam] [Bug 387000] New: GPS Longitude Decimalisation Appears Incorrect In Map

2017-11-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=387000

Bug ID: 387000
   Summary: GPS Longitude Decimalisation Appears Incorrect In Map
   Product: digikam
   Version: 5.8.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Geolocation
  Assignee: digikam-bugs-n...@kde.org
  Reporter: hardy.pub...@gmail.com
  Target Milestone: ---

I have an image (scanned photo) that in all other programs shows the correct
GPS position on a map, but in digiKam it is offset to the East by 1.4km. It's
driving me nuts trying to figure out why.

The EXIF longitude is 1°55'39.71"W. This is -1.9275. However the map view
calculates -1.90652 which is approximately 1.42km too far East.

I cannot re-create the problem but I don't want to post the problem image
publicly. Please let me know how to PM the image to you if you want to
investigate.

Thank you.

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

[kile] [Bug 384665] Kile occasionally segfaults on backward search

2017-11-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=384665

ree...@gmail.com changed:

   What|Removed |Added

 CC||ree...@gmail.com

--- Comment #5 from ree...@gmail.com ---
Using backwards search, the journal shows a complaint from KDirWatch on the
line immediately preceding the segfault.

Tach 16 18:40:55 MyComputer kile[1818]: org.kde.kcoreaddons: KDirWatch: "" is a directory. Use addDir!
Tach 16 18:40:55 MyComputer kernel: kile[1818]: segfault at 98 ip
7f3c0506b9c0 sp 7ffc552e2038 error 4 in
libkdeinit5_kile.so[7f3c04f19000+3db000]
Tach 16 18:40:55 MyComputer systemd[1]: Created slice
system-systemd\x2dcoredump.slice.
Tach 16 18:40:55 MyComputer systemd[1]: Started Process Core Dump (PID
10102/UID 0).
Tach 16 18:40:56 MyComputer kwin_x11[1208]: QXcbConnection: XCB error: 3
(BadWindow), sequence: 34509, resource id: 67108877, major code: 15
(QueryTree), minor code: 0
Tach 16 18:40:56 MyComputer systemd-coredump[10103]: Process 1818 (kile) of
user 1000 dumped core.

 Stack trace of thread
1818:
 #0  0x7f3c0506b9c0
n/a (libkdeinit5_kile.so)
 #1  0x7f3c050cabd2
n/a (libkdeinit5_kile.so)
 #2  0x7f3c050cb24b
n/a (libkdeinit5_kile.so)
 #3  0x7f3c050cb441
n/a (libkdeinit5_kile.so)
 #4  0x7f3c050a2182
n/a (libkdeinit5_kile.so)
 #5  0x7f3c05207a4a
n/a (libkdeinit5_kile.so)
 #6  0x7f3bffca7abd
n/a (libQt5DBus.so.5)
 #7  0x7f3bffcacf29
n/a (libQt5DBus.so.5)
 #8  0x7f3bffcad4f8
n/a (libQt5DBus.so.5)
 #9  0x7f3bffcafd0e
n/a (libQt5DBus.so.5)
 #10 0x7f3bfe897662
_ZN7QObject5eventEP6QEvent (libQt5Core.so.5)
 #11 0x7f3bff5c513c
_ZN7QWidget5eventEP6QEvent (libQt5Widgets.so.5)
 #12 0x7f3bff6dd264
_ZN11QMainWindow5eventEP6QEvent (libQt5Widgets.so.5)
 #13 0x7f3c023533bb
_ZN11KMainWindow5eventEP6QEvent (libKF5XmlGui.so.5)
 #14 0x7f3c023a4ca6
_ZN13KXmlGuiWindow5eventEP6QEvent (libKF5XmlGui.so.5)
 #15 0x7f3bff584f2c
_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5)
 #16 0x7f3bff58ca06
_ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5)
 #17 0x7f3bfe867060
_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5)
 #18 0x7f3bfe8698b6
_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData
(libQt5Core.so.5)
 #19 0x7f3bfe8c26e4
n/a (libQt5Core.so.5)
 #20 0x7f3bf6cad270
g_main_context_dispatch (libglib-2.0.so.0)
 #21 0x7f3bf6caef69
n/a (libglib-2.0.so.0)
 #22 0x7f3bf6caefae
g_main_context_iteration (libglib-2.0.so.0)
 #23 0x7f3bfe8c1cd1
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5)
 #24 0x7f3bfe86548b
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
 #25 0x7f3bfe86e4d8
_ZN16QCoreApplication4execEv (libQt5Core.so.5)
 #26 0x7f3c05150d94
kdemain (libkdeinit5_kile.so)
 #27 0x7f3c04b81f6a
__libc_start_main (libc.so.6)
 #28 0x560f585b776a
_start (kile)

 Stack trace of thread
1819:
 #0  0x7f3c04c4cf7b
__poll (libc.so.6)
 

[k3b] [Bug 386983] Refresh button in the Programs section causes segfault

2017-11-16 Thread Dr . Chapatin
https://bugs.kde.org/show_bug.cgi?id=386983

Dr. Chapatin  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[kscreenlocker] [Bug 346741] bring back "auto-lock screen on login" option from KDM/Plasma 4

2017-11-16 Thread Claus Appel
https://bugs.kde.org/show_bug.cgi?id=346741

Claus Appel  changed:

   What|Removed |Added

 CC||spectru...@gmail.com

--- Comment #6 from Claus Appel  ---
(In reply to Holger from comment #3)
> Erm ... without a hard-drive encryption requesting a lockscreen-password is
> only a little distraction on the way to capture your system. Especially on a
> mobile device, that may get lost/stolen.

Could you please elaborate on why this is not secure? It is not clear to me.
Thanks.

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

[kwin] [Bug 386043] Switch window between same application sometimes does not work.

2017-11-16 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=386043

Martin Flöser  changed:

   What|Removed |Added

   Version Fixed In||5.11.4
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/kwi
   ||n/1ae7990a959ce2c3fad0a6aef
   ||684cf058b07cf1e

--- Comment #10 from Martin Flöser  ---
Git commit 1ae7990a959ce2c3fad0a6aef684cf058b07cf1e by Martin Flöser.
Committed on 16/11/2017 at 19:33.
Pushed by graesslin into branch 'Plasma/5.11'.

Allow a cross-process check for same applications

Summary:
Commit 5d9027b110 introduced a regression in TabBox by using the generic
framework inside KWin to test for same application. What I did not
consider was that the code in TabBox was "broken by design". It didn't
use the generic check as that is too strict and considers windows from
different processes as not belonging to the same application. But this
is not wanted in the case of TabBox.

On the other hand the change itself is an improvement to also support
Wayland in a better way and not have special handling situations. Thus
just reverting would not help.

Instead this change addresses the problem by extending the internal API
and to allow more adjustements. So far there was already an
"active_hack" boolean flag. This is extended to proper flags with an
additional flag to allow cross application checks.

The checks in Client which would filter out different applications check
for this flag and are skipped if set. In addition ShellClient also adds
support for this flag and compares for the desktop file name.

Thus we get in TabBox the same behavior as before with the advantage of
having a better shared code base working on both X11 and Wayland.
FIXED-IN: 5.11.4

Test Plan:
Started two kwrite processes on X11, clicked new in one of them,
used Alt+` and verified that there are three windows shown.

Reviewers: #kwin, #plasma

Subscribers: plasma-devel, kwin

Tags: #kwin

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

M  +2-2abstract_client.cpp
M  +8-4abstract_client.h
M  +4-4activation.cpp
M  +2-2client.cpp
M  +2-2client.h
M  +6-4group.cpp
M  +7-3shell_client.cpp
M  +1-1shell_client.h
M  +2-2tabbox/tabbox.cpp

https://commits.kde.org/kwin/1ae7990a959ce2c3fad0a6aef684cf058b07cf1e

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

[Spectacle] [Bug 376350] Screenshots of single window can be sized wrongly

2017-11-16 Thread Dr . Chapatin
https://bugs.kde.org/show_bug.cgi?id=376350

Dr. Chapatin  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[kwin] [Bug 385956] Support idle-inhibit-unstable-v1 protocol

2017-11-16 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=385956

Martin Flöser  changed:

   What|Removed |Added

  Component|server  |wayland-generic
Product|frameworks-kwayland |kwin
   Assignee|mgraess...@kde.org  |kwin-bugs-n...@kde.org
Version|5.39.0  |git master

--- Comment #3 from Martin Flöser  ---
Moving back to KWin for further implementation

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

[frameworks-kwayland] [Bug 385956] Support idle-inhibit-unstable-v1 protocol

2017-11-16 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=385956

--- Comment #2 from Martin Flöser  ---
Git commit 9520c2f292d0ac7bae98e96b9e067dfa25cb828f by Martin Flöser.
Committed on 16/11/2017 at 19:22.
Pushed by graesslin into branch 'master'.

Add support for zwp_idle_inhibit_manager_v1

Summary:
This protocol allows to indicate that a wl_surface should inhibit idle
actions such as DPMS, screen locking if the surface is visible.

The protocol is quite simple: it just creates an IdleInhibitor for a
Surface. If such an IdleInhibitor exists the Surface is considered to
inhibit idle.

On the server side it is also exposed like that through the API. The
IdleInhibitorInterface is private to the library and only
SurfaceInterface is extended to expose whether it currently inhibits
idle.

Test Plan: New test case added

Reviewers: #frameworks, #kwin, #plasma_on_wayland

Subscribers: plasma-devel

Tags: #plasma_on_wayland, #frameworks

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

M  +31   -0autotests/client/test_wayland_registry.cpp
M  +63   -0autotests/client/test_wayland_surface.cpp
M  +6-0src/client/CMakeLists.txt
A  +176  -0src/client/idleinhibit.cpp [License: BSD]
A  +217  -0src/client/idleinhibit.h [License: BSD]
A  +83   -0src/client/protocols/idle-inhibit-unstable-v1.xml
M  +20   -0src/client/registry.cpp
M  +44   -1src/client/registry.h
M  +8-0src/server/CMakeLists.txt
M  +13   -0src/server/display.cpp
M  +11   -0src/server/display.h
A  +53   -0src/server/idleinhibit_interface.cpp [License: BSD]
A  +77   -0src/server/idleinhibit_interface.h [License: BSD]
A  +96   -0src/server/idleinhibit_interface_p.h [License: BSD]
A  +139  -0src/server/idleinhibit_interface_v1.cpp [License: BSD]
M  +23   -0src/server/surface_interface.cpp
M  +16   -0src/server/surface_interface.h
M  +4-0src/server/surface_interface_p.h
M  +2-0src/tools/mapping.txt

https://commits.kde.org/kwayland/9520c2f292d0ac7bae98e96b9e067dfa25cb828f

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

[kdenlive] [Bug 386932] Audio playback is different pitch & not smooth.

2017-11-16 Thread Jesse
https://bugs.kde.org/show_bug.cgi?id=386932

--- Comment #4 from Jesse  ---
Thanks JB. No rush. If Appimages can be solid enough as native installs, this
can be a huge leap for Kdenlive.

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

[konversation] [Bug 386998] [Wayland] Konversation crash

2017-11-16 Thread Germano Massullo
https://bugs.kde.org/show_bug.cgi?id=386998

--- Comment #1 from Germano Massullo  ---
Created attachment 108904
  --> https://bugs.kde.org/attachment.cgi?id=108904=edit
GDB backtrace

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

[konversation] [Bug 386998] New: [Wayland] Konversation crash

2017-11-16 Thread Germano Massullo
https://bugs.kde.org/show_bug.cgi?id=386998

Bug ID: 386998
   Summary: [Wayland] Konversation crash
   Product: konversation
   Version: 1.7.2
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konversation-de...@kde.org
  Reporter: germano.massu...@gmail.com
CC: k...@davidedmundson.co.uk, plasma-b...@kde.org,
rdie...@gmail.com
  Target Milestone: ---

Created attachment 108903
  --> https://bugs.kde.org/attachment.cgi?id=108903=edit
konversation console output

I triggered this crash by testing Bug #378708 on new 5.9.2 Qt. Since the
crashreport seems a bit different, in the dubt, I am creating a new bugreport


+++ This bug was initially created as a clone of Bug #378708 +++

Konversation 1.6.2 crashes on Wayland.
Video driver: amdgpu


$ gdb konversation
GNU gdb (GDB) Fedora 7.12.1-47.fc25
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from konversation...Reading symbols from
/usr/lib/debug/usr/bin/konversation.debug...done.
done.
(gdb) run
Starting program: /usr/bin/konversation 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
QObject::connect: invalid null parameter
[New Thread 0x7fffdaabc700 (LWP 23080)]
[New Thread 0x7fffd96a5700 (LWP 23081)]
[New Thread 0x7fffd1216700 (LWP 23083)]
[New Thread 0x7fffd0810700 (LWP 23084)]
[New Thread 0x7fffc947c700 (LWP 23085)]
[New Thread 0x7fffc8c7b700 (LWP 23086)]
[New Thread 0x7fffc847a700 (LWP 23087)]
[New Thread 0x7fffc45a9700 (LWP 23088)]
[New Thread 0x7fffc3b59700 (LWP 23089)]
[New Thread 0x7fffc3356700 (LWP 23090)]
[New Thread 0x7fffc2b55700 (LWP 23091)]
[New Thread 0x7fffc2354700 (LWP 23092)]


[Thread 0x7fffc3356700 (LWP 23090) exited]
[Thread 0x7fffc2354700 (LWP 23092) exited]
[Thread 0x7fffc3b59700 (LWP 23089) exited]
[Thread 0x7fffc45a9700 (LWP 23088) exited]
[Thread 0x7fffc2b55700 (LWP 23091) exited]
sonnet.core: No language dictionaries for the language: "it"
The Wayland connection broke. Did the Wayland compositor die?

Thread 2 "QDBusConnection" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffdaabc700 (LWP 23080)]
0x71b79f8d in QObject::disconnect (sender=0x7fffcc004ed0,
signal=signal@entry=0x0, receiver=receiver@entry=0x7fffd4011cc0,
method=method@entry=0x0) at kernel/qobject.cpp:2956
2956const QMetaObject *smeta = sender->metaObject();
(gdb) thread apply all backtrace

Thread 8 (Thread 0x7fffc847a700 (LWP 23087)):
#0  0x7fffef984460 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fffd26d4c5b in cnd_wait (mtx=0x5607aa78, cond=0x5607aaa0) at
../../../include/c11/threads_posix.h:159
#2  0x7fffd26d4c5b in util_queue_thread_func
(input=input@entry=0x55f620b0) at util/u_queue.c:76
#3  0x7fffd26d4ab7 in impl_thrd_routine (p=) at
../../../include/c11/threads_posix.h:87
#4  0x7fffef97e6ca in start_thread (arg=0x7fffc847a700) at
pthread_create.c:333
#5  0x70da0f7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 7 (Thread 0x7fffc8c7b700 (LWP 23086)):
#0  0x7fffef984460 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fffd26d4c5b in cnd_wait (mtx=0x5607aa78, cond=0x5607aaa0) at
../../../include/c11/threads_posix.h:159
#2  0x7fffd26d4c5b in util_queue_thread_func
(input=input@entry=0x55f620b0) at util/u_queue.c:76
#3  0x7fffd26d4ab7 in impl_thrd_routine (p=) at
../../../include/c11/threads_posix.h:87
#4  0x7fffef97e6ca in start_thread (arg=0x7fffc8c7b700) at
pthread_create.c:333
#5  0x70da0f7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 6 (Thread 0x7fffc947c700 (LWP 23085)):
#0  0x7fffef984460 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fffd26d4c5b in cnd_wait (mtx=0x5607aa78, cond=0x5607aaa0) at
../../../include/c11/threads_posix.h:159
#2  0x7fffd26d4c5b in util_queue_thread_func
(input=input@entry=0x55f620b0) at util/u_queue.c:76
#3  0x7fffd26d4ab7 in impl_thrd_routine (p=) 

[Discover] [Bug 386999] New: Discover crash

2017-11-16 Thread nancy
https://bugs.kde.org/show_bug.cgi?id=386999

Bug ID: 386999
   Summary: Discover crash
   Product: Discover
   Version: 5.10.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: nnc@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.10.5)

Qt Version: 5.9.2
Frameworks Version: 5.38.0
Operating System: Linux 4.13.12-200.fc26.x86_64+debug x86_64
Distribution: "Fedora release 26 (Twenty Six)"

-- Information about the crash:
- What I was doing when the application crashed: I was searching for the
application Feddy. It crashed the first time but not the second & third time I
searched.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1b1afad8c0 (LWP 1938))]

Thread 12 (Thread 0x7f1ab700 (LWP 1953)):
#0  0x7f1b160bfd2d in poll () at /lib64/libc.so.6
#1  0x7f1b0f568579 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f1b0f56868c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f1b16ee749b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f1b16e9522a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f1b16ce699a in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f1b16ceac72 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7f1b14c3136d in start_thread () at /lib64/libpthread.so.0
#8  0x7f1b160cbe1f in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7f1ad4d1f700 (LWP 1951)):
#0  0x7f1b14c37e0a in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f1b16ceb2c3 in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f1b16ce7cdf in QThreadPoolThread::run() () at /lib64/libQt5Core.so.5
#3  0x7f1b16ceac72 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#4  0x7f1b14c3136d in start_thread () at /lib64/libpthread.so.0
#5  0x7f1b160cbe1f in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7f1ad64b5700 (LWP 1950)):
#0  0x7f1b160bfd2d in poll () at /lib64/libc.so.6
#1  0x7f1b0f568579 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f1b0f56868c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f1b16ee749b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f1b16e9522a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f1b16ce699a in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f1b16ceac72 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7f1b14c3136d in start_thread () at /lib64/libpthread.so.0
#8  0x7f1b160cbe1f in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7f1ad6cb6700 (LWP 1949)):
#0  0x7f1b160bfd2d in poll () at /lib64/libc.so.6
#1  0x7f1b0f568579 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f1b0f56868c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f1b16ee749b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f1b16e9522a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f1b16ce699a in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f1b16ceac72 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7f1b14c3136d in start_thread () at /lib64/libpthread.so.0
#8  0x7f1b160cbe1f in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f1ad74b7700 (LWP 1946)):
#0  0x7f1b0f5ad4a4 in g_mutex_unlock () at /lib64/libglib-2.0.so.0
#1  0x7f1b0f567f19 in g_main_context_check () at /lib64/libglib-2.0.so.0
#2  0x7f1b0f568520 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#3  0x7f1b0f568912 in g_main_loop_run () at /lib64/libglib-2.0.so.0
#4  0x7f1adeb42db6 in gdbus_shared_thread_func () at /lib64/libgio-2.0.so.0
#5  0x7f1b0f58f516 in g_thread_proxy () at /lib64/libglib-2.0.so.0
#6  0x7f1b14c3136d in start_thread () at /lib64/libpthread.so.0
#7  0x7f1b160cbe1f in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f1ad7cb8700 (LWP 1945)):
#0  0x7f1b160bfd2d in poll () at /lib64/libc.so.6
#1  0x7f1b0f568579 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f1b0f56868c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f1b0f5686d1 in glib_worker_main () at /lib64/libglib-2.0.so.0
#4  0x7f1b0f58f516 in g_thread_proxy () at /lib64/libglib-2.0.so.0
#5  0x7f1b14c3136d in start_thread () at /lib64/libpthread.so.0
#6  0x7f1b160cbe1f in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f1ae7bda700 (LWP 1944)):
#0  

[digikam] [Bug 386959] Properties view: wrong creation date [patch]

2017-11-16 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=386959

Maik Qualmann  changed:

   What|Removed |Added

Summary|Properties view: wrong  |Properties view: wrong
   |creation date   |creation date [patch]

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

[digikam] [Bug 386959] Properties view: wrong creation date

2017-11-16 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=386959

--- Comment #11 from Maik Qualmann  ---
Created attachment 108902
  --> https://bugs.kde.org/attachment.cgi?id=108902=edit
xmpdatetime.patch

Here is the conversion table:

http://www.exiv2.org/conversion.html

Gilles, are you really sure that the Exif tags Exif.Photo.DateTimeOriginal or
Exif.Photo.DateTimeDigitized exist in an XMP sidcar file?

I think these are Xmp.exif.DateTimeOriginal and Xmp.exif.DateTimeDigitized.

I once attached a patch to test and discuss. For me, the Exiv2 conversion is
wrong, but maybe there is a standard for it?

Maik

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

[systemsettings] [Bug 386997] Systemsettings crashed by searching

2017-11-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=386997

isa-...@gmx.de changed:

   What|Removed |Added

Summary|System settings window  |Systemsettings crashed by
   |crashed by searching|searching

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

[systemsettings] [Bug 386997] System settings window crashed by searching

2017-11-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=386997

isa-...@gmx.de changed:

   What|Removed |Added

 CC||isa-...@gmx.de

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

[systemsettings] [Bug 386997] New: System settings window crashed by searching

2017-11-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=386997

Bug ID: 386997
   Summary: System settings window  crashed by searching
   Product: systemsettings
   Version: 5.11.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: isa-...@gmx.de
  Target Milestone: ---

Application: systemsettings5 (5.11.3)

Qt Version: 5.9.1
Frameworks Version: 5.39.0
Operating System: Linux 4.13.0-16-generic x86_64
Distribution: Ubuntu 17.10

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

Opened the system settings and typed "wallpaper" in the search field very
quickly; however while typing (and simultaneously searching) the system
settings crashed. Could reproduce it four times; however it does not always
happen. Maby it's a race condition.

The crash can be reproduced every time.

-- Backtrace:
Application: Systemeinstellungen (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4a7982cd80 (LWP 21086))]

Thread 12 (Thread 0x7f4a1d3a4700 (LWP 21126)):
#0  0x7f4a754b2901 in __GI___poll (fds=0x55691aa067a0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f4a6f3e8169 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f4a6f3e8502 in g_main_loop_run () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f4a0b8f8b26 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x7f4a6f40f645 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f4a712a77fc in start_thread (arg=0x7f4a1d3a4700) at
pthread_create.c:465
#6  0x7f4a754beb0f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 11 (Thread 0x7f4a177ff700 (LWP 21125)):
#0  0x7f4a754b2901 in __GI___poll (fds=0x55691d0d4610, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f4a6f3e8169 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f4a6f3e827c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f4a6f3e82c1 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f4a6f40f645 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f4a712a77fc in start_thread (arg=0x7f4a177ff700) at
pthread_create.c:465
#6  0x7f4a754beb0f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 10 (Thread 0x7f4a24fb4700 (LWP 21113)):
#0  0x7f4a75df0b40 in QTimerInfoList::repairTimersIfNeeded() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7f4a75df0bd3 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f4a75df220e in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f4a6f3e76a8 in g_main_context_prepare () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f4a6f3e809b in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f4a6f3e827c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f4a75df249b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f4a75d97e3a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f4a75bb73ca in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f4a73c6bf45 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#10 0x7f4a75bbc29d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f4a712a77fc in start_thread (arg=0x7f4a24fb4700) at
pthread_create.c:465
#12 0x7f4a754beb0f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 9 (Thread 0x7f4a2e1ef700 (LWP 21109)):
#0  0x7f4a754cd96b in __GI___clock_gettime (clock_id=,
tp=) at ../sysdeps/unix/clock_gettime.c:134
#1  0x7f4a75df1db1 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f4a75df05e9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f4a75df0bc5 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f4a75df220e in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f4a6f3e76a8 in g_main_context_prepare () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f4a6f3e809b in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f4a6f3e827c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f4a75df249b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f4a75d97e3a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f4a75bb73ca in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f4a73c6bf45 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#12 0x7f4a75bbc29d in  () at 

  1   2   >