[parley] [Bug 468591] Window does not repaint under wayland

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/educ |https://invent.kde.org/educ
   |ation/parley/-/commit/5e2f7 |ation/parley/-/commit/2c730
   |0bf149515a7e7d087a8b1449bf2 |388a14fe6dbd303f2e345efeeea
   |4d822c5e|28bb1b6b

--- Comment #5 from Andreas Cord-Landwehr  ---
Git commit 2c730388a14fe6dbd303f2e345efeeea28bb1b6b by Andreas Cord-Landwehr.
Committed on 18/02/2024 at 14:38.
Pushed by cordlandwehr into branch 'master'.

Fix window updates on wayland

This refactors all (wrongly) used KXmlGuiWindow objects to be just
QWidgets. This avoids wrong calls to winid() which leads to severe
window render update misses.

M  +23   -17   src/parleymainwindow.cpp
M  +2-3src/parleymainwindow.h

https://invent.kde.org/education/parley/-/commit/2c730388a14fe6dbd303f2e345efeeea28bb1b6b

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

[parley] [Bug 468591] Window does not repaint under wayland

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 CC||thebluequa...@mailo.com

--- Comment #4 from Andreas Cord-Landwehr  ---
*** Bug 459934 has been marked as a duplicate of this bug. ***

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

[parley] [Bug 459934] Parley (native package) editor rendering of collection spreadsheets is highly glitchy on Wayland

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||cordlandw...@kde.org
 Status|REPORTED|RESOLVED

--- Comment #1 from Andreas Cord-Landwehr  ---


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

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

[parley] [Bug 468591] Window does not repaint under wayland

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/educ
   ||ation/parley/-/commit/5e2f7
   ||0bf149515a7e7d087a8b1449bf2
   ||4d822c5e

--- Comment #3 from Andreas Cord-Landwehr  ---
Git commit 5e2f70bf149515a7e7d087a8b1449bf24d822c5e by Andreas Cord-Landwehr.
Committed on 18/02/2024 at 14:50.
Pushed by cordlandwehr into branch 'release/24.02'.

Fix window updates on wayland

This refactors all (wrongly) used KXmlGuiWindow objects to be just
QWidgets. This avoids wrong calls to winid() which leads to severe
window render update misses.

M  +23   -17   src/parleymainwindow.cpp
M  +2-3src/parleymainwindow.h

https://invent.kde.org/education/parley/-/commit/5e2f70bf149515a7e7d087a8b1449bf24d822c5e

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

[parley] [Bug 468591] Window does not repaint under wayland

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 CC||temporary-address@yopmail.c
   ||om

--- Comment #2 from Andreas Cord-Landwehr  ---
*** Bug 469716 has been marked as a duplicate of this bug. ***

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

[parley] [Bug 469716] Parley lags when editing a list

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #3 from Andreas Cord-Landwehr  ---


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

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

[parley] [Bug 468591] Window does not repaint under wayland

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 CC||cordlandw...@kde.org

--- Comment #1 from Andreas Cord-Landwehr  ---
A temporary solution until we find a fix, you can run parley with "-platform
xcb" to workaround this problem. The actual problems seems to be quite deep in
the render stack and might need some time to fix/cannot be fixed in Parley
alone.

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

[parley] [Bug 469716] Parley lags when editing a list

[Andreas Cord-Landwehr]

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

--- Comment #2 from Andreas Cord-Landwehr  ---
A temporary solution until we find a fix, you can run parley with "-platform
xcb" to workaround this problem. The actual problems seems to be quite deep in
the render stack and might need some time to fix/cannot be fixed in Parley
alone.

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

[parley] [Bug 469716] Parley lags when editing a list

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 CC||cordlandw...@kde.org

--- Comment #1 from Andreas Cord-Landwehr  ---
I was able to reproduce the named behavior when running in a Wayland session
(actually, only when running on Wayland an never on X11).
Can you confirm that you had a Wayland session running when you noticed this
behavior?

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

[Akonadi] [Bug 472282] Kolab Now reports too many open connections

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from Andreas Cord-Landwehr  ---
@heinz, yesterday at FOSDEM I ran into Christoph Molenkopf. On Kolab side they
were able to reproduce a crash in their IMAP servers coming from the specific
sequence sent by Kontact/Akonadi and apparently could fix it. On my side I do
not see this issue anymore and thus would close the defect. Please reopen, if
you see it different.

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

[Akonadi] [Bug 472282] Kolab Now reports too many open connections

[Andreas Cord-Landwehr]

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

--- Comment #3 from Andreas Cord-Landwehr  ---
OK, I found a horrible workaround to not trigger this error: I did a local
patch that filters the "METADATA" capability out of the announced IMAP server
capabilities (before handing them over to KMail) and it seems to work well in
terms of not leading to infinite server answers. At the downside, obviously
this IMAP feature is not functional anymore.
The important insight though is that it further pins the problem to the sever
side handling it GETMEATADATA requests.

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

[Akonadi] [Bug 472282] Kolab Now reports too many open connections

[Andreas Cord-Landwehr]

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

--- Comment #2 from Andreas Cord-Landwehr  ---
After some more debug outputs, essentially uncommenting the GOT/SENT debug
lines in getmetadatajob.cpp and increasing the debug level to debug for kimap,
I am very sure that the Kolab server behaves in a way that some calls to
"GETMETADATA (DEPTH infinity)" never are answered and thus the socket timeout
is hit. What is quite interesting, in the same IMAP session the exact same
call, eg

C: A08 GETMETADATA (DEPTH infinity) "KDE/Community" (/shared)
S: * METADATA KDE/Community ( /shared/vendor/cmu/cyrus-imapd/server
imapb036.mykolab.com )
S: A08 OK Completed

at one point succeeds and a few seconds later

C: A15 GETMETADATA (DEPTH infinity) "KDE/Community" (/shared)

never is answered (I modified getmetadatajob such that timeout is set to
infinity and now after waiting 15 minutes, I am very sure that the sever never
will answer).
@heinz, do you see the same behavior?
With my limited IMAP knowledge, as far as I can see, here is not much that can
be done on the client Akonadi side other than some crude hacks that retry the
getmetadatajob once a socket timeout is reached instead of tearing down the
full connection.

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

[Akonadi] [Bug 472282] Kolab Now reports too many open connections

[Andreas Cord-Landwehr]

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

--- Comment #1 from Andreas Cord-Landwehr  ---
I had a slightly deeper look into this issue because I can also reproduce this
behavior with the Kolabnow.com server:
Using the KIMAP_LOGFILE logging option when restarting Akonadi I monitored the
socket disconnects and in every single connection loss I see a "GETMETADATA
(DEPTH infinity) operation as last operation before losing connection, here one
example log tail:

[...]
S: * OK Ok [ ANNOTATIONS 65536  ]
S: A10 OK Completed [ READ-WRITE  ]
C: A11 UID FETCH 1:26193 (FLAGS UID) (CHANGEDSINCE 39247)
S: * 24503 FETCH ( FLAGS (\Seen) UID 26164 MODSEQ (39273) )
S: * 24504 FETCH ( FLAGS (\Seen) UID 26165 MODSEQ (39271) )
S: * 24505 FETCH ( FLAGS (\Seen) UID 26166 MODSEQ (39272) )
S: * 24506 FETCH ( FLAGS (\Seen) UID 26167 MODSEQ (39274) )
S: * 24507 FETCH ( FLAGS (\Seen) UID 26168 MODSEQ (39270) )
S: * 24508 FETCH ( FLAGS (\Seen) UID 26169 MODSEQ (39269) )
S: * 24509 FETCH ( FLAGS (\Seen) UID 26170 MODSEQ (39267) )
S: * 24510 FETCH ( FLAGS (\Seen) UID 26171 MODSEQ (39268) )
S: * 24511 FETCH ( FLAGS (\Seen) UID 26172 MODSEQ (39266) )
S: * 24512 FETCH ( FLAGS (\Seen) UID 26173 MODSEQ (39276) )
S: * 24513 FETCH ( FLAGS (\Seen) UID 26174 MODSEQ (39260) )
S: * 24514 FETCH ( FLAGS (\Seen) UID 26175 MODSEQ (39264) )
S: * 24515 FETCH ( FLAGS (\Seen) UID 26176 MODSEQ (39275) )
S: * 24516 FETCH ( FLAGS (\Seen) UID 26177 MODSEQ (39265) )
S: * 24517 FETCH ( FLAGS (\Seen) UID 26178 MODSEQ (39257) )
S: * 24518 FETCH ( FLAGS (\Seen) UID 26179 MODSEQ (39263) )
S: * 24519 FETCH ( FLAGS (\Seen) UID 26180 MODSEQ (39261) )
S: * 24520 FETCH ( FLAGS (\Seen) UID 26181 MODSEQ (39258) )
S: * 24521 FETCH ( FLAGS (\Seen) UID 26182 MODSEQ (39259) )
S: * 24522 FETCH ( FLAGS (\Seen) UID 26183 MODSEQ (39256) )
S: * 24523 FETCH ( FLAGS (\Seen) UID 26184 MODSEQ (39262) )
S: * 24524 FETCH ( FLAGS (\Seen) UID 26185 MODSEQ (39255) )
S: * 24525 FETCH ( FLAGS (\Seen) UID 26186 MODSEQ (39250) )
S: * 24526 FETCH ( FLAGS (\Seen) UID 26187 MODSEQ (39251) )
S: * 24527 FETCH ( FLAGS (\Seen) UID 26188 MODSEQ (39252) )
S: * 24528 FETCH ( FLAGS (\Seen) UID 26189 MODSEQ (39253) )
S: * 24529 FETCH ( FLAGS (\Seen) UID 26190 MODSEQ (39248) )
S: * 24530 FETCH ( FLAGS (\Seen) UID 26191 MODSEQ (39254) )
S: * 24531 FETCH ( FLAGS (\Seen) UID 26192 MODSEQ (39249) )
S: A11 OK Completed ( 0.001 sec )
C: A12 GETMETADATA (DEPTH infinity) "KDE/Devel" (/shared)
X

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

[Akonadi] [Bug 472282] Kolab Now reports too many open connections

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 CC||cordlandw...@kde.org

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

[parley] [Bug 339183] Dashboard is too large for the screen because collection icons are unnecessarily placed in two rows

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||cordlandw...@kde.org
 Resolution|WORKSFORME  |---
 Status|RESOLVED|REOPENED

--- Comment #7 from Andreas Cord-Landwehr  ---
Checked and confirmed that this issue is still present.

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

[kjournald] [Bug 462053] Can't unselect a Priority to see all.

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://invent.kde.org/syst
   ||em/kjournald/commit/e421cd2
   ||92693e210d9a60d64deb098d252
   ||711ef6

--- Comment #3 from Andreas Cord-Landwehr  ---
Git commit e421cd292693e210d9a60d64deb098d252711ef6 by Andreas Cord-Landwehr.
Committed on 20/11/2022 at 17:12.
Pushed by cordlandwehr into branch 'master'.

Add option to fully disable priority filtering

M  +16   -4lib/filtercriteriamodel.cpp
M  +2-2lib/filtercriteriamodel_p.h
M  +8-4lib/journaldviewmodel.cpp
M  +1-1lib/journaldviewmodel_p.h

https://invent.kde.org/system/kjournald/commit/e421cd292693e210d9a60d64deb098d252711ef6

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

[kjournald] [Bug 462053] Can't unselect a Priority to see all.

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

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

[kjournald] [Bug 462053] Can't unselect a Priority to see all.

[Andreas Cord-Landwehr]

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

--- Comment #1 from Andreas Cord-Landwehr  ---
Thanks for the report! I checked and can confirm that I also see journald log
entries with missing PRIORITY data fields, which fully explains this problem. I
will add a further priority level "no filter" to disable priority filtering.
IMO it is more convenient to have radio buttons than to unselect multiple
levels for fast error filtering.

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

[parley] [Bug 413720] Parley crashes when I try to start practice with a certain file

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/educ
   ||ation/parley/commit/de1b5af
   ||c4976a0efa9dd3264330b49b9ff
   ||65caf6
 Resolution|--- |FIXED
 Status|REOPENED|RESOLVED

--- Comment #7 from Andreas Cord-Landwehr  ---
Git commit de1b5afc4976a0efa9dd3264330b49b9ff65caf6 by Andreas Cord-Landwehr.
Committed on 30/10/2022 at 08:13.
Pushed by cordlandwehr into branch 'master'.

Fix document update race conditions in model updates

The StatisticsModel requires both an updated KVocDocument and an updated
set of selected languages before being able to answer model request
correctly. This change ensures that for invalid combinations no
out-of-bounds access is performed.

M  +9-0src/statistics/statisticsmodel.cpp

https://invent.kde.org/education/parley/commit/de1b5afc4976a0efa9dd3264330b49b9ff65caf6

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

[parley] [Bug 413720] Parley crashes when I try to start practice with a certain file

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 CC||cordlandw...@kde.org
 Resolution|WORKSFORME  |---
 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1

--- Comment #6 from Andreas Cord-Landwehr  ---
I am sorry, it seems that this bug slipped through triaging. I just had a look
and can reproduce it with the described steps.
Thank your for the very detailed bug report and analysis!

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

[Rocs] [Bug 448164] After clicking on Rocs app icon in KDE neon user everytime, it crashes everytime.

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 CC||cordlandw...@kde.org

--- Comment #1 from Andreas Cord-Landwehr  ---
Thank you for your report! It would be great, if you could use a little bit
more and attach the log messages produced by Rocs from the moments before this
crash happens. The easier way is to open a console application (eg. "Konsole"),
write "rocs" and press enter. I would like to see all messages following this
command.

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

[frameworks-kunitconversion] [Bug 441337] Krunner currency conversion plugin cannot be triggered until a dotfile is removed

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/fram |https://invent.kde.org/fram
   |eworks/kunitconversion/comm |eworks/kunitconversion/comm
   |it/6e41104426a3ae59bcb90be7 |it/2a57f9d1c6b2f8d9e2babcda
   |08abcc3092155436|ca66f1cf2a3c5849

--- Comment #7 from Andreas Cord-Landwehr  ---
Git commit 2a57f9d1c6b2f8d9e2babcdaca66f1cf2a3c5849 by Andreas Cord-Landwehr.
Committed on 28/08/2021 at 13:57.
Pushed by cordlandwehr into branch 'master'.

Fix initialization of currency values

If there is already a recent currency.xml file provided then use this to
initialize the currency converter.

M  +8-0autotests/CMakeLists.txt
A  +33   -0autotests/currencytableinittest.cpp [License: LGPL(v2.0+)]
A  +26   -0autotests/currencytableinittest.h [License: LGPL(v2.0+)]
A  +43   -0autotests/currencytableinittest/currency.xml
A  +5-0autotests/currencytableinittest/data.qrc
M  +6-0autotests/valuetest.cpp
M  +7-3src/currency.cpp

https://invent.kde.org/frameworks/kunitconversion/commit/2a57f9d1c6b2f8d9e2babcdaca66f1cf2a3c5849

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

[frameworks-kunitconversion] [Bug 441337] Krunner currency conversion plugin cannot be triggered until a dotfile is removed

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/fram
   ||eworks/kunitconversion/comm
   ||it/6e41104426a3ae59bcb90be7
   ||08abcc3092155436
 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

--- Comment #6 from Andreas Cord-Landwehr  ---
Git commit 6e41104426a3ae59bcb90be708abcc3092155436 by Andreas Cord-Landwehr.
Committed on 24/08/2021 at 19:06.
Pushed by cordlandwehr into branch 'master'.

Fix automatic currency file sync after 24h

Conversion plugin in Krunner depends on automatic refresh of currency
table. std::call_once does not work there, because process is never
stopped.

M  +16   -0autotests/convertertest.cpp
M  +6-0autotests/convertertest.h
M  +6-3src/currency.cpp

https://invent.kde.org/frameworks/kunitconversion/commit/6e41104426a3ae59bcb90be708abcc3092155436

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

[frameworks-kunitconversion] [Bug 441337] Krunner currency conversion plugin cannot be triggered until a dotfile is removed

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

   Assignee|jl...@kde.org   |cordlandw...@kde.org

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

[parley] [Bug 441048] Parley Crashes when editing a newly created Collection

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 CC||cordlandw...@kde.org

--- Comment #1 from Andreas Cord-Landwehr  ---
Thank you for your report! Unfortunately I do not get the same backtrace as you
described, since I just fixed a wrong behavior at a very related location I
would like to figure out if this was the same problem.
What I understand:
1. you started Parley and you do not have any collections installed
2. you clicked on "Create a New Collection"
3. you fill in some data into this dialog and click "OK"
4. 
Thanks you for your help!

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

[frameworks-plasma] [Bug 438444] plasma-framework master fails to compile with cmake v3.20.2

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/fram
   ||eworks/plasma-framework/com
   ||mit/8953e77ec26b90da0e79e3c
   ||f3ecb727034768d58
 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

--- Comment #8 from Andreas Cord-Landwehr  ---
Git commit 8953e77ec26b90da0e79e3cf3ecb727034768d58 by Andreas Cord-Landwehr.
Committed on 24/06/2021 at 20:11.
Pushed by cordlandwehr into branch 'master'.

Add compatibility code when GLVND is not available

CMake's FindOpenGL internally handles EGL only correctly when GLVND is
available. This might not the case on embedded systems and actually it
is not necessary when EGL::EGL is found.

M  +14   -1CMakeLists.txt
M  +3-1src/declarativeimports/core/CMakeLists.txt

https://invent.kde.org/frameworks/plasma-framework/commit/8953e77ec26b90da0e79e3cf3ecb727034768d58

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

[frameworks-plasma] [Bug 438444] plasma-framework master fails to compile with cmake v3.20.2

[Andreas Cord-Landwehr]

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

--- Comment #5 from Andreas Cord-Landwehr  ---
While looking in pretty much the same problem in a Yocto setup, I discovered
some (at least in my impression) surprising condition checking in
FindOpenGL.cmake.
The logic is that the EGL target is only created, if the OpenGL target could be
created, which looks for the libOpenGL.so library.
Can you check that libglvnd-dev is installed on your system?

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

[frameworks-plasma] [Bug 438444] plasma-framework master fails to compile with cmake v3.20.2

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 CC||cordlandw...@kde.org

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

[Artikulate] [Bug 436510] Artikulate crashes while trying to download courses for first time

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 CC||ced...@nekoni.fr

--- Comment #2 from Andreas Cord-Landwehr  ---
*** Bug 420730 has been marked as a duplicate of this bug. ***

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

[Artikulate] [Bug 420730] Artikulate crash when download course

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #2 from Andreas Cord-Landwehr  ---
Thanks for the report, this is now fixed in the release/21.04 branch.

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

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

[Artikulate] [Bug 436510] Artikulate crashes while trying to download courses for first time

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
  Latest Commit||https://invent.kde.org/educ
   ||ation/artikulate/commit/d4a
   ||af42d02fab0aaf27ee7346f924d
   ||269eeac5c9

--- Comment #1 from Andreas Cord-Landwehr  ---
Git commit d4aaf42d02fab0aaf27ee7346f924d269eeac5c9 by Andreas Cord-Landwehr.
Committed on 15/05/2021 at 12:55.
Pushed by cordlandwehr into branch 'release/21.04'.

Fix invalid index on resource creation

On debug builds this can trigger a QAbstractItemModel assert because
a negative index is used.

M  +1-1src/core/iresourcerepository.h
M  +1-1src/core/resourcerepository.cpp

https://invent.kde.org/education/artikulate/commit/d4aaf42d02fab0aaf27ee7346f924d269eeac5c9

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

[frameworks-kio] [Bug 356506] Crash (assert) on changing file associations

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #4 from Andreas Cord-Landwehr  ---
Thanks for cleaning up the old reports. Checked with Dolphin 20.08.2 and cannot
reproduce anymore.

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

[Akonadi] [Bug 349696] Akonadi/KF5 hit assert while running in background

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #4 from Andreas Cord-Landwehr  ---
Thanks for cleaning up the old reports!
Since I did not see this assert over the last few years, let's close it.

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

[Artikulate] [Bug 427006] Artikulate not starting

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #1 from Andreas Cord-Landwehr  ---
Please install the missing QML packages from the terminal errors and try again.
Apparently, your package manager does not install the QML packages for QtQuick
controls and layouts. Any such missing package results in a fatal error.
This is a problem that needs to be solved by the respective packagers.

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

[Artikulate] [Bug 423899] Segmentation fault on fresh build of artikulate

[Andreas Cord-Landwehr]

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

--- Comment #4 from Andreas Cord-Landwehr  ---
You do not find anything in the CMake output, because your problem is not in
the build system: When starting Artikulate, it looks in your system at the Qt
default paths for plugins as well as the location that are defined with
QT_PLUGIN_PATH (see https://doc.qt.io/qt-5/deployment-plugins.html). Because
Artikulate does not find the (apparently correctly built plugins) it crashes on
startup.

Thus, all you have to do to set the path correctly in your environment.

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

[Artikulate] [Bug 423899] Segmentation fault on fresh build of artikulate

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|ASSIGNED

--- Comment #2 from Andreas Cord-Landwehr  ---
This crash comes from the problem that the respective OutputDevice plugin is
not found. Please set the QT_PLUGIN_PATH environment variable in cases when the
plugin is not installed into the Qt system location.
I will add a fatal error though that explains this problem.

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

[Artikulate] [Bug 418680] Artikulate does not start on my computer

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|REPORTED|RESOLVED

--- Comment #1 from Andreas Cord-Landwehr  ---
Thank you for your bug report!
Unfortunately, this is a packaging issue, where we cannot do much about. It
would be great if you could fill the same report at your distribution's bug
tracker with the hint that the package qml-module-qtquick-shapes is a runtime
dependency.
Installing that package should solve your problem.

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

[Rocs] [Bug 416710] some files not installed while installing kde rocs software

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 CC||cordlandw...@kde.org
 Resolution|--- |UPSTREAM
 Status|REPORTED|RESOLVED

--- Comment #1 from Andreas Cord-Landwehr  ---
The missing files are not a Rocs bug, because they are provided by by Qt
modules. Please contact your distribution and request to add the QtQuick
modules as dependency to the Rocs package. Specifically, you need to install
the Qt QtQuick Packages for QtQuick Layouts, Controls, Dialogs and
StateMachine.
Please note that these packages are runtime-only dependencies.

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

[Artikulate] [Bug 414985] Cannot install training materials

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/art
   ||ikulate/de8870b02888b4274c4
   ||04b74749553a303e6a66c

--- Comment #2 from Andreas Cord-Landwehr  ---
Git commit de8870b02888b4274c404b74749553a303e6a66c by Andreas Cord-Landwehr.
Committed on 19/12/2019 at 16:52.
Pushed by cordlandwehr into branch 'master'.

Adapt to KNewStuff API change in 5.63

Two changes are needed to be compatible with KNewStuff > 5.62:
- the installItem call now requires two arguments (previously this with
  only the first)
- binding the items model to the engine property does not work anymore
  but binding it directly to the engine object solves the issue

Note that this is a runtime only issue because QML methods are used.
However, this patch increases the minimal required version to 5.63 for
all frameworks, which shall help to ensure a functional KNewStuff
version being present.

M  +1-1CMakeLists.txt
M  +4-3src/qml/DownloadPage.qml

https://commits.kde.org/artikulate/de8870b02888b4274c404b74749553a303e6a66c

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

[Artikulate] [Bug 414985] Cannot install training materials

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Andreas Cord-Landwehr  ---
Thanks for reporting, after updating my KF5 packages I can reproduce the issue.

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

[Rocs] [Bug 415081] Increase minimum required Qt version to 5.11

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/kde/
   ||rocs/commit/765c85bac6abbf6
   ||59c2201f870f1ae5f6ac624d0
 Status|REPORTED|RESOLVED

--- Comment #1 from Andreas Cord-Landwehr  ---
Git commit 765c85bac6abbf659c2201f870f1ae5f6ac624d0 by Andreas Cord-Landwehr.
Committed on 13/12/2019 at 17:43.
Pushed by cordlandwehr into branch 'master'.

Set minimal Qt version according to used Qt API to 5.11

M  +1-1CMakeLists.txt

https://invent.kde.org/kde/rocs/commit/765c85bac6abbf659c2201f870f1ae5f6ac624d0

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

[parley] [Bug 393862] Cannot been installed on Lubuntu

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

 CC||cordlandw...@kde.org
 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Unfortunately, this issue is a packaging problem that comes from the way Parley
is packaged for Lubuntu. What this error message is about, is that the required
libqt5multimedia5 dependency is not installed on your system though it should
be automatically deployed by your package management system.

Please report this issue to the Lubuntu developers.

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

[kdevelop] [Bug 382626] New: Crash in KDevelop::FunctionDeclaration::additionalIdentity() [Git Master]

[Andreas Cord-Landwehr]

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

Bug ID: 382626
   Summary: Crash in
KDevelop::FunctionDeclaration::additionalIdentity()
[Git Master]
   Product: kdevelop
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: cordlandw...@kde.org
  Target Milestone: ---

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

Application: kdevelop (5.1.40)
 (Compiled from sources)
Qt Version: 5.8.0
Frameworks Version: 5.36.0
Operating System: Linux 4.9.0-2-amd64 x86_64
Distribution: Debian GNU/Linux testing (buster)

-- Information about the crash:
- What I was doing when the application crashed:
Directly after startup during initial re-parsing of my project, the appended
crash happened. (full report as attachment)

KDevelop & KDevPlatform and plugins were just cleanly rebuilt from sources.

Thread 12 (Thread 0x7fcd98daa700 (LWP 25828)):
[KCrash Handler]
#6  0x7fce04e05efb in KDevelop::FunctionDeclaration::additionalIdentity()
const (this=0x55dd56429a80) at
/opt/kde/src/extragear/kdevelop/kdevplatform/language/duchain/functiondeclaration.cpp:88
#7  0x7fce04dd111d in KDevelop::Declaration::id(bool) const
(this=0x55dd56429a80, forceDirect=false) at
/opt/kde/src/extragear/kdevelop/kdevplatform/language/duchain/declaration.cpp:542
#8  0x7fce04db1c4a in
KDevelop::TopDUContext::indexForUsedDeclaration(KDevelop::Declaration*, bool)
(this=0x55dd5636f450, declaration=0x55dd56429a80, create=true) at
/opt/kde/src/extragear/kdevelop/kdevplatform/language/duchain/topducontext.cpp:1109
#9  0x7fcdbd6ac267 in (anonymous
namespace)::Visitor::Visitor(CXTranslationUnit, CXFile, IncludeFileContexts
const&, bool) (this=0x7fcd98da9200, tu=0x7fcd6a36d8a0, file=0x7fcd5846d1a0,
includes=..., update=true) at
/opt/kde/src/extragear/kdevelop/kdevelop/languages/clang/duchain/builder.cpp:1425
#10 0x7fcdbd6accfa in Builder::visit(CXTranslationUnitImpl*, void*,
QHash const&, bool)
(tu=0x7fcd6a36d8a0, file=0x7fcd5846d1a0, includes=..., update=true) at
/opt/kde/src/extragear/kdevelop/kdevelop/languages/clang/duchain/builder.cpp:1515
#11 0x7fcdbd705933 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features,
QHash&, ClangIndex*,
std::function const&) (file=0x7fcd5846d1a0, imports=..., session=...,
features=KDevelop::TopDUContext::AllDeclarationsContextsAndUses,
includedFiles=..., index=0x55dd52313b60, abortFunction=...) at
/opt/kde/src/extragear/kdevelop/kdevelop/languages/clang/duchain/clanghelpers.cpp:189
#12 0x7fcdbd70516a in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features,
QHash&, ClangIndex*,
std::function const&) (file=0x7fcd688cd7e0, imports=..., session=...,
features=KDevelop::TopDUContext::AllDeclarationsContextsAndUses,
includedFiles=..., index=0x55dd52313b60, abortFunction=...) at
/opt/kde/src/extragear/kdevelop/kdevelop/languages/clang/duchain/clanghelpers.cpp:121
#13 0x7fcdbd99c418 in
ClangParseJob::run(QSharedPointer,
ThreadWeaver::Thread*) (this=0x55dd560bd410) at
/opt/kde/src/extragear/kdevelop/kdevelop/languages/clang/clangparsejob.cpp:322
#14 0x7fce03e01e60 in
ThreadWeaver::IdDecorator::run(QSharedPointer,
ThreadWeaver::Thread*) (this=0x55dd560bce80, self=..., thread=0x7fcd940013e0)
at /opt/kde/src/frameworks/threadweaver/src/iddecorator.cpp:69
#15 0x7fce03e02b46 in
ThreadWeaver::Executor::run(QSharedPointer const&,
ThreadWeaver::Thread*) (this=0x7fce0401e6b0
, job=..., thread=0x7fcd940013e0) at
/opt/kde/src/frameworks/threadweaver/src/executor.cpp:52
#16 0x7fce03e01a55 in
ThreadWeaver::Private::DefaultExecutor::execute(QSharedPointer
const&, ThreadWeaver::Thread*) (this=0x7fce0401e6b0
, job=..., thread=0x7fcd940013e0) at
/opt/kde/src/frameworks/threadweaver/src/job_p.cpp:70
#17 0x7fce03e02d8e in
ThreadWeaver::ExecuteWrapper::executeWrapped(QSharedPointer
const&, ThreadWeaver::Thread*) (this=0x55dd560bcac8, job=...,
thread=0x7fcd940013e0) at
/opt/kde/src/frameworks/threadweaver/src/executewrapper.cpp:64
#18 0x7fce03e019c1 in
ThreadWeaver::Private::DebugExecuteWrapper::execute(QSharedPointer
const&, ThreadWeaver::Thread*) (this=0x55dd560bcac8, job=...,
th=0x7fcd940013e0) at /opt/kde/src/frameworks/threadweaver/src/job_p.cpp:58
#19 0x7fce03e02d8e in
ThreadWeaver::ExecuteWrapper::executeWrapped(QSharedPointer
const&, ThreadWeaver::Thread*) (this=0x55dd560bcaf0, job=...,
thread=0x7fcd940013e0) at
/opt/kde/src/frameworks/threadweaver/src/executewrapper.cpp:64
#20 0x7fce03e02d19 

[Rocs] [Bug 378095] rocs-16.12.3 cannot export any graph on kde 5

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/roc
   ||s/b8cc5ef420474cadf3a506527
   ||bebde09ac36e3f9
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Git commit b8cc5ef420474cadf3a506527bebde09ac36e3f9 by Andreas Cord-Landwehr.
Committed on 26/05/2017 at 15:29.
Pushed by cordlandwehr into branch 'master'.

Fix graph export filter

Includes:
- add message boxes if anything goes fatally wrong (i.e. no data is written)
- fix generation of export filters
- deduce export plugin from selected filter and not from file suffix, since
  that is not relyable

M  +21   -15   src/ui/fileformatdialog.cpp

https://commits.kde.org/rocs/b8cc5ef420474cadf3a506527bebde09ac36e3f9

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

[parley] [Bug 368490] Get New Themes shows collections instead of themes

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

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

--- Comment #1 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Was an import error in the KDE store, fixed now.

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

[parley] [Bug 368489] Download new vocabularies not working

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

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

--- Comment #1 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Please test again, should work now. However, for now you have to select
"Parley" specifically as category. (at the right).
There is a pending review for GHNS that will also fix this.

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

[parley] [Bug 368148] Cannot upload vocabulary collection

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

   Assignee|parley-bugs-n...@kde.org|cordlandw...@kde.org
 CC||cordlandw...@kde.org

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

[parley] [Bug 368490] Get New Themes shows collections instead of themes

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

 CC||cordlandw...@kde.org
   Assignee|parley-bugs-n...@kde.org|cordlandw...@kde.org

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

[parley] [Bug 368489] Download new vocabularies not working

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

   Assignee|parley-bugs-n...@kde.org|cordlandw...@kde.org
 CC||cordlandw...@kde.org

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

[kdesrc-build] [Bug 362687] Enable kdesrc-build to handle Git Submodules

[Andreas Cord-Landwehr]

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

--- Comment #2 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Sorry for the late answer, completely forgot about this :/
Qt5 would be an example where I could imagine to use it. With Qt's own
configuration system however, I am not sure how easy it will be to build it
with kdesrc-build. My specific use case is that I would like to add QtCreator
to kdesrc-build, which uses submodules. Within KDE I cannot recall any use of
submodules except the kf5-books project (which is a very special corner-case
that we do not have to add to kdesrc-build :)
Deactivating it by default seems completely fine for me.

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

[kalzium] [Bug 371963] Menu File > Quit does not work

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kalz
   ||ium/7c9e0221cd4a6d9d58c7ee0
   ||c9bac32f4e06b40da
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Git commit 7c9e0221cd4a6d9d58c7ee0c9bac32f4e06b40da by Andreas Cord-Landwehr.
Committed on 12/11/2016 at 15:43.
Pushed by cordlandwehr into branch 'master'.

Connect to correct application quit slot

M  +1-1src/kalzium.cpp

http://commits.kde.org/kalzium/7c9e0221cd4a6d9d58c7ee0c9bac32f4e06b40da

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

[kalzium] [Bug 317375] Molecular editor total black

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
 CC||cordlandw...@kde.org

--- Comment #5 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
The molecule editor was ported to Avogadro 2 for the upcoming Kalzium release
in December (KDE Applications 16.12). With that version I cannot reproduce the
bug.

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

[kalzium] [Bug 346563] The molecular editor does not display any molecule

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

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

--- Comment #4 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
The molecule editor was ported to Avogadro 2 for the upcoming Kalzium release
in December (KDE Applications 16.12). With that version I cannot reproduce the
bug.

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

[kalzium] [Bug 313720] Molecular editor

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

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

--- Comment #3 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
The molecule editor was ported to Avogadro 2 for the upcoming Kalzium release
in December (KDE Applications 16.12). With that version I cannot reproduce the
bug.

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

[kalzium] [Bug 326837] kalzium crashes when selecting clicking on button "molecular editor"

[Andreas Cord-Landwehr]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

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

--- Comment #3 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
This should be fixed in the upcoming Kalzium release with the KDE Applications
16/12 release (December 2016), in which Kalzium switches to Avogadro 2.

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

[KScreen] [Bug 364044] Second screen in docking station keeps black after suspend

[Andreas Cord-Landwehr]

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

--- Comment #14 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
... and here the output after resumed from suspend-to-ram:

kscreen-console bug
kscreen-console(11252)/(default) main: START: Requesting Config
kscreen-console(11252)/(default) KScreen::BackendManager::startBackend: DBUS
signal sent
kscreen-console(11252)/(default) KScreen::BackendManager::requestBackend: SEND
startBackend for  ""
kscreen-console(11252)/(default) KScreen::BackendManager::onBackendRequestDone:
DBUS DONE
kscreen-console(11252)/(default) configReceived: Received config. Took 68
milliseconds

xrandr --verbose==
Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 8192 x 8192
eDP-1 connected primary 1920x1080+0+0 (0x4b) normal (normal left inverted right
x axis y axis) 309mm x 173mm
Identifier: 0x42
Timestamp:  103923196
Subpixel:   unknown
Gamma:  1.0:1.0:1.0
Brightness: 1.0
Clones:
CRTC:   0
CRTCs:  0 1 2
Transform:  1.00 0.00 0.00
0.00 1.00 0.00
0.00 0.00 1.00
   filter: 
EDID: 
000006af3d12
00160104951f11780287e5a456509e26
0d50540001010101010101010101
010101010101143780b8703824401010
3e0035ad1018000f
002000fe0041
554f0a20202020202020202000fe
004231343048414e30312e32200a00a3
scaling mode: Full aspect 
supported: None, Full, Center, Full aspect
Broadcast RGB: Automatic 
supported: Automatic, Full, Limited 16:235
audio: auto 
supported: force-dvi, off, auto, on
  1920x1080 (0x4b) 141.000MHz -HSync -VSync *current +preferred
h: width  1920 start 1936 end 1952 total 2104 skew0 clock  67.02KHz
v: height 1080 start 1083 end 1097 total 1116   clock  60.05Hz
  1920x1080 (0x4c) 138.500MHz +HSync -VSync 
h: width  1920 start 1968 end 2000 total 2080 skew0 clock  66.59KHz 
v: height 1080 start 1083 end 1088 total    clock  59.93Hz  
  1680x1050 (0x4d) 146.250MHz -HSync +VSync 
h: width  1680 start 1784 end 1960 total 2240 skew0 clock  65.29KHz 
v: height 1050 start 1053 end 1059 total 1089   clock  59.95Hz  
  1680x1050 (0x4e) 119.000MHz +HSync -VSync 
h: width  1680 start 1728 end 1760 total 1840 skew0 clock  64.67KHz 
v: height 1050 start 1053 end 1059 total 1080   clock  59.88Hz  
  1600x1024 (0x4f) 103.125MHz +HSync +VSync 
h: width  1600 start 1600 end 1656 total 1664 skew0 clock  61.97KHz 
v: height 1024 start 1024 end 1029 total 1030   clock  60.17Hz  
  1400x1050 (0x50) 122.000MHz +HSync +VSync 
h: width  1400 start 1488 end 1640 total 1880 skew0 clock  64.89KHz 
v: height 1050 start 1052 end 1064 total 1082   clock  59.98Hz  
  1280x1024 (0x51) 108.000MHz +HSync +VSync 
h: width  1280 start 1328 end 1440 total 1688 skew0 clock  63.98KHz 
v: height 1024 start 1025 end 1028 total 1066   clock  60.02Hz  
  1440x900 (0x52) 106.500MHz -HSync +VSync  
h: width  1440 start 1520 end 1672 total 1904 skew0 clock  55.93KHz 
v: height  900 start  903 end  909 total  934   clock  59.89Hz  
  1280x960 (0x53) 108.000MHz +HSync +VSync  
h: width  1280 start 1376 end 1488 total 1800 skew0 clock  60.00KHz 
v: height  960 start  961 end  964 total 1000   clock  60.00Hz  
  1360x768 (0x54) 84.750MHz -HSync +VSync   
h: width  1360 start 1432 end 1568 total 1776 skew0 clock  47.72KHz 
v: height  768 start  771 end  781 total  798   clock  59.80Hz  
  1360x768 (0x55) 72.000MHz +HSync -VSync   
h: width  1360 start 1408 end 1440 total 1520 skew0 clock  47.37KHz
v: height  768 start  771 end  781 total  790   clock  59.96Hz
  1152x864 (0x56) 81.620MHz -HSync +VSync
h: width  1152 start 1216 end 1336 total 1520 skew0 clock  53.70KHz
v: height  864 start  865 end  868 total  895   clock  60.00Hz
  1024x768 (0x57) 133.475MHz -HSync +VSync DoubleScan
h: width  1024 start 1100 end 1212 total 1400 skew0 clock  95.34KHz
v: height  768 start  768 end  770 total  794   clock  60.04Hz

[KScreen] [Bug 364044] Second screen in docking station keeps black after suspend

[Andreas Cord-Landwehr]

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

--- Comment #13 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Hi, the problem is still present with Plasma 5.8. Here the output with both
screens working:

$ kscreen-console bug
kscreen-console(10856)/(default) main: START: Requesting Config
kscreen-console(10856)/(default) KScreen::BackendManager::startBackend: DBUS
signal sent
kscreen-console(10856)/(default) KScreen::BackendManager::requestBackend: SEND
startBackend for  ""
kscreen-console(10856)/(default) KScreen::BackendManager::onBackendRequestDone:
DBUS DONE
kscreen-console(10856)/(default) configReceived: Received config. Took 66
milliseconds

xrandr --verbose==
Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 8192 x 8192
eDP-1 connected primary 1920x1080+0+0 (0x4b) normal (normal left inverted right
x axis y axis) 309mm x 173mm
Identifier: 0x42
Timestamp:  103923196
Subpixel:   unknown
Gamma:  1.0:1.0:1.0
Brightness: 1.0
Clones:
CRTC:   0
CRTCs:  0 1 2
Transform:  1.00 0.00 0.00
0.00 1.00 0.00
0.00 0.00 1.00
   filter: 
EDID: 
000006af3d12
00160104951f11780287e5a456509e26
0d50540001010101010101010101
010101010101143780b8703824401010
3e0035ad1018000f
002000fe0041
554f0a20202020202020202000fe
004231343048414e30312e32200a00a3
scaling mode: Full aspect 
supported: None, Full, Center, Full aspect
Broadcast RGB: Automatic 
supported: Automatic, Full, Limited 16:235
audio: auto 
supported: force-dvi, off, auto, on
  1920x1080 (0x4b) 141.000MHz -HSync -VSync *current +preferred
h: width  1920 start 1936 end 1952 total 2104 skew0 clock  67.02KHz
v: height 1080 start 1083 end 1097 total 1116   clock  60.05Hz  
  1920x1080 (0x4c) 138.500MHz +HSync -VSync 
h: width  1920 start 1968 end 2000 total 2080 skew0 clock  66.59KHz 
v: height 1080 start 1083 end 1088 total    clock  59.93Hz  
  1680x1050 (0x4d) 146.250MHz -HSync +VSync 
h: width  1680 start 1784 end 1960 total 2240 skew0 clock  65.29KHz 
v: height 1050 start 1053 end 1059 total 1089   clock  59.95Hz  
  1680x1050 (0x4e) 119.000MHz +HSync -VSync 
h: width  1680 start 1728 end 1760 total 1840 skew0 clock  64.67KHz 
v: height 1050 start 1053 end 1059 total 1080   clock  59.88Hz  
  1600x1024 (0x4f) 103.125MHz +HSync +VSync 
h: width  1600 start 1600 end 1656 total 1664 skew0 clock  61.97KHz 
v: height 1024 start 1024 end 1029 total 1030   clock  60.17Hz  
  1400x1050 (0x50) 122.000MHz +HSync +VSync 
h: width  1400 start 1488 end 1640 total 1880 skew0 clock  64.89KHz 
v: height 1050 start 1052 end 1064 total 1082   clock  59.98Hz  
  1280x1024 (0x51) 108.000MHz +HSync +VSync 
h: width  1280 start 1328 end 1440 total 1688 skew0 clock  63.98KHz 
v: height 1024 start 1025 end 1028 total 1066   clock  60.02Hz  
  1440x900 (0x52) 106.500MHz -HSync +VSync  
h: width  1440 start 1520 end 1672 total 1904 skew0 clock  55.93KHz 
v: height  900 start  903 end  909 total  934   clock  59.89Hz  
  1280x960 (0x53) 108.000MHz +HSync +VSync  
h: width  1280 start 1376 end 1488 total 1800 skew0 clock  60.00KHz 
v: height  960 start  961 end  964 total 1000   clock  60.00Hz  
  1360x768 (0x54) 84.750MHz -HSync +VSync   
h: width  1360 start 1432 end 1568 total 1776 skew0 clock  47.72KHz 
v: height  768 start  771 end  781 total  798   clock  59.80Hz  
  1360x768 (0x55) 72.000MHz +HSync -VSync   
h: width  1360 start 1408 end 1440 total 1520 skew0 clock  47.37KHz 
v: height  768 start  771 end  781 total  790   clock  59.96Hz
  1152x864 (0x56) 81.620MHz -HSync +VSync
h: width  1152 start 1216 end 1336 total 1520 skew0 clock  53.70KHz
v: height  864 start  865 end  868 total  895   clock  60.00Hz
  1024x768 (0x57) 133.475MHz -HSync +VSync DoubleScan
h: width  1024 start 1100 end 1212 total 1400 skew0 clock  95.34KHz
v: height  768 start  768 end

[Rocs] [Bug 367647] Unsupported compiler flags passed to Clang

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/rocs
   ||/624a6bc2118a9224089f3a7ee6
   ||5e2993efc1dc1c
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Git commit 624a6bc2118a9224089f3a7ee65e2993efc1dc1c by Andreas Cord-Landwehr.
Committed on 05/09/2016 at 13:41.
Pushed by cordlandwehr into branch 'Applications/16.08'.

Use BOOST_MATH_DISABLE_FLOAT128 to avoid operator problem.

The use of -fext-numeric-literals apparently is not supported
by Clang. Use correct Boost define to avoid use of custom
literals.

M  +0-1CMakeLists.txt
M  +2-0libgraphtheory/modifiers/topology.h

http://commits.kde.org/rocs/624a6bc2118a9224089f3a7ee65e2993efc1dc1c

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

[kdevelop] [Bug 368270] New: Crash when pressing ALT + ENTER in assistant dialog

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Bug ID: 368270
   Summary: Crash when pressing ALT + ENTER in assistant dialog
   Product: kdevelop
   Version: 5.0.0
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: cordlandw...@kde.org

Application: kdevelop (5.0.0)
 (Compiled from sources)
Qt Version: 5.7.0
Frameworks Version: 5.25.0
Operating System: Linux 4.6.0-1-amd64 x86_64
Distribution: Debian GNU/Linux testing (stretch)

-- Information about the crash:
- What I was doing when the application crashed:
When the crash happend, I was pressing ALT + ENTER in the assistant dialog.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff683638940 (LWP 807))]

Thread 21 (Thread 0x7ff608a4b700 (LWP 1954)):
#0  0x7ff69767509f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7ff697356ee4 in QTWTF::TCMalloc_PageHeap::scavengerThread()
(this=0x7ff69743d1a0 ) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x7ff697356f29 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*)
(context=) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x7ff69766f464 in start_thread (arg=0x7ff608a4b700) at
pthread_create.c:333
#4  0x7ff69ea7130d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 20 (Thread 0x7ff609a4d700 (LWP 859)):
#0  0x7ff69ea6819d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7ff69288439c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7ff604002e40, timeout=, context=0x7ff604000990) at
/build/glib2.0-vjfO_h/glib2.0-2.48.1/./glib/gmain.c:4135
#2  0x7ff69288439c in g_main_context_iterate
(context=context@entry=0x7ff604000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-vjfO_h/glib2.0-2.48.1/./glib/gmain.c:3835
#3  0x7ff6928844ac in g_main_context_iteration (context=0x7ff604000990,
may_block=may_block@entry=1) at
/build/glib2.0-vjfO_h/glib2.0-2.48.1/./glib/gmain.c:3901
#4  0x7ff69f88b29b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7ff6040008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7ff69f8391ca in
QEventLoop::exec(QFlags)
(this=this@entry=0x7ff609a4cbf0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#6  0x7ff69f66f2ac in QThread::exec() (this=) at
thread/qthread.cpp:511
#7  0x7ff69cb19b9f in KDevelop::CompletionWorkerThread::run()
(this=0x43a1780) at
/opt/kde/src/extragear/kdevelop/kdevplatform/language/codecompletion/codecompletionmodel.cpp:89
#8  0x7ff69f673bd9 in QThreadPrivate::start(void*) (arg=0x43a1780) at
thread/qthread_unix.cpp:343
#9  0x7ff69766f464 in start_thread (arg=0x7ff609a4d700) at
pthread_create.c:333
#10 0x7ff69ea7130d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 19 (Thread 0x7ff621ffb700 (LWP 853)):
#0  0x7ff69767509f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7ff69f67497b in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x27deb30) at
thread/qwaitcondition_unix.cpp:143
#2  0x7ff69f67497b in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0x25a3560, time=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7ff69b9364e6 in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked(ThreadWeaver::Thread*)
(this=0x27dea40, th=0x7ff60c003020) at
/opt/kde/src/frameworks/threadweaver/src/weaver.cpp:594
#4  0x7ff69b9361bf in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) (this=0x27dea40, th=0x7ff60c003020, threadWasBusy=false,
suspendIfInactive=false, justReturning=false) at
/opt/kde/src/frameworks/threadweaver/src/weaver.cpp:554
#5  0x7ff69b93ebe7 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool)
(this=0x25d2d60, th=0x7ff60c003020, wasBusy=false) at
/opt/kde/src/frameworks/threadweaver/src/workinghardstate.cpp:66
#6  0x7ff69b936300 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool)
(this=0x27dea40, th=0x7ff60c003020, wasBusy=false) at
/opt/kde/src/frameworks/threadweaver/src/weaver.cpp:568
#7  0x7ff69b93ecea in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool)
(this=0x25d2d60, th=0x7ff60c003020, wasBusy=false) at
/opt/kde/src/frameworks/threadweaver/src/workinghardstate.cpp:73
#8  0x7ff69b936300 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool)
(this=0x27dea40, th=0x7ff60c003020, wasBusy=false) at

[KScreen] [Bug 364044] Second screen in docking station keeps black after suspend

[Andreas Cord-Landwehr via KDE Bugzilla]

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

--- Comment #11 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Sorry for the late reply, had a long struggle with the kscreen kcm not starting
up correctly (finally turned out to be caused by a mix of loaded Qt libs with
different SO versions...).
Back to topic: I can still reproduce the issue with Plasma/5.7 branch. Will
next update to Plasma/5.8 and test again.

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

[kdevelop] [Bug 365773] New: Crash when clicking at context dialog on container

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Bug ID: 365773
   Summary: Crash when clicking at context dialog on container
   Product: kdevelop
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: cordlandw...@kde.org

Application: kdevelop (4.90.92)
 (Compiled from sources)
Qt Version: 5.7.0
Frameworks Version: 5.25.0
Operating System: Linux 4.6.0-1-amd64 x86_64
Distribution: Debian GNU/Linux testing (stretch)

-- Information about the crash:
What I was doing when the application crashed:
- hover mouse over any type/variable/function declaration
- in the context dialog click at the containing type
-> Crash

-- Backtrace:
Application: KDevelop (kdevelop), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3f32867940 (LWP 27599))]

Thread 13 (Thread 0x7f3ecbe74700 (LWP 27672)):
#0  0x7f3f3f7e3c22 in g_main_context_check
(context=context@entry=0x7f3ebb80b3e0, max_priority=2147483647,
fds=fds@entry=0x7f3ebb372cb0, n_fds=n_fds@entry=1) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3614
#1  0x7f3f3f7e4340 in g_main_context_iterate
(context=context@entry=0x7f3ebb80b3e0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3837
#2  0x7f3f3f7e44ac in g_main_context_iteration (context=0x7f3ebb80b3e0,
may_block=may_block@entry=1) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3901
#3  0x7f3f4c7e129b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f3eb9696540, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f3f4c78f1ca in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f3ecbe73bf0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#5  0x7f3f4c5c52ac in QThread::exec() (this=) at
thread/qthread.cpp:511
#6  0x7f3f49a711b5 in KDevelop::CompletionWorkerThread::run()
(this=0x5926bd0) at
/opt/kde/src/extragear/kdevelop/kdevplatform/language/codecompletion/codecompletionmodel.cpp:89
#7  0x7f3f4c5c9bd9 in QThreadPrivate::start(void*) (arg=0x5926bd0) at
thread/qthread_unix.cpp:343
#8  0x7f3f445cd464 in start_thread (arg=0x7f3ecbe74700) at
pthread_create.c:333
#9  0x7f3f4b9c830d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7f3ed97b2700 (LWP 27644)):
#0  0x7f3f4b9bf19d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f3f3f7e439c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7f3ec41b7dc0, timeout=, context=0x7f3ec40008c0) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:4135
#2  0x7f3f3f7e439c in g_main_context_iterate
(context=context@entry=0x7f3ec40008c0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3835
#3  0x7f3f3f7e44ac in g_main_context_iteration (context=0x7f3ec40008c0,
may_block=may_block@entry=1) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3901
#4  0x7f3f4c7e129b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f3ec4003ce0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f3f4c78f1ca in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f3ed97b1c90, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#6  0x7f3f4c5c52ac in QThread::exec() (this=) at
thread/qthread.cpp:511
#7  0x7f3f4c5c9bd9 in QThreadPrivate::start(void*) (arg=0x7f3f5170d718
) at
thread/qthread_unix.cpp:343
#8  0x7f3f445cd464 in start_thread (arg=0x7f3ed97b2700) at
pthread_create.c:333
#9  0x7f3f4b9c830d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7f3eda925700 (LWP 27639)):
#0  0x7f3f445d309f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f3f4c5ca97b in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x24871a0) at
thread/qwaitcondition_unix.cpp:143
#2  0x7f3f4c5ca97b in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0x230d270, time=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7f3f4888b546 in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked(ThreadWeaver::Thread*)
(this=0x24870b0, th=0x7f3ed4001e20) at
/opt/kde/src/frameworks/threadweaver/src/weaver.cpp:594
#4  0x7f3f4888b21f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) (this=0x24870b0, th=0x7f3ed4001e20, threadWasBusy=true,
suspendIfInactive=false, justReturning=false) at
/opt/kde/src/frameworks/threadweaver/src/weaver.cpp:554
#5  0x7f3f48893c47 in

[kdevelop] [Bug 365766] Crash when stopping unit test that segfaulted [KDevelop::OutputExecuteJob]

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/kdev
   ||platform/1d87fc630265792235
   ||4a6fc49e2ce0b1d0d1f918

--- Comment #1 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Git commit 1d87fc6302657922354a6fc49e2ce0b1d0d1f918 by Andreas Cord-Landwehr.
Committed on 17/07/2016 at 12:27.
Pushed by cordlandwehr into branch '5.0'.

Do not assert if process survives kill.

Summary:
If process survives kill, an error message is already printed to
indicate the problem. Since we cannot hope to kill the process,
gracefully handle this case.

Test Plan: Manual testing.

Reviewers: #kdevelop, brauch

Reviewed By: #kdevelop, brauch

Subscribers: brauch, kdevelop-devel

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

M  +10   -4outputview/outputexecutejob.cpp

http://commits.kde.org/kdevplatform/1d87fc6302657922354a6fc49e2ce0b1d0d1f918

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

[kdevelop] [Bug 365766] New: Crash when stopping unit test that segfaulted [KDevelop::OutputExecuteJob]

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Bug ID: 365766
   Summary: Crash when stopping unit test that segfaulted
[KDevelop::OutputExecuteJob]
   Product: kdevelop
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: cordlandw...@kde.org

Application: kdevelop (4.90.92)
 (Compiled from sources)
Qt Version: 5.7.0
Frameworks Version: 5.25.0
Operating System: Linux 4.6.0-1-amd64 x86_64
Distribution: Debian GNU/Linux testing (stretch)

-- Information about the crash:
Steps to reproduce:
- start a unit unit that enters a gdb session due to eg. a segfault
- whilte gdb is still starting, stop that unit test
- the appended crash occurs

The crash can be reproduced every time.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6695d09940 (LWP 23883))]

Thread 14 (Thread 0x7f6646ee9700 (LWP 23965)):
#0  0x7f66a7a7509f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f66a7756ee4 in QTWTF::TCMalloc_PageHeap::scavengerThread()
(this=0x7f66a783d1a0 ) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x7f66a7756f29 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*)
(context=) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x7f66a7a6f464 in start_thread (arg=0x7f6646ee9700) at
pthread_create.c:333
#4  0x7f66aee6930d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7f664549a700 (LWP 23942)):
#0  0x7f66afa62a28 in QMutex::unlock() (__m2=,
__m1=std::memory_order_release, __p2=0x0, __p1=@0x7f66454999b0: 0x1,
this=0x455a5d0) at /usr/include/c++/5/bits/atomic_base.h:752
#1  0x7f66afa62a28 in QMutex::unlock() (__m=std::memory_order_release,
__p2=0x0, __p1=@0x7f66454999b0: 0x1, this=0x455a5d0) at
/usr/include/c++/5/atomic:475
#2  0x7f66afa62a28 in QMutex::unlock() (currentValue=,
newValue=0x0, expectedValue=0x1, _q_value=...) at
../../include/QtCore/../../src/corelib/arch/qatomic_cxx11.h:174
#3  0x7f66afa62a28 in QMutex::unlock() (currentValue=,
newValue=0x0, expectedValue=, this=this@entry=0x455a5d0) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:261
#4  0x7f66afa62a28 in QMutex::unlock() (current=,
this=this@entry=0x455a5d0) at thread/qmutex.h:91
#5  0x7f66afa62a28 in QMutex::unlock() (this=this@entry=0x455a5d0) at
thread/qmutex.cpp:277
#6  0x7f66afc81a3d in postEventSourcePrepare(GSource*, gint*)
(this=) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:144
#7  0x7f66afc81a3d in postEventSourcePrepare(GSource*, gint*)
(this=, __in_chrg=) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:138
#8  0x7f66afc81a3d in postEventSourcePrepare(GSource*, gint*)
(this=0x455a5a0) at
../../include/QtCore/5.7.0/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:254
#9  0x7f66afc81a3d in postEventSourcePrepare(GSource*, gint*)
(s=0x7f66303c5e00, timeout=timeout@entry=0x7f6645499a34) at
kernel/qeventdispatcher_glib.cpp:259
#10 0x7f66a2c8592d in g_main_context_prepare
(context=context@entry=0x7f6630086a60, priority=priority@entry=0x7f6645499ac0)
at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3442
#11 0x7f66a2c862cb in g_main_context_iterate
(context=context@entry=0x7f6630086a60, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3820
#12 0x7f66a2c864ac in g_main_context_iteration (context=0x7f6630086a60,
may_block=may_block@entry=1) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3901
#13 0x7f66afc8229b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f6630a21220, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#14 0x7f66afc301ca in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f6645499bf0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#15 0x7f66afa662ac in QThread::exec() (this=) at
thread/qthread.cpp:511
#16 0x7f66acf121ef in KDevelop::CompletionWorkerThread::run()
(this=0x455c8a0) at
/opt/kde/src/extragear/kdevelop/kdevplatform/language/codecompletion/codecompletionmodel.cpp:89
#17 0x7f66afa6abd9 in QThreadPrivate::start(void*) (arg=0x455c8a0) at
thread/qthread_unix.cpp:343
#18 0x7f66a7a6f464 in start_thread (arg=0x7f664549a700) at
pthread_create.c:333
#19 0x7f66aee6930d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7f66466e8700 (LWP 23914)):
#0  0x7f66aee5c17d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f66a2cc9740 in g_wakeup_acknowledge (__nbytes=16,
__buf=0x7f66466e7a90, __fd=) at

[KScreen] [Bug 365040] kscreen KCM cannot be used if KSCREEN_BACKEND is not set

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #3 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
After some major cleanup of my .config and .local directories (grown since the
first Qt5 based pre-alpha versions), I cannot reproduce this issue anymore. So,
I will close it.

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

[kdevelop] [Bug 235283] Crash on deleting folder

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #7 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Did not see this problem during the last couple of years.
Let's close it :)

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

[KScreen] [Bug 364044] Second screen in docking station keeps black after suspend

[Andreas Cord-Landwehr via KDE Bugzilla]

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

--- Comment #7 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
I can still reproduce this issue with this patch. Do you need updated
information?
My Qt now is 5.7.

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

[frameworks-baloo] [Bug 361903] Assert "DocumentUrlDB::del"

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

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

--- Comment #1 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Fixed by Pinak during the last Randa sprint.

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

[KScreen] [Bug 365040] kscreen KCM cannot be used if KSCREEN_BACKEND is not set

[Andreas Cord-Landwehr via KDE Bugzilla]

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

--- Comment #2 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
You are right; I looked at the wrong code location. Here is a probably more
verbose output. I now generated a backtrace for getting the debug message:

kcmshell5(30793)/(kscreen) KScreen::BackendManager::startBackend: starting
external backend launcher for ""

At this point, I have (added an assert in
"/opt/kde/src/kde/workspace/libkscreen/src/backendmanager.cpp", line=291):
#5  0x7fffda2f3bc6 in KScreen::BackendManager::startBackend(QString const&,
QMap<QString, QVariant> const&) (this=0x6af270, backend=..., arguments=...)
at /opt/kde/src/kde/workspace/libkscreen/src/backendmanager.cpp:291
#6  0x7fffda2f3aca in KScreen::BackendManager::requestBackend()
(this=0x6af270) at
/opt/kde/src/kde/workspace/libkscreen/src/backendmanager.cpp:276
#7  0x7fffda2fe5cb in KScreen::ConfigOperationPrivate::requestBackend()
(this=0x9265f0) at
/opt/kde/src/kde/workspace/libkscreen/src/configoperation.cpp:45
#8  0x7fffda30019e in KScreen::GetConfigOperation::start() (this=0x92bfd0)
at /opt/kde/src/kde/workspace/libkscreen/src/getconfigoperation.cpp:178
#9  0x7fffda315dcd in
KScreen::ConfigOperation::qt_static_metacall(QObject*, QMetaObject::Call, int,
void**) (_o=0x92bfd0, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x92bd10)
at /opt/kde/build/kde/workspace/libkscreen/src/moc_configoperation.cpp:81
#10 0x74d8ad07 in QMetaCallEvent::placeMetaCall(QObject*)
(this=0x93afb0, object=0x92bfd0) at kernel/qobject.cpp:495
#11 0x74d8bda0 in QObject::event(QEvent*) (this=0x92bfd0, e=0x93afb0)
at kernel/qobject.cpp:1256
#12 0x7594a4f2 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=0x61a250, receiver=0x92bfd0, e=0x93afb0) at kernel/qapplication.cpp:3804
#13 0x759478bd in QApplication::notify(QObject*, QEvent*)
(this=0x7fffd1f0, receiver=0x92bfd0, e=0x93afb0) at
kernel/qapplication.cpp:3163
#14 0x74d51bfa in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x92bfd0, event=0x93afb0) at kernel/qcoreapplication.cpp:1015
#15 0x74d55c30 in QCoreApplication::sendEvent(QObject*, QEvent*)
(receiver=0x92bfd0, event=0x93afb0) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:225
#16 0x74d52fe2 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x6190d0) at
kernel/qcoreapplication.cpp:1650
#17 0x74d52962 in QCoreApplication::sendPostedEvents(QObject*, int)
(receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1508
#18 0x74dcbb2c in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x672fb0) at kernel/qeventdispatcher_glib.cpp:270
#19 0x7fffed56a1a7 in g_main_context_dispatch (context=0x7fffdc0016f0) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3154
#20 0x7fffed56a1a7 in g_main_context_dispatch
(context=context@entry=0x7fffdc0016f0) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3769
#21 0x7fffed56a400 in g_main_context_iterate
(context=context@entry=0x7fffdc0016f0, block=block@entry=1,
dispatch=dispatch@entry=1, self=)
at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3840
---Type  to continue, or q  to quit---
#22 0x7fffed56a4ac in g_main_context_iteration (context=0x7fffdc0016f0,
may_block=1) at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3901
#23 0x74dcc305 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x67ceb0, flags=...) at kernel/qeventdispatcher_glib.cpp:417
#24 0x7fffe78cce86 in
QPAEventDispatcherGlib::processEvents(QFlags)
(this=0x67ceb0, flags=...) at eventdispatchers/qeventdispatcher_glib.cpp:115
#25 0x74d4e570 in
QEventLoop::processEvents(QFlags)
(this=0x7fffd050, flags=...) at kernel/qeventloop.cpp:128
#26 0x74d4e86c in
QEventLoop::exec(QFlags) (this=0x7fffd050,
flags=...) at kernel/qeventloop.cpp:204
#27 0x74d52344 in QCoreApplication::exec() () at
kernel/qcoreapplication.cpp:1285
#28 0x7517d598 in QGuiApplication::exec() () at
kernel/qguiapplication.cpp:1607
#29 0x759472a1 in QApplication::exec() () at
kernel/qapplication.cpp:2979
#30 0x77bd4210 in kdemain(int, char**) (_argc=2, _argv=0x7fffdb18)
at /opt/kde/src/kde/workspace/kde-cli-tools/kcmshell/main.cpp:294
#31 0x004009a8 in main(int, char**) (argc=2, argv=0x7fffdb18) at
/opt/kde/build/kde/workspace/kde-cli-tools/kcmshell/kcmshell5_dummy.cpp:3

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

[KScreen] [Bug 365040] New: kscreen KCM cannot be used if KSCREEN_BACKEND is not set

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Bug ID: 365040
   Summary: kscreen KCM cannot be used if KSCREEN_BACKEND is not
set
   Product: KScreen
   Version: git
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: kcm
  Assignee: se...@kde.org
  Reporter: cordlandw...@kde.org

If KSCREEN_BACKEND is not set, the KCM only shows "No kscreen backend found.
Please check your kscreen installation." A workaround is explicitly setting the
variable to e.g. "QScreen" or "XRandR".
Line 137 in libkscreen/src/configoperation.cpp explicitly asks for the value of
this env variable and has no fallback code if it is not set.
However, kscreen-doctor tells me the correct preferred backend for my system:

kscreen-doctor -b
Environment: 
  * KSCREEN_BACKEND is: [not set]
  * KSCREEN_BACKEND_INPROCESS : [not set]
Preferred KScreen backend : KSC_XRandR.so
Available KScreen backends:
  * KSC_Fake.so:
/opt/kde/install/kf5/lib/x86_64-linux-gnu/plugins/kf5/kscreen/KSC_Fake.so
  * KSC_KWayland.so:
/opt/kde/install/kf5/lib/x86_64-linux-gnu/plugins/kf5/kscreen/KSC_KWayland.so
  * KSC_QScreen.so:
/opt/kde/install/kf5/lib/x86_64-linux-gnu/plugins/kf5/kscreen/KSC_QScreen.so
  * KSC_XRandR.so:
/opt/kde/install/kf5/lib/x86_64-linux-gnu/plugins/kf5/kscreen/KSC_XRandR.so
  * KSC_XRandR11.so:
/opt/kde/install/kf5/lib/x86_64-linux-gnu/plugins/kf5/kscreen/KSC_XRandR11.so

Output of kscreen-console bug:
cordlandwehr@weatherwax:~/.local5$ kscreen-console bug
kscreen-console(26229)/(default) main: START: Requesting Config
kscreen-console(26229)/(kscreen) KScreen::BackendManager::startBackend:
starting external backend launcher for ""
kscreen-console(26229)/(default) configReceived: Received config. Took 278
milliseconds

xrandr --verbose==
Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767
eDP1 connected 1920x1080+0+0 (0x4d) normal (normal left inverted right x axis y
axis) 309mm x 173mm
Identifier: 0x43
Timestamp:  66102451
Subpixel:   unknown
Gamma:  1.0:1.0:1.0
Brightness: 1.0
Clones:
CRTC:   0
CRTCs:  0 1 2
Transform:  1.00 0.00 0.00
0.00 1.00 0.00
0.00 0.00 1.00
   filter: 
EDID: 
000006af3d12
00160104951f11780287e5a456509e26
0d50540001010101010101010101
010101010101143780b8703824401010
3e0035ad1018000f
002000fe0041
554f0a20202020202020202000fe
004231343048414e30312e32200a00a3
BACKLIGHT: 426 
range: (0, 851)
Backlight: 426 
range: (0, 851)
scaling mode: Full aspect 
supported: None, Full, Center, Full aspect
Broadcast RGB: Automatic 
supported: Automatic, Full, Limited 16:235
audio: auto 
supported: force-dvi, off, auto, on
  1920x1080 (0x4d) 141.000MHz -HSync -VSync *current +preferred
h: width  1920 start 1936 end 1952 total 2104 skew0 clock  67.02KHz
v: height 1080 start 1083 end 1097 total 1116   clock  60.05Hz
  1920x1080 (0xee) 138.500MHz +HSync -VSync
h: width  1920 start 1968 end 2000 total 2080 skew0 clock  66.59KHz
v: height 1080 start 1083 end 1088 total    clock  59.93Hz
  1680x1050 (0xef) 146.250MHz -HSync +VSync
h: width  1680 start 1784 end 1960 total 2240 skew0 clock  65.29KHz
v: height 1050 start 1053 end 1059 total 1089   clock  59.95Hz
  1680x1050 (0xf0) 119.000MHz +HSync -VSync
h: width  1680 start 1728 end 1760 total 1840 skew0 clock  64.67KHz
v: height 1050 start 1053 end 1059 total 1080   clock  59.88Hz
  1600x1024 (0xf1) 103.125MHz +HSync +VSync
h: width  1600 start 1600 end 1656 total 1664 skew0 clock  61.97KHz
v: height 1024 start 1024 end 1029 total 1030   clock  60.17Hz
  1400x1050 (0xf2) 122.000MHz +HSync +VSync
h: width  1400 start 1488 end 1640 total 1880 skew0 clock  64.89KHz
v: height 1050 start 1052 end 1064 total 1082   clock  59.98Hz
  1600x900 (0xf3) 118.997MHz -HSync +VSync
h: width  1600 start 1696 end 1864 total 2128 skew0 clock  55.92KHz
v: height  900 start  901 end  904 total  932   clock  60.00Hz
  1280x1024 (0xf4) 108.000MHz +HSync +VSync
h: width  1280 start 1328 end 1440 total 1688 skew0 clock  63.98KHz
v: height 1024 start 1025 end 1028 total 1066   clock  60.02Hz
  1440x900 (0xf5) 106.500MHz -HSync +VSync
h: width  

[parley] [Bug 362799] can't write export file

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||cordlandw...@kde.org
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Could you provide the exact steps how you try to export your practice results?
E.g. the exact menu entry/button you use?

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

[parley] [Bug 364211] Parley crashes after creating a new file - everytime

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||cordlandw...@kde.org
 Resolution|--- |WORKSFORME

--- Comment #2 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Without a backtrace, unfortunately it is not possible to investigate this
problem. Following the given steps, I cannot reproduce the reported issue.
However, I *think* this problem is fixed (there is a recent fix). But this is
impossible to say without looking at a backtrace. Hence, I am closing this
report for now. If you can provide a backtrace as described in the above given
link, please feel free to re-open it.

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

[kmail2] [Bug 364721] KMail Crash every time I press "Enter" for completing a mail recipient.

[Andreas Cord-Landwehr via KDE Bugzilla]

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

--- Comment #2 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
I can still reproduce it with yesterday night's master branch (updated
kdesrc-build groups kde-pimlibs and kde-pim; restarted Akonadi).

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

[kmail2] [Bug 364721] New: KMail Crash every time I press "Enter" for completing a mail recipient.

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Bug ID: 364721
   Summary: KMail Crash every time I press "Enter" for completing
a mail recipient.
   Product: kmail2
   Version: Git (master)
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: composer
  Assignee: kdepim-b...@kde.org
  Reporter: cordlandw...@kde.org

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

As explained in the title: KMail Crash every time I press "Enter" for
completing a mail recipient.

(I am pasting only the problematic thread)

Thread 1 (Thread 0x7f0b08f4d940 (LWP 7992)):
[KCrash Handler]
#6  0x7f0b25457458 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:55
#7  0x7f0b254588da in __GI_abort () at abort.c:89
#8  0x7f0b2610681e in qt_message_fatal(QtMsgType, QMessageLogContext
const&, QString const&) (context=..., message=...) at global/qlogging.cpp:1648
#9  0x7f0b26102cd6 in QMessageLogger::fatal(char const*, ...) const
(this=0x7ffce93e9570, msg=0x7f0b26435530 "ASSERT: \"%s\" in file %s, line %d")
at global/qlogging.cpp:790
#10 0x7f0b260fbe4e in qt_assert(char const*, char const*, int)
(assertion=0x7f0b292b6ace "!mReadingFinished", file=0x7f0b292b6a20
"/opt/kde/src/kde/pim/akonadi/src/core/jobs/job.cpp", line=69) at
global/qglobal.cpp:2999
#11 0x7f0b29224046 in Akonadi::JobPrivate::handleResponse(long long,
Akonadi::Protocol::Command const&) (this=0x63c8c20, tag=16, response=...) at
/opt/kde/src/kde/pim/akonadi/src/core/jobs/job.cpp:69
#12 0x7f0b291e5932 in Akonadi::SessionPrivate::handleCommand(long long,
Akonadi::Protocol::Command const&) (this=0x754abf0, tag=16, cmd=...) at
/opt/kde/src/kde/pim/akonadi/src/core/session.cpp:143
#13 0x7f0b291e7655 in Akonadi::Session::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (_o=0x753f050,
_c=QMetaObject::InvokeMetaMethod, _id=4, _a=0x7f0a90003090) at
/opt/kde/build/kde/pim/akonadi/src/core/moc_session.cpp:118
#14 0x7f0b26386d07 in QMetaCallEvent::placeMetaCall(QObject*)
(this=0x7f0a90002630, object=0x753f050) at kernel/qobject.cpp:495
#15 0x7f0b26387da0 in QObject::event(QEvent*) (this=0x753f050,
e=0x7f0a90002630) at kernel/qobject.cpp:1256
#16 0x7f0b271104f2 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=0x2196f80, receiver=0x753f050, e=0x7f0a90002630) at
kernel/qapplication.cpp:3804
#17 0x7f0b2710d8bd in QApplication::notify(QObject*, QEvent*)
(this=0x7ffce93ea6a0, receiver=0x753f050, e=0x7f0a90002630) at
kernel/qapplication.cpp:3163
#18 0x7f0b2634dbfa in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x753f050, event=0x7f0a90002630) at kernel/qcoreapplication.cpp:1015
#19 0x7f0b26351c30 in QCoreApplication::sendEvent(QObject*, QEvent*)
(receiver=0x753f050, event=0x7f0a90002630) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:225
#20 0x7f0b2634efe2 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x21905d0) at
kernel/qcoreapplication.cpp:1650
#21 0x7f0b2634e962 in QCoreApplication::sendPostedEvents(QObject*, int)
(receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1508
#22 0x7f0b263c7b2c in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x21e2df0) at kernel/qeventdispatcher_glib.cpp:270
#23 0x7f0b148e61a7 in g_main_context_dispatch (context=0x7f0b16f0) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3154
#24 0x7f0b148e61a7 in g_main_context_dispatch
(context=context@entry=0x7f0b16f0) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3769
#25 0x7f0b148e6400 in g_main_context_iterate
(context=context@entry=0x7f0b16f0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3840
#26 0x7f0b148e64ac in g_main_context_iteration (context=0x7f0b16f0,
may_block=1) at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3901
#27 0x7f0b263c8305 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x21f30c0, flags=...) at kernel/qeventdispatcher_glib.cpp:417
#28 0x7f0b08cf2e86 in
QPAEventDispatcherGlib::processEvents(QFlags)
(this=0x21f30c0, flags=...) at eventdispatchers/qeventdispatcher_glib.cpp:115
#29 0x7f0b2634a570 in
QEventLoop::processEvents(QFlags)
(this=0x7ffce93ea5b0, flags=...) at kernel/qeventloop.cpp:128
#30 0x7f0b2634a86c in
QEventLoop::exec(QFlags) (this=0x7ffce93ea5b0,
flags=...) at kernel/qeventloop.cpp:204
#31 0x7f0b2634e344 in QCoreApplication::exec() () at
kernel/qcoreapplication.cpp:1285
#32 0x7f0b26943598 in QGuiApplication::exec() () at
kernel/qguiapplication.cpp:1607
#33 0x7f0b2710d2a1 in QApplication::exec() () at
kernel/qapplication.cpp:2979
#34 0x004058f8 in main(int, char**) (argc=1, argv=0x7ffce93ead28) at

[Artikulate] [Bug 364718] hangs when launched - no GUI appears

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #4 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
I am afraid, this is a packaging problem (though one that is very hard to fix):
- the dependency QtGStreamer is linked against GStreamer 1.x API
- the dependency QtMultimedia is linked against GStreamer 0.10 API
Both GStreamer API versions are mutual exclusive in a program and cause it to
stop/deadlock. Your distribution would have to update the QtMultimedia
dependency to 1.x API. Yet that requires a big patch and a considerable amount
of work (I did this for the Debian packages). And as Qt4 slowly comes to end of
its life, I am not sure if your distribution want to invest that time.
Moreover, you use Artikulate still from a KDE SC 4 release. Newer versions
depending on Qt5 do not have this problem anymore, since we can avoid using
both at the same time.

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

[Artikulate] [Bug 364718] hangs when launched - no GUI appears

[Andreas Cord-Landwehr via KDE Bugzilla]

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

--- Comment #2 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Could you paste the output of "ldd `whereis artikulate`"?

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

[kdevelop] [Bug 317013] "Remove" and "rename" context menu items in "Project" toolview doesn't work

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |WORKSFORME
 CC||cordlandw...@kde.org

--- Comment #7 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Closing because of inactivity. If this is still a problem, please reopen.

I can remember this problem to exist in earlier version of the KF5 port, but
also cannot remember it anymore.

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

[kdevelop] [Bug 361068] Icon for Kdevelop

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

 CC||cordlandw...@kde.org
 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Could you check that that the breeze icon package is installed?

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

[kdevelop] [Bug 364145] Crash in QML Parser while parsing QtDeclarative [DeclarationBuilder::closeAndAssignType]

[Andreas Cord-Landwehr via KDE Bugzilla]

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

--- Comment #1 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Created attachment 99520
  --> https://bugs.kde.org/attachment.cgi?id=99520=edit
The problematic file causing the assert

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

[krunner] [Bug 364342] New: KRunner crash by Akonadi's PIMContactsRunner

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Bug ID: 364342
   Summary: KRunner crash by Akonadi's PIMContactsRunner
   Product: krunner
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: m...@vhanda.in
  Reporter: cordlandw...@kde.org

Application: krunner (5.6.90)
 (Compiled from sources)
Qt Version: 5.6.1
Frameworks Version: 5.23.0
Operating System: Linux 4.5.0-2-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
Crash occured when by opening KRunner.
See backtrace, it directly tells the reason.

-- Backtrace:
Application: krunner (krunner), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7fa5920b1900 (LWP 1521))]

Thread 13 (Thread 0x7fa58ed8a700 (LWP 1534)):
#0  0x7fa5a0c7adcd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa59fabd382 in _xcb_conn_wait (__timeout=-1, __nfds=1,
__fds=0x7fa58ed89b80) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  0x7fa59fabd382 in _xcb_conn_wait (c=c@entry=0x218cb40,
cond=cond@entry=0x218cb80, vector=vector@entry=0x0, count=count@entry=0x0) at
../../src/xcb_conn.c:459
#3  0x7fa59fabeff7 in xcb_wait_for_event (c=0x218cb40) at
../../src/xcb_in.c:693
#4  0x7fa591e0dadd in QXcbEventReader::run() (this=0x21971a0) at
qxcbconnection.cpp:1325
#5  0x7fa5a18d42e5 in QThreadPrivate::start(void*) (arg=0x21971a0) at
thread/qthread_unix.cpp:340
#6  0x7fa59d1e5454 in start_thread (arg=0x7fa58ed8a700) at
pthread_create.c:334
#7  0x7fa5a0c83e5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7fa58d444700 (LWP 1539)):
#0  0x7fa5990ab8e0 in g_main_context_prepare
(context=context@entry=0x7fa58990, priority=priority@entry=0x7fa58d443a80)
at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3424
#1  0x7fa5990ac2cb in g_main_context_iterate
(context=context@entry=0x7fa58990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3820
#2  0x7fa5990ac4ac in g_main_context_iteration (context=0x7fa58990,
may_block=1) at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3901
#3  0x7fa5a1b80334 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fa588c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  0x7fa5a1b02570 in
QEventLoop::processEvents(QFlags)
(this=0x7fa58d443c30, flags=...) at kernel/qeventloop.cpp:128
#5  0x7fa5a1b0286c in
QEventLoop::exec(QFlags) (this=0x7fa58d443c30,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7fa5a18cc276 in QThread::exec() (this=0x7fa5a35f05e0 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:504
#7  0x7fa5a3556860 in QDBusConnectionManager::run() (this=0x7fa5a35f05e0
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:181
#8  0x7fa5a18d42e5 in QThreadPrivate::start(void*) (arg=0x7fa5a35f05e0
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:340
#9  0x7fa59d1e5454 in start_thread (arg=0x7fa58d444700) at
pthread_create.c:334
#10 0x7fa5a0c83e5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7fa586b27700 (LWP 1562)):
#0  0x7fa5a0c7adcd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa5990ac39c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7fa57c002e70, timeout=, context=0x7fa57c000990) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:4135
#2  0x7fa5990ac39c in g_main_context_iterate
(context=context@entry=0x7fa57c000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3835
#3  0x7fa5990ac4ac in g_main_context_iteration (context=0x7fa57c000990,
may_block=1) at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3901
#4  0x7fa5a1b80334 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fa57c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5  0x7fa5a1b02570 in
QEventLoop::processEvents(QFlags)
(this=0x7fa586b26c60, flags=...) at kernel/qeventloop.cpp:128
#6  0x7fa5a1b0286c in
QEventLoop::exec(QFlags) (this=0x7fa586b26c60,
flags=...) at kernel/qeventloop.cpp:204
#7  0x7fa5a18cc276 in QThread::exec() (this=0x24210c0) at
thread/qthread.cpp:504
#8  0x7fa5a4350487 in QQmlThreadPrivate::run() (this=0x24210c0) at
qml/ftw/qqmlthread.cpp:141
#9  0x7fa5a18d42e5 in QThreadPrivate::start(void*) (arg=0x24210c0) at
thread/qthread_unix.cpp:340
#10 0x7fa59d1e5454 in start_thread (arg=0x7fa586b27700) at
pthread_create.c:334

[kdevelop] [Bug 364317] Crash when executing multiple tests

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

Version|unspecified |git master
Summary|Crash when executing|Crash when executing
   |multiple tests (master  |multiple tests
   |branch) |

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

[kdevelop] [Bug 363931] Crash in CMake Background Parser [CMakeFunctionArgument::CMakeFunctionArgument, DeclarationBuilder::startVisiting]

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

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

--- Comment #6 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Daniel, can you retest with current master? The cmake parsing crash should be
fixed with b4263571146bab54459dd0aa122fc5dc604705d5. If not, please feel free
to re-open.

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

[kdevelop] [Bug 364317] New: Crash when executing multiple tests (master branch)

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Bug ID: 364317
   Summary: Crash when executing multiple tests (master branch)
   Product: kdevelop
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: cordlandw...@kde.org

Application: kdevelop (4.90.92)
 (Compiled from sources)
Qt Version: 5.6.1
Frameworks Version: 5.23.0
Operating System: Linux 4.5.0-2-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

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

I started to run multiple unit tests from the ctest plugin at once (by run all
tests). Several popups where displayed that a unit test was already running,
asking to terminate a test.
When I clicked "kill", this crash appeared.

It is reproduceable.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4d13129940 (LWP 18344))]

Thread 18 (Thread 0x7f4d0eff1700 (LWP 18346)):
#0  0x7f4d2d398dcd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f4d1fc1e39c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7f4da580, timeout=, context=0x7f4d0990) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:4135
#2  0x7f4d1fc1e39c in g_main_context_iterate
(context=context@entry=0x7f4d0990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3835
#3  0x7f4d1fc1e4ac in g_main_context_iteration (context=0x7f4d0990,
may_block=1) at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3901
#4  0x7f4d2e25d334 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f4d08c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5  0x7f4d2e1df570 in
QEventLoop::processEvents(QFlags)
(this=0x7f4d0eff0bf0, flags=...) at kernel/qeventloop.cpp:128
#6  0x7f4d2e1df86c in
QEventLoop::exec(QFlags) (this=0x7f4d0eff0bf0,
flags=...) at kernel/qeventloop.cpp:204
#7  0x7f4d2dfa9276 in QThread::exec() (this=0x7f4d351b65e0 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:504
#8  0x7f4d3511c860 in QDBusConnectionManager::run() (this=0x7f4d351b65e0
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:181
#9  0x7f4d2dfb12e5 in QThreadPrivate::start(void*) (arg=0x7f4d351b65e0
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:340
#10 0x7f4d249a0454 in start_thread (arg=0x7f4d0eff1700) at
pthread_create.c:334
#11 0x7f4d2d3a1e5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 17 (Thread 0x7f4cfb26b700 (LWP 18348)):
#0  0x7f4d249a63f8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7f4d2dfb29d9 in QWaitConditionPrivate::wait_relative(unsigned long)
(this=0x3db30a0, time=1000) at thread/qwaitcondition_unix.cpp:126
#2  0x7f4d2dfb2a06 in QWaitConditionPrivate::wait(unsigned long)
(this=0x3db30a0, time=1000) at thread/qwaitcondition_unix.cpp:134
#3  0x7f4d2dfb27f5 in QWaitCondition::wait(QMutex*, unsigned long)
(this=0x3db0c88, mutex=0x3db0c90, time=1000) at
thread/qwaitcondition_unix.cpp:208
#4  0x7f4d2b2f60c3 in KDevelop::DUChainPrivate::CleanupThread::run()
(this=0x3db0c70) at
/opt/kde/src/extragear/kdevelop/kdevplatform/language/duchain/duchain.cpp:282
#5  0x7f4d2dfb12e5 in QThreadPrivate::start(void*) (arg=0x3db0c70) at
thread/qthread_unix.cpp:340
#6  0x7f4d249a0454 in start_thread (arg=0x7f4cfb26b700) at
pthread_create.c:334
#7  0x7f4d2d3a1e5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 16 (Thread 0x7f4cf8a7b700 (LWP 18350)):
#0  0x7f4d2dfa5ea9 in
std::atomic::compare_exchange_strong(QMutexData*&, QMutexData*,
std::memory_order) (__m2=std::memory_order_acquire,
__m1=std::memory_order_acquire, __p2=0x1, __p1=@0x7f4cf8a7a870: 0x0,
this=0x45fe178) at /usr/include/c++/5/bits/atomic_base.h:752
#1  0x7f4d2dfa5ea9 in
std::atomic::compare_exchange_strong(QMutexData*&, QMutexData*,
std::memory_order) (this=0x45fe178, __p1=@0x7f4cf8a7a870: 0x0, __p2=0x1,
__m=std::memory_order_acquire) at /usr/include/c++/5/atomic:475
#2  0x7f4d2dfa5cbf in
QAtomicOps::testAndSetAcquire(std::atomic&,
QMutexData*, QMutexData*, QMutexData**) (_q_value=..., expectedValue=0x0,
newValue=0x1, currentValue=0x7f4cf8a7a908) at
../../include/QtCore/../../src/corelib/arch/qatomic_cxx11.h:158
#3  0x7f4d2dfa5b9a in
QBasicAtomicPointer::testAndSetAcquire(QMutexData*, QMutexData*,
QMutexData*&) (this=0x45fe178, 

[KScreen] [Bug 364044] Second screen in docking station keeps black after suspend

[Andreas Cord-Landwehr via KDE Bugzilla]

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

--- Comment #5 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Via kickoff -> Leave -> Suspend

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

[kdevelop] [Bug 364145] New: Crash in QML Parser while parsing QtDeclarative

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Bug ID: 364145
   Summary: Crash in QML Parser while parsing QtDeclarative
   Product: kdevelop
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: QML/JavaScript
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: cordlandw...@kde.org

Application: KDevelop (kdevelop), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7fe6525b88c0 (LWP 11669))]

Thread 10 (Thread 0x7fe633307700 (LWP 11670)):
#0  0x7fe64ea72e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fe6413c6c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fe6413c88d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fe6342a32c9 in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/plugins/platforms/../../lib/libQt5XcbQpa.so.5
#4  0x7fe64f16762f in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#5  0x7fe647c436fa in start_thread (arg=0x7fe633307700) at
pthread_create.c:333
#6  0x7fe64ea7eb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7fe61f736700 (LWP 11672)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7fe64f168598 in QWaitCondition::wait(QMutex*, unsigned long) () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#2  0x7fe64c837958 in KDevelop::DUChainPrivate::CleanupThread::run
(this=0x31fcb60) at
/opt/nightly/src/extragear/kdevelop/kdevplatform/language/duchain/duchain.cpp:282
#3  0x7fe64f16762f in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#4  0x7fe647c436fa in start_thread (arg=0x7fe61f736700) at
pthread_create.c:333
#5  0x7fe64ea7eb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7fe615a1f700 (LWP 11681)):
#0  __libc_disable_asynccancel () at
../sysdeps/unix/sysv/linux/x86_64/cancellation.S:98
#1  0x7fe64ea72e99 in poll () at ../sysdeps/unix/syscall-template.S:84
#2  0x7fe64674131c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fe64674142c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fe64f3aaa9c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#5  0x7fe64f353212 in
QEventLoop::exec(QFlags) () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#6  0x7fe64f1627bc in QThread::exec() () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#7  0x7fe64c1dd0f5 in ?? () from /opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Qml.so.5
#8  0x7fe64f16762f in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#9  0x7fe647c436fa in start_thread (arg=0x7fe615a1f700) at
pthread_create.c:333
#10 0x7fe64ea7eb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7fe6293f4700 (LWP 11693)):
#0  0x7fe646785a64 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fe6467408a0 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fe64674124b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fe64674142c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fe64f3aaa9c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#5  0x7fe64f353212 in
QEventLoop::exec(QFlags) () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#6  0x7fe64f1627bc in QThread::exec() () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#7  0x7fe64f16762f in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#8  0x7fe647c436fa in start_thread (arg=0x7fe6293f4700) at
pthread_create.c:333
#9  0x7fe64ea7eb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7fe60d6a3700 (LWP 11697)):
#0  0x7fe646785a49 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fe646741418 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fe64f3aaa9c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#3  0x7fe64f353212 in
QEventLoop::exec(QFlags) () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#4  0x7fe64f1627bc in QThread::exec() () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#5  0x7fe64c99c27c in KDevelop::CompletionWorkerThread::run
(this=0x2477bc0) at
/opt/nightly/src/extragear/kdevelop/kdevplatform/language/codecompletion/codecompletionmodel.cpp:89
#6  0x7fe64f16762f in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#7  0x7fe647c436fa in start_thread (arg=0x7fe60d6a3700) at

[KScreen] [Bug 364044] Second screen in docking station keeps black after suspend

[Andreas Cord-Landwehr via KDE Bugzilla]

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

--- Comment #2 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Hi Sebas, restarting kded5 makes no change when I am in the state after
resuming on one monitor does not get a signal.

Output of kscreen-console bug:

cordlandwehr@weatherwax:/tmp$ kscreen-console bug
kscreen-console(30373)/(default) main: START: Requesting Config
kscreen-console(30373)/(kscreen) KScreen::BackendManager::startBackend:
starting external backend launcher for ""
kscreen-console(30373)/(default) configReceived: Received config. Took 47
milliseconds

xrandr --verbose==
Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767
eDP1 connected primary 1920x1080+0+0 (0x4d) normal (normal left inverted right
x axis y axis) 309mm x 173mm
Identifier: 0x43
Timestamp:  131887559
Subpixel:   unknown
Gamma:  1.0:1.0:1.0
Brightness: 1.0
Clones:
CRTC:   0
CRTCs:  0 1 2
Transform:  1.00 0.00 0.00
0.00 1.00 0.00
0.00 0.00 1.00
   filter: 
EDID: 
000006af3d12
00160104951f11780287e5a456509e26
0d50540001010101010101010101
010101010101143780b8703824401010
3e0035ad1018000f
002000fe0041
554f0a20202020202020202000fe
004231343048414e30312e32200a00a3
BACKLIGHT: 426 
range: (0, 851)
Backlight: 426 
range: (0, 851)
scaling mode: Full aspect 
supported: None, Full, Center, Full aspect
Broadcast RGB: Automatic 
supported: Automatic, Full, Limited 16:235
audio: auto 
supported: force-dvi, off, auto, on
  1920x1080 (0x4d) 141.000MHz -HSync -VSync *current +preferred 
h: width  1920 start 1936 end 1952 total 2104 skew0 clock  67.02KHz 
v: height 1080 start 1083 end 1097 total 1116   clock  60.05Hz  
  1920x1080 (0xee) 138.500MHz +HSync -VSync 
h: width  1920 start 1968 end 2000 total 2080 skew0 clock  66.59KHz 
v: height 1080 start 1083 end 1088 total    clock  59.93Hz  
  1680x1050 (0xef) 146.250MHz -HSync +VSync 
h: width  1680 start 1784 end 1960 total 2240 skew0 clock  65.29KHz 
v: height 1050 start 1053 end 1059 total 1089   clock  59.95Hz  
  1680x1050 (0xf0) 119.000MHz +HSync -VSync 
h: width  1680 start 1728 end 1760 total 1840 skew0 clock  64.67KHz 
v: height 1050 start 1053 end 1059 total 1080   clock  59.88Hz  
  1600x1024 (0xf1) 103.125MHz +HSync +VSync 
h: width  1600 start 1600 end 1656 total 1664 skew0 clock  61.97KHz 
v: height 1024 start 1024 end 1029 total 1030   clock  60.17Hz  
  1400x1050 (0xf2) 122.000MHz +HSync +VSync 
h: width  1400 start 1488 end 1640 total 1880 skew0 clock  64.89KHz 
v: height 1050 start 1052 end 1064 total 1082   clock  59.98Hz
  1600x900 (0xf3) 118.997MHz -HSync +VSync
h: width  1600 start 1696 end 1864 total 2128 skew0 clock  55.92KHz
v: height  900 start  901 end  904 total  932   clock  60.00Hz
  1280x1024 (0xf4) 108.000MHz +HSync +VSync
h: width  1280 start 1328 end 1440 total 1688 skew0 clock  63.98KHz
v: height 1024 start 1025 end 1028 total 1066   clock  60.02Hz
  1440x900 (0xf5) 106.500MHz -HSync +VSync
h: width  1440 start 1520 end 1672 total 1904 skew0 clock  55.93KHz
v: height  900 start  903 end  909 total  934   clock  59.89Hz
  1280x960 (0xf6) 108.000MHz +HSync +VSync
h: width  1280 start 1376 end 1488 total 1800 skew0 clock  60.00KHz
v: height  960 start  961 end  964 total 1000   clock  60.00Hz
  1368x768 (0xf7) 85.860MHz -HSync +VSync
h: width  1368 start 1440 end 1584 total 1800 skew0 clock  47.70KHz
v: height  768 start  769 end  772 total  795   clock  60.00Hz
  1360x768 (0xf8) 84.750MHz -HSync +VSync
h: width  1360 start 1432 end 1568 total 1776 skew0 clock  47.72KHz
v: height  768 start  771 end  781 total  798   clock  59.80Hz
  1360x768 (0xf9) 72.000MHz +HSync -VSync
h: width  1360 start 1408 end 1440 total 1520 skew0 clock  47.37KHz
v: height  768 start  771 end  781 total  790   clock  59.96Hz
  1152x864 (0xfa) 81.620MHz -HSync +VSync
h: width  1152 start 1216 end 1336 total 1520 skew0 clock  53.70KHz
v: h

[frameworks-knewstuff] [Bug 340111] Get new themes/icons/styles fails with 'Network Error: (6)' message

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

 CC||cordlandw...@kde.org

--- Comment #8 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Hi Xavier, is the problem still present?

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

[frameworks-knewstuff] [Bug 342172] System Settings Add-On Installer Fails

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO
 CC||cordlandw...@kde.org

--- Comment #9 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Can you try to disable the network cache as explained in
https://bugs.kde.org/show_bug.cgi?id=348049 ?
It's possible that we have a duplicate bug report here.

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

[KScreen] [Bug 364044] New: Second screen in docking station keeps black after suspend

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Bug ID: 364044
   Summary: Second screen in docking station keeps black after
suspend
   Product: KScreen
   Version: git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: se...@kde.org
  Reporter: cordlandw...@kde.org

On my Lenovo Pro docking stations, I have one additional monitor connected.
After setting the laptop screen as primary and the additional screen as an
extended screen, I suspend the laptop.
When resuming the session, the laptop monitor is shown correctly. Yet the
second monitor says "no signal", even if kscreen tells me that it is enabled
and working.

The workaround to make the second monitor work again is: Disable the monitor in
kscreen, apply this, enabled the monitor again, apply again.

Reproducible: Always

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

[dolphin] [Bug 363982] New: QVector out of range access in kitemlistviewaccessible.cpp

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Bug ID: 363982
   Summary: QVector out of range access in
kitemlistviewaccessible.cpp
   Product: dolphin
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: cordlandw...@kde.org

I got the following crash on my current Git-master version of dolphin:

Application: Dolphin (dolphin), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb735da1940 (LWP 21360))]

Thread 4 (Thread 0x7fb732663700 (LWP 21363)):
#0  0x7fb742f1fdcd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fb73ed46382 in _xcb_conn_wait (__timeout=-1, __nfds=1,
__fds=0x7fb732662b40) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  0x7fb73ed46382 in _xcb_conn_wait (c=c@entry=0xa5d8a0,
cond=cond@entry=0xa5d8e0, vector=vector@entry=0x0, count=count@entry=0x0) at
../../src/xcb_conn.c:459
#3  0x7fb73ed47ff7 in xcb_wait_for_event (c=0xa5d8a0) at
../../src/xcb_in.c:693
#4  0x7fb735afdadd in QXcbEventReader::run() (this=0xa67f70) at
qxcbconnection.cpp:1325
#5  0x7fb743b782e5 in QThreadPrivate::start(void*) (arg=0xa67f70) at
thread/qthread_unix.cpp:340
#6  0x7fb74023f454 in start_thread (arg=0x7fb732663700) at
pthread_create.c:334
#7  0x7fb742f28e5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fb731283700 (LWP 21364)):
#0  0x7fb743b491de in QMutexLocker::QMutexLocker(QBasicMutex*)
(this=0x7fb731282920, m=0xaaa7a8) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:129
#1  0x7fb743e20aae in QThreadData::canWaitLocked() (this=0xaaa780) at
../../include/QtCore/5.6.1/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:247
#2  0x7fb743e23a6d in postEventSourcePrepare(GSource*, gint*)
(s=0x7fb7240012d0, timeout=0x7fb7312829b4) at
kernel/qeventdispatcher_glib.cpp:253
#3  0x7fb73b41092d in g_main_context_prepare
(context=context@entry=0x7fb724000990, priority=priority@entry=0x7fb731282a40)
at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3442
#4  0x7fb73b4112cb in g_main_context_iterate
(context=context@entry=0x7fb724000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3820
#5  0x7fb73b4114ac in g_main_context_iteration (context=0x7fb724000990,
may_block=1) at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3901
#6  0x7fb743e24334 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fb7240008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#7  0x7fb743da6570 in
QEventLoop::processEvents(QFlags)
(this=0x7fb731282bf0, flags=...) at kernel/qeventloop.cpp:128
#8  0x7fb743da686c in
QEventLoop::exec(QFlags) (this=0x7fb731282bf0,
flags=...) at kernel/qeventloop.cpp:204
#9  0x7fb743b70276 in QThread::exec() (this=0x7fb7441725e0 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:504
#10 0x7fb7440d8860 in QDBusConnectionManager::run() (this=0x7fb7441725e0
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:181
#11 0x7fb743b782e5 in QThreadPrivate::start(void*) (arg=0x7fb7441725e0
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:340
#12 0x7fb74023f454 in start_thread (arg=0x7fb731283700) at
pthread_create.c:334
#13 0x7fb742f28e5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fb7238c3700 (LWP 21365)):
#0  0x7fb742f1bdad in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fb73b454740 in g_wakeup_acknowledge (__nbytes=16,
__buf=0x7fb7238c29a0, __fd=) at
/usr/include/x86_64-linux-gnu/bits/unistd.h:44
#2  0x7fb73b454740 in g_wakeup_acknowledge (wakeup=0x7fb7240025a0) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gwakeup.c:210
#3  0x7fb73b410e84 in g_main_context_check
(context=context@entry=0x7fb71c000990, max_priority=2147483647,
fds=fds@entry=0x7fb71c002e20, n_fds=n_fds@entry=1) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3632
#4  0x7fb73b411340 in g_main_context_iterate
(context=context@entry=0x7fb71c000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3837
#5  0x7fb73b4114ac in g_main_context_iteration (context=0x7fb71c000990,
may_block=1) at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3901
#6  0x7fb743e24334 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fb71c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#7  0x7fb743da6570 in
QEventLoop::processEvents(QFlags)
(this=0x7fb7238c2c20, flags=...) at kernel/qeventloop.cpp:128
#8  0x7fb743da686c in

[kdevelop] [Bug 363713] Crash in QML Parser

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kdev
   ||platform/6e56496997feebee5e
   ||3bde86c9b4823125156f46
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED FIXED
  Latest Commit||http://commits.kde.org/kdev
   ||platform/46d2612955c8f390a7
   ||f657f1e7b257b51a7bd6c9
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Git commit 6e56496997feebee5e3bde86c9b4823125156f46 by Andreas Cord-Landwehr.
Committed on 02/06/2016 at 17:23.
Pushed by cordlandwehr into branch '5.0'.

Fix declaration name access if not fully parsed

Summary:
Fixes the crash in KDE bug #363713 that is caused by requesting code
completion on a not fully parsed QML file. For details, please see
backtrace in bug report.

Reviewers: mwolff, #kdevelop, kfunk

Reviewed By: #kdevelop, kfunk

Subscribers: kfunk, kdevelop-devel

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


http://commits.kde.org/kdevplatform/6e56496997feebee5e3bde86c9b4823125156f46

--- Comment #2 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Git commit 46d2612955c8f390a7f657f1e7b257b51a7bd6c9 by Andreas Cord-Landwehr.
Committed on 01/06/2016 at 19:22.
Pushed by cordlandwehr into branch '5.0'.

Fix declaration name access if not fully parsed

Fixes the crash in KDE bug #363713 that is caused by requesting code
completion on a not fully parsed file. For details, please see
backtrace in bug report.

M  +3-0language/codecompletion/normaldeclarationcompletionitem.cpp

http://commits.kde.org/kdevplatform/46d2612955c8f390a7f657f1e7b257b51a7bd6c9

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

[kdevelop] [Bug 363707] Assert when parsing project

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kdev
   ||elop/b4263571146bab54459dd0
   ||aa122fc5dc604705d5
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED FIXED
  Latest Commit||http://commits.kde.org/kdev
   ||elop/bef8072e620ecaac9cdaf2
   ||7c1996167caa7f75b5
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Git commit b4263571146bab54459dd0aa122fc5dc604705d5 by Andreas Cord-Landwehr.
Committed on 02/06/2016 at 05:13.
Pushed by cordlandwehr into branch '5.0'.

Handle CMake methods/functions without arguments gracefully

Summary:
Fixes crash from KDE bug #363707. For details see backtrace in
bug report.

Reviewers: apol, #kdevelop

Reviewed By: apol, #kdevelop

Subscribers: kdevelop-devel

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


http://commits.kde.org/kdevelop/b4263571146bab54459dd0aa122fc5dc604705d5

--- Comment #3 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Git commit bef8072e620ecaac9cdaf27c1996167caa7f75b5 by Andreas Cord-Landwehr.
Committed on 01/06/2016 at 19:54.
Pushed by cordlandwehr into branch '5.0'.

Handle CMake methods/functions without arguments gracefully

Fixes crash from KDE bug #363707. For details see backtrace in
bug report.

M  +6-0projectmanagers/cmake/duchain/declarationbuilder.cpp

http://commits.kde.org/kdevelop/bef8072e620ecaac9cdaf27c1996167caa7f75b5

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

[kdevelop] [Bug 363707] Assert when parsing project

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kdev
   ||elop/b4263571146bab54459dd0
   ||aa122fc5dc604705d5
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED FIXED
  Latest Commit||http://commits.kde.org/kdev
   ||elop/bef8072e620ecaac9cdaf2
   ||7c1996167caa7f75b5
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Git commit b4263571146bab54459dd0aa122fc5dc604705d5 by Andreas Cord-Landwehr.
Committed on 02/06/2016 at 05:13.
Pushed by cordlandwehr into branch '5.0'.

Handle CMake methods/functions without arguments gracefully

Summary:
Fixes crash from KDE bug #363707. For details see backtrace in
bug report.

Reviewers: apol, #kdevelop

Reviewed By: apol, #kdevelop

Subscribers: kdevelop-devel

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


http://commits.kde.org/kdevelop/b4263571146bab54459dd0aa122fc5dc604705d5

--- Comment #3 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Git commit bef8072e620ecaac9cdaf27c1996167caa7f75b5 by Andreas Cord-Landwehr.
Committed on 01/06/2016 at 19:54.
Pushed by cordlandwehr into branch '5.0'.

Handle CMake methods/functions without arguments gracefully

Fixes crash from KDE bug #363707. For details see backtrace in
bug report.

M  +6-0projectmanagers/cmake/duchain/declarationbuilder.cpp

http://commits.kde.org/kdevelop/bef8072e620ecaac9cdaf27c1996167caa7f75b5

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

[kdevelop] [Bug 363707] Assert when parsing project

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

  Component|Language Support: CPP   |Build tools: CMake
   |(Clang-based)   |

--- Comment #1 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Looking again at the crash log, I think reassigning to the cmake build system
support more suited.

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

[kdevelop] [Bug 363713] New: Crash in QML Parser

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Bug ID: 363713
   Summary: Crash in QML Parser
   Product: kdevelop
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Language Support: QML/JavaScript
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: cordlandw...@kde.org

Crash in QML Parser while parsing project:

Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f69c587d8c0 (LWP 19155))]

Thread 12 (Thread 0x7f69a65cc700 (LWP 19156)):
#0  0x7f69c1d37e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f69b468bc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f69b468d8d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f69a75682c9 in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/plugins/platforms/../../lib/libQt5XcbQpa.so.5
#4  0x7f69c242c62f in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#5  0x7f69baf086fa in start_thread (arg=0x7f69a65cc700) at
pthread_create.c:333
#6  0x7f69c1d43b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7f6992936700 (LWP 19158)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7f69c242d598 in QWaitCondition::wait(QMutex*, unsigned long) () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#2  0x7f69bfafc958 in KDevelop::DUChainPrivate::CleanupThread::run
(this=0x31d1140) at
/opt/nightly/src/extragear/kdevelop/kdevplatform/language/duchain/duchain.cpp:282
#3  0x7f69c242c62f in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#4  0x7f69baf086fa in start_thread (arg=0x7f6992936700) at
pthread_create.c:333
#5  0x7f69c1d43b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7f6990907700 (LWP 19159)):
#0  0x7f69b9a4aa49 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f69b9a058b9 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f69b9a0624b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f69b9a0642c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f69c266fa9c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#5  0x7f69c2618212 in
QEventLoop::exec(QFlags) () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#6  0x7f69c24277bc in QThread::exec() () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#7  0x7f69c242c62f in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#8  0x7f69baf086fa in start_thread (arg=0x7f6990907700) at
pthread_create.c:333
#9  0x7f69c1d43b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7f6983fff700 (LWP 19162)):
#0  __libc_enable_asynccancel () at
../sysdeps/unix/sysv/linux/x86_64/cancellation.S:65
#1  0x7f69c1d37e82 in poll () at ../sysdeps/unix/syscall-template.S:84
#2  0x7f69b9a0631c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f69b9a0642c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f69c266fa9c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#5  0x7f69c2618212 in
QEventLoop::exec(QFlags) () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#6  0x7f69c24277bc in QThread::exec() () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#7  0x7f69bfc6127c in KDevelop::CompletionWorkerThread::run
(this=0x2385150) at
/opt/nightly/src/extragear/kdevelop/kdevplatform/language/codecompletion/codecompletionmodel.cpp:89
#8  0x7f69c242c62f in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#9  0x7f69baf086fa in start_thread (arg=0x7f6983fff700) at
pthread_create.c:333
#10 0x7f69c1d43b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7f6982292700 (LWP 19163)):
#0  0x7ffc833caa70 in ?? ()
#1  0x7ffc833cacfd in clock_gettime ()
#2  0x7f69c1d51fb6 in __GI___clock_gettime (clock_id=1, tp=0x7f6982291a20)
at ../sysdeps/unix/clock_gettime.c:115
#3  0x7f69c24da196 in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#4  0x7f69c266d599 in QTimerInfoList::updateCurrentTime() () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#5  0x7f69c266daa5 in QTimerInfoList::timerWait(timespec&) () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#6  0x7f69c266ee8e in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#7  0x7f69b9a058ad in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f69b9a0624b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f69b9a0642c in g_main_context_iteration () 

[kdevelop] [Bug 363707] New: Assert when parsing project

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Bug ID: 363707
   Summary: Assert when parsing project
   Product: kdevelop
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: cordlandw...@kde.org

The following assert happens every time when my current project is parsed:

Application: KDevelop (kdevelop), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7f6b481438c0 (LWP 16253))]

Thread 9 (Thread 0x7f6b28e92700 (LWP 16254)):
#0  0x7f6b445fde8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6b36f51c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f6b36f538d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f6b29e2e2c9 in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/plugins/platforms/../../lib/libQt5XcbQpa.so.5
#4  0x7f6b44cf262f in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#5  0x7f6b3d7ce6fa in start_thread (arg=0x7f6b28e92700) at
pthread_create.c:333
#6  0x7f6b44609b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7f6b15200700 (LWP 16256)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7f6b44cf3598 in QWaitCondition::wait(QMutex*, unsigned long) () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#2  0x7f6b423c2958 in KDevelop::DUChainPrivate::CleanupThread::run
(this=0x16c9f00) at
/opt/nightly/src/extragear/kdevelop/kdevplatform/language/duchain/duchain.cpp:282
#3  0x7f6b44cf262f in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#4  0x7f6b3d7ce6fa in start_thread (arg=0x7f6b15200700) at
pthread_create.c:333
#5  0x7f6b44609b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f6b0f076700 (LWP 16257)):
#0  0x7f6b445fde8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6b3c2cc31c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6b3c2cc42c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6b44f35a87 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#4  0x7f6b44ede212 in
QEventLoop::exec(QFlags) () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#5  0x7f6b44ced7bc in QThread::exec() () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#6  0x7f6b44cf262f in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#7  0x7f6b3d7ce6fa in start_thread (arg=0x7f6b0f076700) at
pthread_create.c:333
#8  0x7f6b44609b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f6b069a4700 (LWP 16260)):
#0  0x7f6b445fde8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6b3c2cc31c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6b3c2cc42c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6b44f35a9c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#4  0x7f6b44ede212 in
QEventLoop::exec(QFlags) () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#5  0x7f6b44ced7bc in QThread::exec() () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#6  0x7f6b4252727c in KDevelop::CompletionWorkerThread::run (this=0x872150)
at
/opt/nightly/src/extragear/kdevelop/kdevplatform/language/codecompletion/codecompletionmodel.cpp:89
#7  0x7f6b44cf262f in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#8  0x7f6b3d7ce6fa in start_thread (arg=0x7f6b069a4700) at
pthread_create.c:333
#9  0x7f6b44609b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f6b04c37700 (LWP 16261)):
#0  0x7f6b445fde8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6b3c2cc31c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6b3c2cc42c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6b44f35a9c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#4  0x7f6b44ede212 in
QEventLoop::exec(QFlags) () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#5  0x7f6b44ced7bc in QThread::exec() () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#6  0x7f6b4252727c in KDevelop::CompletionWorkerThread::run
(this=0x1b06580) at
/opt/nightly/src/extragear/kdevelop/kdevplatform/language/codecompletion/codecompletionmodel.cpp:89
#7  0x7f6b44cf262f in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#8  0x7f6b3d7ce6fa in start_thread 

[Artikulate] [Bug 363250] It is empty on the GUI

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/arti
   ||kulate/543d2b5bab2e114631b4
   ||c095bcb0a77bc1e918cf
 Resolution|--- |FIXED

--- Comment #3 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Git commit 543d2b5bab2e114631b4c095bcb0a77bc1e918cf by Andreas Cord-Landwehr.
Committed on 26/05/2016 at 14:45.
Pushed by cordlandwehr into branch 'Applications/16.04'.

Load welcome screen when no course is available

M  +1-1src/qml/Main.qml

http://commits.kde.org/artikulate/543d2b5bab2e114631b4c095bcb0a77bc1e918cf

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

[kdevelop] [Bug 358907] Literal ampersands in toolview context-menu titles.

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kdev
   ||platform/a974f4193aa75f6ff5
   ||3b1ee3425fb950ec64dc3a

--- Comment #1 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Git commit a974f4193aa75f6ff53b1ee3425fb950ec64dc3a by Andreas Cord-Landwehr.
Committed on 18/05/2016 at 18:32.
Pushed by cordlandwehr into branch '5.0'.

Fix Display of Ampersand in Context Menu

Use unprocessed window title that does not contain any ampersand
symbols for shortcuts.

M  +1-1sublime/idealdockwidget.cpp

http://commits.kde.org/kdevplatform/a974f4193aa75f6ff53b1ee3425fb950ec64dc3a

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

[kdevelop] [Bug 354748] GHNS "Get New Documentation" broken

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/atti
   ||ca/d6118e0d79fc5b1abda3e2d1
   ||e506bb7bde160747
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
Git commit d6118e0d79fc5b1abda3e2d1e506bb7bde160747 by Andreas Cord-Landwehr.
Committed on 14/05/2016 at 13:52.
Pushed by cordlandwehr into branch 'master'.

Fix redirection of absolut Urls

Redirection only worked with relative urls. Yet, e.g. the http to https
redirection on KDE servers uses absolute paths, which resulted in an
empty url, since the reply attribute was not relative.

This patch adds a case distinction for redirecting absolute and relative
paths.
REVIEW: 127900

M  +7-2src/atticabasejob.cpp

http://commits.kde.org/attica/d6118e0d79fc5b1abda3e2d1e506bb7bde160747

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

[kdesrc-build] [Bug 362687] New: Enable kdesrc-build to handle Git Submodules

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Bug ID: 362687
   Summary: Enable kdesrc-build to handle Git Submodules
   Product: kdesrc-build
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: mp...@kde.org
  Reporter: cordlandw...@kde.org

Currently, kdesrc-build does not respect when Git repositories have submodules
and one has to checkout all of them by hand and update them by hand. I see two
possible ways how to provide this feature:
1) by default handle every repository as it had submodules: "git clone
--recursive" should not be disruptive as well as "git submodule update
--recursive" should not harm a repository with submodules IMHO
2) provide an option for the Git call of a module to specifically enable
submodule handling.

Reproducible: Always

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

[kontact] [Bug 361902] Assert when deleting mails (master branch)

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Andreas Cord-Landwehr <cordlandw...@kde.org> changed:

   What|Removed |Added

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

--- Comment #1 from Andreas Cord-Landwehr <cordlandw...@kde.org> ---
After today's rebuild of PIM and its libraries, I cannot reproduce anymore.

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