[kpat] [Bug 402220] KPat crashes when "Change Appearance" is selected

[awilfox]

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

A. Wilcox (awilfox)  changed:

   What|Removed |Added

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

--- Comment #4 from A. Wilcox (awilfox)  ---
All decks affected have embedded PNG images as the actual card data.  For
example, from the xskat-french card deck:

  

So perhaps this is a bug in Qt.  I suppose I can close this and attempt to file
a bug upstream.

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

[kpat] [Bug 402220] KPat crashes when "Change Appearance" is selected

[awilfox]

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

--- Comment #3 from A. Wilcox (awilfox)  ---
Okay, so it seems that even using KPat 17.12.0 now shows this same error.

I started looking harder and it looks like it may actually be in the card decks
themselves.  Removing:

svg-ancient-egyptians
svg-future
svg-jolly-royal
svg-konqi-modern
svg-standard
svg-xskat-french

from /usr/share/carddecks allows KPat to draw the rest of the card decks fine.

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

[kpat] [Bug 402220] KPat crashes when "Change Appearance" is selected

[awilfox]

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

A. Wilcox (awilfox)  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

--- Comment #2 from A. Wilcox (awilfox)  ---
We were still using 5.9.6 when this started, but we have since updated to 5.9.7
with no change.

Valgrind output is not helpful:

awilcox on gwyn [pts/11 Wed 19 18:43] ~: valgrind kpat
==22303== Memcheck, a memory error detector
==22303== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==22303== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==22303== Command: kpat
==22303== 
==22303== Conditional jump or move depends on uninitialised value(s)
==22303==at 0x402BFE0: strchrnul (strchrnul.c:21)
==22303==by 0x403E1CB: getenv (getenv.c:9)
==22303==by 0x84E0BEB: ??? (in /usr/lib/libGL.so.1.2.0)
==22303==by 0x96D3893: ??? (in /usr/lib/libexpat.so.1.6.8)
==22303==by 0x96D461F: ??? (in /usr/lib/libexpat.so.1.6.8)
==22303==by 0x96D66D3: ??? (in /usr/lib/libexpat.so.1.6.8)
==22303==by 0x96D6E73: ??? (in /usr/lib/libexpat.so.1.6.8)
==22303==by 0x96D8FE7: XML_ParseBuffer (in /usr/lib/libexpat.so.1.6.8)
==22303==by 0x96D975F: XML_Parse (in /usr/lib/libexpat.so.1.6.8)
==22303==by 0x84E283B: ??? (in /usr/lib/libGL.so.1.2.0)
==22303==by 0x84DF373: ??? (in /usr/lib/libGL.so.1.2.0)
==22303==by 0x84DDD37: ??? (in /usr/lib/libGL.so.1.2.0)
==22303== 
==22303== Conditional jump or move depends on uninitialised value(s)
==22303==at 0x402BFE0: strchrnul (strchrnul.c:21)
==22303==by 0x403E1CB: getenv (getenv.c:9)
==22303==by 0xE33924B: ??? (in /usr/lib/xorg/modules/dri/r600_dri.so)
==22303==by 0x96D3893: ??? (in /usr/lib/libexpat.so.1.6.8)
==22303==by 0x96D461F: ??? (in /usr/lib/libexpat.so.1.6.8)
==22303==by 0x96D66D3: ??? (in /usr/lib/libexpat.so.1.6.8)
==22303==by 0x96D6E73: ??? (in /usr/lib/libexpat.so.1.6.8)
==22303==by 0x96D8FE7: XML_ParseBuffer (in /usr/lib/libexpat.so.1.6.8)
==22303==by 0x96D975F: XML_Parse (in /usr/lib/libexpat.so.1.6.8)
==22303==by 0xE33AE9B: ??? (in /usr/lib/xorg/modules/dri/r600_dri.so)
==22303==by 0xE19D5B3: ??? (in /usr/lib/xorg/modules/dri/r600_dri.so)
==22303==by 0x84DDE2B: ??? (in /usr/lib/libGL.so.1.2.0)
==22303== 
==22303== 
==22303== Process terminating with default action of signal 11 (SIGSEGV)
==22303==  Bad permissions for mapped region at address 0x159D8048
==22303==at 0x6267FCC: convertARGB32PMToARGB64PM(QRgba64*, unsigned int
const*, int, QVector const*, QDitherInfo*) (qdrawhelper.cpp:653)
==22303== 
==22303== HEAP SUMMARY:
==22303== in use at exit: 35,374,539 bytes in 90,629 blocks
==22303==   total heap usage: 268,386 allocs, 177,757 frees, 100,049,643 bytes
allocated
==22303== 
==22303== LEAK SUMMARY:
==22303==definitely lost: 216 bytes in 7 blocks
==22303==indirectly lost: 0 bytes in 0 blocks
==22303==  possibly lost: 26,002 bytes in 432 blocks
==22303==still reachable: 35,313,113 bytes in 90,097 blocks
==22303==   of which reachable via heuristic:
==22303== newarray   : 96 bytes in 3 blocks
==22303== multipleinheritance: 72,120 bytes in 88
blocks
==22303== suppressed: 35,208 bytes in 93 blocks
==22303== Rerun with --leak-check=full to see details of leaked memory
==22303== 
==22303== For counts of detected and suppressed errors, rerun with: -v
==22303== Use --track-origins=yes to see where uninitialised values come from
==22303== ERROR SUMMARY: 26 errors from 2 contexts (suppressed: 0 from 0)
zsh: segmentation fault  valgrind kpat


I really hope this does not turn into another round of hot potato where the KDE
devs blame Qt and the Qt devs blame KDE and meanwhile nobody can change card
decks or backgrounds in KPat.

I will attempt to bisect this crash and see if I can find an exact commit that
causes it.

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

[kpat] [Bug 402220] New: KPat crashes when "Change Appearance" is selected

[awilfox]

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

Bug ID: 402220
   Summary: KPat crashes when "Change Appearance" is selected
   Product: kpat
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: co...@kde.org
  Reporter: awil...@adelielinux.org
CC: kde-games-b...@kde.org
  Target Milestone: ---

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

SUMMARY
KPat crashes when any user of Adélie Linux (based on musl libc) attempts to use
the Change Appearance dialog.


STEPS TO REPRODUCE
1. Open KPat.
2. Choose Tools -> Change Appearance, or press the F10 key.

OBSERVED RESULT
Thread 6 "PreviewThread" received signal SIGSEGV, Segmentation fault.
[Switching to LWP 31799]
0x36b367f0 in fetchTransformedBilinear64<(TextureBlendType)4>
(buffer=0x3fffeaf68418, data=0x100763428, y=0, x=0, length=74) at
painting/qdrawhelper.cpp:2967
2967painting/qdrawhelper.cpp: No such file or directory.
(gdb) bt
#0  0x36b367f0 in fetchTransformedBilinear64<(TextureBlendType)4>
(buffer=0x3fffeaf68418, data=0x100763428, y=0, x=0, length=74) at
painting/qdrawhelper.cpp:2967
#1  0x36b4186c in BlendSrcGenericRGB64::fetch (len=74, y=0, x=0,
this=0x3fffeaf64378) at painting/qdrawhelper.cpp:4054
#2  handleSpans (count=256, spans=0x3fffeaf6c710,
data=, handler=...) at painting/qdrawhelper.cpp:3967
#3  0x36b409e8 in blend_src_generic_rgb64 (count=,
spans=0x3fffeaf6c710, userData=0x100763428) at painting/qdrawhelper.cpp:4081
#4  0x36b3b0dc in qBlendTexture (count=,
spans=0x3fffeaf6c710, userData=0x100763428) at painting/qdrawhelper.cpp:5347
#5  0x36b6bcf0 in qt_span_fill_clipRect (count=,
spans=0x3fffeaf6c710, userData=0x100763428) at
painting/qpaintengine_raster.cpp:4099
#6  0x36bde020 in QSpanBuffer::flushSpans (this=0x3fffeaf6c700) at
painting/qrasterizer.cpp:111
#7  QSpanBuffer::addSpan (coverage=, y=85, len=,
x=, this=0x3fffeaf6c700) at painting/qrasterizer.cpp:105
#8  QRasterizer::rasterizeLine (this=0x10074d7c0, a=..., b=...,
width=, squareCap=) at
painting/qrasterizer.cpp:917
#9  0x36b75b2c in QRasterPaintEngine::drawImage (this=0x100763000,
r=..., img=..., sr=...) at painting/qpaintengine_raster.cpp:2423
#10 0x36b9aca8 in QPainter::drawImage (this=0x3fffeaf6d840,
targetRect=..., image=..., sourceRect=..., flags=...) at
painting/qpainter.cpp:5477
#11 0x35c10364 in QPainter::drawImage (image=..., r=...,
this=0x3fffeaf6d840) at /usr/include/QtGui/qpainter.h:848
#12 QSvgImage::draw (this=0x101092a40, p=0x3fffeaf6d840, states=...) at
qsvggraphics.cpp:137
#13 0x35c3cd94 in QSvgG::draw (this=0x1010926a0, p=0x3fffeaf6d840,
states=...) at qsvgstructure.cpp:71
#14 0x35c3cd94 in QSvgG::draw (this=0x101092440, p=0x3fffeaf6d840,
states=...) at qsvgstructure.cpp:71
#15 0x35c477c0 in QSvgTinyDocument::draw (this=0x1007ef200,
p=0x3fffeaf6d840, id=..., bounds=...) at qsvgtinydocument.cpp:304
#16 0x35c4a580 in QSvgRenderer::render (this=,
painter=, elementId=..., bounds=...) at qsvgrenderer.cpp:399
#17 0x37e60858 in PreviewThread::run (this=0x10075b520) at
/usr/src/packages/user/kpat/src/kpat-18.08.3/libkcardgame/kcardthemewidget.cpp:104
#18 0x361b3c88 in QThreadPrivate::start (arg=0x10075b520) at
thread/qthread_unix.cpp:368
#19 0x37fa276c in start (p=0x3fffeaf6da78) at
src/thread/pthread_create.c:147
#20 0x37fae608 in __clone () at src/thread/powerpc64/clone.s:43



EXPECTED RESULT
The dialog to work properly.


SOFTWARE/OS VERSIONS
Linux: 4.14.76
KDE Plasma Version: 5.12.7
KDE Frameworks Version: 5.52.0
Qt Version: 5.9.7

ADDITIONAL INFORMATION
This occurs on PowerPC and x86.  We haven't had any reports from ARM users yet.
 This seems like a regression; kpat 18.04 didn't seem have this issue.

It does draw the current card deck before it crashes; attached is a screenshot
showing where the window stops drawing when running KPat under gdb.

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

[Breeze] [Bug 352951] Breeze locks up in ~AnimationData while changing colours

[awilfox]

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

A. Wilcox (awilfox)  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

--- Comment #4 from A. Wilcox (awilfox)  ---
I no longer have the hardware needed to reproduce this (it only happens on
Intel GPU), so I can't say if it is fixed or not.

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

[konsole] [Bug 364285] Konsole crashes when saving output from closing tab

[awilfox]

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

A. Wilcox (awilfox)  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from A. Wilcox (awilfox)  ---
Can't duplicate this on 18.08.3 with Qt 5.9.6 and KF 5.52.0.  Probably fixed. 
(^+S immediately displays a modal that won't let me ^D under it; ^D won't let
^+S pop a save dialogue.)

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

[umbrello] [Bug 400501] Umbrello fails to start due to ASSERT failure in QVector::at "index out of range"

[awilfox]

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

A. Wilcox (awilfox)  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1

--- Comment #4 from A. Wilcox (awilfox)  ---
Applying that commit as a patch didn't change anything.  Does it require more
commits from master?  It was applied directly to a 18.08.2 tarball.


awilcox on gwyn [pts/11 Tue 6 15:23] user: gdb umbrello5
GNU gdb (GDB) 8.2
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "powerpc64-foxkit-linux-musl".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from umbrello5...Reading symbols from
/usr/lib/debug//usr/bin/umbrello5.debug...done.
done.
(gdb) run
Starting program: /usr/bin/umbrello5 
Qt: gdb: -nograb added to command-line options.
 Use the -dograb option to enforce grabbing.
[New LWP 36041]
[New LWP 36042]
Shortcut for action  "delete_selected" "Delete " set with
QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Shortcut for action  "move_tab_left" " Tab Left" set with
QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Shortcut for action  "move_tab_right" " Tab Right" set with
QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Shortcut for action  "previous_tab" "Select Diagram on Left" set with
QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Shortcut for action  "next_tab" "Select Diagram on Right" set with
QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
[New LWP 36043]
[New LWP 36044]
Illegal icon group:  7
umbrello: searching for "/usr/bin/../doc/apphelp/index.cache.bz2"
umbrello: searching for
"/usr/bin/../share/doc/HTML/en/umbrello/apphelp/index.cache.bz2"
umbrello: searching for
"/usr/bin/../share/doc/HTML/en_GB/umbrello/apphelp/index.cache.bz2"
umbrello: searching for
"/usr/bin/../share/doc/HTML/en/umbrello/apphelp/index.cache.bz2"
umbrello: searching for
"/home/awilcox/.local/share/doc/HTML/en/umbrello/apphelp/index.cache.bz2"
umbrello: searching for
"/home/awilcox/.local/share/doc/HTML/en_GB/umbrello/apphelp/index.cache.bz2"
umbrello: searching for
"/home/awilcox/.local/share/doc/HTML/en/umbrello/apphelp/index.cache.bz2"
umbrello: searching for
"/usr/share/doc/HTML/en/umbrello/apphelp/index.cache.bz2"
umbrello: searching for
"/usr/share/doc/HTML/en_GB/umbrello/apphelp/index.cache.bz2"
umbrello: searching for
"/usr/share/doc/HTML/en/umbrello/apphelp/index.cache.bz2"
umbrello: searching for
"/usr/local/share/doc/HTML/en/umbrello/apphelp/index.cache.bz2"
umbrello: searching for
"/usr/local/share/doc/HTML/en_GB/umbrello/apphelp/index.cache.bz2"
umbrello: searching for
"/usr/local/share/doc/HTML/en/umbrello/apphelp/index.cache.bz2"
umbrello: view is NULL
umbrello: "folder"  : umlPackage not set on object
umbrello: view is NULL
umbrello: screen dpi: 96 file dpi: 96 scale: 1
umbrello: folder= "Logical View"  / type= "Class"  / name= "class diagram"
umbrello: "class diagram"  to folder  UMLFolder: localName="Logical View",
folderFile="", diagrams=0  ( "Logical View" )
umbrello: id= "ukYrMZXkIkFZG"
umbrello: setZoom 100
umbrello: could not find  "class diagram"  in  UMLListViewItem: "Logical View",
type="lvt_Logical_View", id="Logical_View", children=1
umbrello: Changed view to UMLScene: "class diagram" / type="Class" /
id="ukYrMZXkIkFZG" / isOpen=true
umbrello: Modified file= "Untitled"
umbrello: setZoom 100
umbrello: could not find  "class diagram"  in  UMLListViewItem: "Logical View",
type="lvt_Logical_View", id="Logical_View", children=1
umbrello: Changed view to UMLScene: "class diagram" / type="Class" /
id="ukYr

[umbrello] [Bug 400501] Umbrello fails to start due to ASSERT failure in QVector::at "index out of range"

[awilfox]

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

--- Comment #2 from A. Wilcox (awilfox)  ---
No, I am not able to do that, because we don't have the (deprecated, no longer
supported) KDE 4 libraries packaged.

As for "QPainterPath::addRect: Adding rect where a parameter is NaN or Inf,
ignoring call":

That output only appears on ppc64, which is using software backend for KWin and
that is the likely cause for that message.  The crash still occurs, without
this message, on the other architectures.

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

[umbrello] [Bug 400501] New: Umbrello fails to start due to ASSERT failure in QVector::at "index out of range"

[awilfox]

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

Bug ID: 400501
   Summary: Umbrello fails to start due to ASSERT failure in
QVector::at "index out of range"
   Product: umbrello
   Version: 2.26.2 (KDE Applications 18.08.2)
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: umbrello-de...@kde.org
  Reporter: awil...@adelielinux.org
  Target Milestone: ---

Hi, I'm the package maintainer for Umbrello at the Adélie Linux distribution. 
Umbrello is not able to start up on any platform we ship on (x86, x86_64, ppc,
ppc64, arm64).

Qt: 5.9.6
KDE Frameworks: 5.51.0
Umbrello UML Modeller: 2.26.2

Output:
awilcox on gwyn [pts/11 Wed 31 1:16] ~: umbrello5
Shortcut for action  "delete_selected" "Delete " set with
QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Shortcut for action  "move_tab_left" " Tab Left" set with
QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Shortcut for action  "move_tab_right" " Tab Right" set with
QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Shortcut for action  "previous_tab" "Select Diagram on Left" set with
QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Shortcut for action  "next_tab" "Select Diagram on Right" set with
QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Illegal icon group:  7
umbrello: searching for "/usr/bin/../doc/apphelp/index.cache.bz2"
umbrello: searching for
"/usr/bin/../share/doc/HTML/en/umbrello/apphelp/index.cache.bz2"
umbrello: searching for
"/usr/bin/../share/doc/HTML/en_GB/umbrello/apphelp/index.cache.bz2"
umbrello: searching for
"/usr/bin/../share/doc/HTML/en/umbrello/apphelp/index.cache.bz2"
umbrello: searching for
"/home/awilcox/.local/share/doc/HTML/en/umbrello/apphelp/index.cache.bz2"
umbrello: searching for
"/home/awilcox/.local/share/doc/HTML/en_GB/umbrello/apphelp/index.cache.bz2"
umbrello: searching for
"/home/awilcox/.local/share/doc/HTML/en/umbrello/apphelp/index.cache.bz2"
umbrello: searching for
"/usr/share/doc/HTML/en/umbrello/apphelp/index.cache.bz2"
umbrello: searching for
"/usr/share/doc/HTML/en_GB/umbrello/apphelp/index.cache.bz2"
umbrello: searching for
"/usr/share/doc/HTML/en/umbrello/apphelp/index.cache.bz2"
umbrello: searching for
"/usr/local/share/doc/HTML/en/umbrello/apphelp/index.cache.bz2"
umbrello: searching for
"/usr/local/share/doc/HTML/en_GB/umbrello/apphelp/index.cache.bz2"
umbrello: searching for
"/usr/local/share/doc/HTML/en/umbrello/apphelp/index.cache.bz2"
umbrello: view is NULL
umbrello: "folder"  : umlPackage not set on object
umbrello: view is NULL
umbrello: screen dpi: 96 file dpi: 96 scale: 1
umbrello: folder= "Logical View"  / type= "Class"  / name= "class diagram"
umbrello: "class diagram"  to folder  UMLFolder: localName="Logical View",
folderFile="", diagrams=0  ( "Logical View" )
umbrello: id= "uXuj12TS8ZppK"
umbrello: setZoom 100
umbrello: could not find  "class diagram"  in  UMLListViewItem: "Logical View",
type="lvt_Logical_View", id="Logical_View", children=1
umbrello: Changed view to UMLScene: "class diagram" / type="Class" /
id="uXuj12TS8ZppK" / isOpen=true
umbrello: Modified file= "Untitled"
umbrello: setZoom 100
umbrello: could not find  "class diagram"  in  UMLListViewItem: "Logical View",
type="lvt_Logical_View", id="Logical_View", children=1
umbrello: Changed view to UMLScene: "class diagram" / type="Class" /
id="uXuj12TS8ZppK" / isOpen=true
umbrello: setZoom 100
umbrello: setZoom 100
umbrello: Modified file= "Untitled"
umbrello: id= "uXuj12TS8ZppK"
umbrello: setZoom 100
umbrello: Changed view to UMLScene: "class diagram" / type="Class" /
id="uXuj12TS8ZppK" / isOpen=true
umbrello: Modified file= "Untitled"
umbrello: "Create UML object : char"  [ 1 ]
umbrello: Modified file= "Untitled"
umbrello: scene= "class diagram"  / object= "char"
umbrello: "Create UML object : int"  [ 2 ]
umbrello: Modified file= "Untitled"
umbrello: scene= "class diagram"  / object= "int"
QPainterPath::addRect: Adding rect where a parameter is NaN or Inf, ignoring
call
umbrello: "Create UML object : float"  [ 3 ]
umbrello: Modified file= "Untitled"
umbrello: scene= "class diagram"  / object= "float"
QPainterPath::addRect: Adding rect where a parameter is NaN or Inf, ignoring
call
umbrello: "Create UML object : double"  [ 4 ]
umbrello: Modified file= "Untitled"
umbrello: scene= "class diagram"  / object= "double"
umbrello: "Create UML object : bool"  [ 5 ]
umbrello: Modified file= "Untitled"
umbrello: scene= "class diagram"  / object= "bool"
umbrello: "Create UML object : string"  [ 6 ]
umbrello: Modified file= "Untitled"
umbrello: scene= "class diagram"  / object= "string"
umbrello: "Create UML object : unsigned char"  [ 7 ]
umbrello: Modified file= "Untitled"
umbrello: scene= "class 

[calligrawords] [Bug 400267] New: Building Calligra Words 3.1.0 on musl: ustring.cpp:69:18: error: '_isnan' was not declared in this scope

[awilfox]

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

Bug ID: 400267
   Summary: Building Calligra Words 3.1.0 on musl:
ustring.cpp:69:18: error: '_isnan' was not declared in
this scope
   Product: calligrawords
   Version: 3.1.0
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: filters
  Assignee: calligra-words-bugs-n...@kde.org
  Reporter: awil...@adelielinux.org
  Target Milestone: ---

SUMMARY
Attemping to build Calligra Words 3.1.0 on Linux using musl libc on PowerPC.


STEPS TO REPRODUCE
1. Download calligra-3.1.0.tar.xz
2. Run CMake
3. Run make / ninja


OBSERVED RESULT
/usr/src/packages/user/calligra/src/calligra-3.1.0/filters/words/msword-odf/wv2/src/ustring.cpp:
In function ‘bool wvWare::isNaN(double)’:
/usr/src/packages/user/calligra/src/calligra-3.1.0/filters/words/msword-odf/wv2/src/ustring.cpp:69:18:
error: ‘_isnan’ was not declared in this scope
   return _isnan(d) != 0;
  ^


EXPECTED RESULT
Successful compilation


SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.12.6
KDE Frameworks Version: 5.51.0
Qt Version: 5.9.6


ADDITIONAL INFORMATION
musl does not implement isinf/isnan as linkable functions; they are
preprocessor macros.

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

[kwin] [Bug 379681] Crash after turning off compositions with Alt+Shift+F12

[awilfox]

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

--- Comment #14 from A. Wilcox (awilfox)  ---
FWIW, I haven't seen this error once while using `ffplay` on ppc64 with the
same GPU, so I think this is some arch-specific weirdness.  I no longer own an
x86_64 computer so I don't care any more anyway.

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

[frameworks-knotifications] [Bug 348414] Crash in KNotification::flags() (NotifyByAudio::onAudioFinished)

[awilfox]

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

A. Wilcox (awilfox)  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED
 Ever confirmed|1   |0

--- Comment #88 from A. Wilcox (awilfox)  ---
Comment 69, Comment 70, Comment 86 provide enough information to mark the
NEEDSINFO flag invalid, imo.  -> Reported

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

[kate] [Bug 397298] Kate crashes with segmentation fault when hovering over folded code segment

[awilfox]

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

A. Wilcox (awilfox)  changed:

   What|Removed |Added

 Resolution|DUPLICATE   |UPSTREAM

--- Comment #4 from A. Wilcox (awilfox)  ---
Still happens with Kate 18.08.1 / KF 5.50.  Reported upstream at
https://bugreports.qt.io/browse/QTBUG-70797

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

[valgrind] [Bug 398883] valgrind incorrectly assumes ABI on PowerPC based on endianness

[awilfox]

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

A. Wilcox (awilfox)  changed:

   What|Removed |Added

 Attachment #115278|application/mbox|text/plain
  mime type||
 Attachment #115278|0   |1
   is patch||

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

[valgrind] [Bug 398883] valgrind incorrectly assumes ABI on PowerPC based on endianness

[awilfox]

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

--- Comment #2 from A. Wilcox (awilfox)  ---
Created attachment 115278
  --> https://bugs.kde.org/attachment.cgi?id=115278=edit
Ensure ELFv2 is supported on PPC64

This patch has been tested on PPC64 BE, both ELFv1 (Debian) and ELFv2 (Adélie).
 I don't have any LE hardware to test on, but there should be no functional
change.

I've tested memcheck and callgrind on both ELF ABIs on a POWER9 host running
big-endian and found no issues.

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

[valgrind] [Bug 398883] valgrind incorrectly assumes ABI on PowerPC based on endianness

[awilfox]

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

--- Comment #1 from A. Wilcox (awilfox)  ---
Okay, it doesn't have to be so hard.  There is already VG_PLAT_USES_PPCTOC; so
this change just needs to actually use that define instead of just endianness
to determine what ABI to use.

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

[valgrind] [Bug 398883] New: valgrind incorrectly assumes ABI on PowerPC based on endianness

[awilfox]

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

Bug ID: 398883
   Summary: valgrind incorrectly assumes ABI on PowerPC based on
endianness
   Product: valgrind
   Version: 3.13.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: awil...@adelielinux.org
  Target Milestone: ---

valgrind (mainly coregrind, though there are a few misc bits in memcheck it
looks like) assumes ELFv1 ABI on big endian and ELFv2 ABI on little endian.

Neither of these assumptions are correct; the musl libc (used by Void, Adélie,
Alpine, Sabotage, and other Linux distros) uses ELFv2 ABI on big endian, and
older releases of OpenSuSE use ELFv1 ABI on little endian.

I plan on submitting a patch, either here or on Differential, in the coming
weeks.  My change plan is:


* add definition, VGP_ppc64_linux_abi1 and VGP_ppc64_linux_abi2

* abi1 is defined if (defined(VGP_ppc64be_linux) && (!defined(_CALL_ELF) ||
_CALL_ELF == 1) || (defined(VGP_ppc64le_linux) && defined(_CALL_ELF) &&
_CALL_ELF == 1)

* abi2 is defined if (defined(VGP_ppc64le_linux) && (!defined(_CALL_ELF) ||
_CALL_ELF == 2) || (defined(VGP_ppc64be_linux) && defined(_CALL_ELF) &&
_CALL_ELF == 2)

* then, in the C code, defined(VGP_ppc64le_linux) becomes
defined(VGP_ppc64_linux_abi2)

* and defined(VGP_ppc64be_linux) becomes defined(VGP_ppc64_linux_abi1)

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

[LabPlot2] [Bug 398342] ProjectImportTest segfaults while loading Excel file

[awilfox]

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

--- Comment #10 from A. Wilcox (awilfox)  ---
I'm terribly sorry, for some reason I didn't get any bugmail that there was a
second patch.

Yes, this patch does fix it!  The project import test passes on ppc64 now. 
Thank you so much for your effort.

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

[LabPlot2] [Bug 398342] ProjectImportTest segfaults while loading Excel file

[awilfox]

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

--- Comment #6 from A. Wilcox (awilfox)  ---
It is not possible to "mix" endians, unfortunately, so there is no way for us
to compile LabPlot in LE mode.

I applied the attached patch to our tree and rebuilt.  The exact same stack
trace was present; only the memory addresses were different, due to ASLR.

Attempting to pass -DENABLE_LIBORIGIN=OFF to CMake resulted in a build error:

In file included from
/usr/src/packages/user/labplot/src/labplot-2.5.0/src/backend/datasources/projects/OriginProjectParser.h:34:0,
 from
/usr/src/packages/user/labplot/src/labplot-2.5.0/src/kdefrontend/MainWin.cpp:40:
/usr/src/packages/user/labplot/src/labplot-2.5.0/liborigin/OriginFile.h:34:30:
fatal error: liborigin/config.h: No such file or directory
 #include "liborigin/config.h"
  ^
compilation terminated.
make[2]: *** [src/CMakeFiles/labplot2lib.dir/build.make:333:
src/CMakeFiles/labplot2lib.dir/kdefrontend/MainWin.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs
In file included from
/usr/src/packages/user/labplot/src/labplot-2.5.0/src/backend/datasources/projects/OriginProjectParser.h:34:0,
 from
/usr/src/packages/user/labplot/src/labplot-2.5.0/src/kdefrontend/datasources/ImportProjectDialog.cpp:33:
/usr/src/packages/user/labplot/src/labplot-2.5.0/liborigin/OriginFile.h:34:30:
fatal error: liborigin/config.h: No such file or directory
 #include "liborigin/config.h"
  ^
compilation terminated.
make[2]: *** [src/CMakeFiles/labplot2lib.dir/build.make:541:
src/CMakeFiles/labplot2lib.dir/kdefrontend/datasources/ImportProjectDialog.cpp.o]
Error 1

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

[LabPlot2] [Bug 398342] ProjectImportTest segfaults while loading Excel file

[awilfox]

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

--- Comment #2 from A. Wilcox (awilfox)  ---
awilcox on gwyn [pts/15 Sat 8 1:57] labplot-2.5.0:
tests/import_export/project/projectimporttest
* Start testing of ProjectImportTest *
Config: Using QtTest library 5.9.6, Qt 5.9.6 (power64-big_endian-lp64 shared
(dynamic) debug build; by GCC 6.4.0)
PASS   : ProjectImportTest::initTestCase()
QDEBUG : ProjectImportTest::testOrigin01() "Starting the import of
/usr/src/packages/user/labplot/src/labplot-2.5.0/tests/import_export/project/data/origin8_test_tree_import.opj"
OriginProjectParser::load()

= Received signal, dumping stack ==
GNU gdb (GDB) 8.2
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "powerpc64-foxkit-linux-musl".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word".
Attaching to process 25556
[New LWP 25557]
[New LWP 25558]
__cp_end () at src/thread/powerpc64/syscall_cp.s:32
(gdb) 
Thread 3 (LWP 25558):
#0  __cp_end () at src/thread/powerpc64/syscall_cp.s:32
No locals.
#1  0x3fffbd7642e4 in __syscall_cp_c (nr=128, u=2, v=70367527851920, w=0,
x=0, y=0, z=0) at src/thread/pthread_cancel.c:35
self = 
r = 
st = 0
#2  0x3fffbd7630d8 in __syscall_cp (nr=, u=,
v=, w=, x=, y=,
z=)
at src/thread/__syscall_cp.c:20
No locals.
#3  0x3fffbd7631f4 in __timedwait_cp (addr=0x3fffb7805804, val=, clk=, at=, priv=128) at
src/thread/__timedwait.c:31
r = 
to = {tv_sec = 299, tv_nsec = 99168}
top = 
#4  0x3fffbd70d028 in __pthread_cond_timedwait (c=0x3fffb99a4c28,
m=0x3fffb99a4c00, ts=0x3fffb78058d8) at src/thread/pthread_cond_timedwait.c:105
node = {prev = 0x0, next = 0x0, state = 0, barrier = 2, notify = 0x0}
e = 
seq = 2
clock = 1
cs = 0
shared = 0
oldstate = 
tmp = 
fut = 0x3fffb7805804
#5  0x3fffbb4816f8 in QWaitConditionPrivate::wait_relative (time=30,
this=0x3fffb99a4c00) at thread/qwaitcondition_unix.cpp:133
ti = {tv_sec = 5797241, tv_nsec = 374265993}
ti = 
#6  QWaitConditionPrivate::wait (time=30, this=0x3fffb99a4c00) at
thread/qwaitcondition_unix.cpp:141
code = 
code = 
#7  QWaitCondition::wait (this=, mutex=0x3fffb99a49f8,
time=30) at thread/qwaitcondition_unix.cpp:215
__PRETTY_FUNCTION__ = "bool QWaitCondition::wait(QMutex*, long unsigned
int)"
returnValue = 
#8  0x3fffbd6234d0 in QTest::WatchDog::run (this=0x3fffb99a49e0) at
qtestcase.cpp:988
t = 
locker = {val = 70367563106809}
__PRETTY_FUNCTION__ = "virtual void QTest::WatchDog::run()"
#9  0x3fffbb480c88 in QThreadPrivate::start (arg=0x3fffb99a49e0) at
thread/qthread_unix.cpp:368
__cb = {__f = 0x3fffbb47f04c , __x =
0x3fffb99a49e0, __next = 0x0}
thr = 0x3fffb99a49e0
data = 
#10 0x3fffbd76483c in start (p=0x3fffb7805a88) at
src/thread/pthread_create.c:147
self = 0x3fffb7805a88
#11 0x3fffbd7705a8 in __clone () at src/thread/powerpc64/clone.s:43
No locals.

Thread 2 (LWP 25557):
#0  __cp_end () at src/thread/powerpc64/syscall_cp.s:32
No locals.
#1  0x3fffbd764374 in __syscall_cp_c (nr=167, u=-1, v=0, w=0, x=0, y=0,
z=0) at src/thread/pthread_cancel.c:35
self = 
r = 
st = 0
#2  0x3fffbd7630d8 in __syscall_cp (nr=, u=,
v=, w=, x=, y=,
z=)
at src/thread/__syscall_cp.c:20
No locals.
#3  0x3fffbd7520b4 in poll (fds=, n=,
timeout=) at src/select/poll.c:10
No locals.
#4  0x3fffb9bec6e0 in _xcb_conn_wait (c=0x12d29bec0, cond=,
vector=0x0, count=0x0) at xcb_conn.c:479
ret = 
fd = {fd = 3, events = 1, revents = 0}
#5  0x3fffb9bef074 in xcb_wait_for_event (c=) at
xcb_in.c:697
ret = 0x0
#6  0x3fffb7bb9a98 in QXcbEventReader::run (this=0x3fffbd607a60) at
qxcbconnection.cpp:1330
event = 0x0
#7  0x3fffbb480c88 in QThreadPrivate::start (arg=0x3fffbd607a60) at
thread/qthread_unix.cpp:368
__cb = {__f = 0x3fffbb47f04c , __x =
0x3fffbd607a60, __next = 0x0}
thr = 0x3fffbd607a60
data = 
#8  0x3fffbd76483c in start (p=0x3fffb786ea88) at
src/thread/pthread_create.c:147
self = 0x3fffb786ea88
#9  0x3fffbd7705a8 in __clone () at src/thread/powerpc64/clone.s:43
No lo

[LabPlot2] [Bug 398342] New: ProjectImportTest segfaults while loading Excel file

[awilfox]

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

Bug ID: 398342
   Summary: ProjectImportTest segfaults while loading Excel file
   Product: LabPlot2
   Version: latest
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: backend
  Assignee: alexander.se...@web.de
  Reporter: awil...@adelielinux.org
  Target Milestone: ---

Building LabPlot 2.5.0 on Adélie Linux 1.0-beta1-exp with musl libc 1.1.20,
there was a segmentation fault during the automated tests:


awilcox on gwyn [pts/16 Thu 6 22:54] labplot-2.5.0:
tests/import_export/project/projectimporttest
* Start testing of ProjectImportTest *
Config: Using QtTest library 5.9.6, Qt 5.9.6 (power64-big_endian-lp64 shared
(dynamic) debug build; by GCC 6.4.0)
PASS   : ProjectImportTest::initTestCase()
QDEBUG : ProjectImportTest::testOrigin01() "Starting the import of
/usr/src/packages/user/labplot/src/labplot-2.5.0/tests/import_export/project/data/origin8_test_tree_import.opj"
OriginProjectParser::load()

= Received signal, dumping stack ==
GNU gdb (GDB) 8.2
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "powerpc64-foxkit-linux-musl".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word".
Attaching to process 57000
[New LWP 57001]
[New LWP 57002]
__cp_end () at src/thread/powerpc64/syscall_cp.s:32
(gdb) 
Thread 3 (LWP 57002):
#0  __cp_end () at src/thread/powerpc64/syscall_cp.s:32
No locals.
#1  0x3fffa2ed22e4 in __syscall_cp_c (nr=128, u=2, v=70367082657680, w=0,
x=0, y=0, z=0) at src/thread/pthread_cancel.c:35
self = 
r = 
st = 0
#2  0x3fffa2ed10d8 in __syscall_cp (nr=, u=,
v=, w=, x=, y=,
z=)
at src/thread/__syscall_cp.c:20
No locals.
#3  0x3fffa2ed11f4 in __timedwait_cp (addr=0x3fff9cf73804, val=, clk=, at=, priv=128) at
src/thread/__timedwait.c:31
r = 
to = {tv_sec = 299, tv_nsec = 99232}
top = 
#4  0x3fffa2e7b028 in __pthread_cond_timedwait (c=0x3fffa0761c28,
m=0x3fffa0761c00, ts=0x3fff9cf738d8) at src/thread/pthread_cond_timedwait.c:105
node = {prev = 0x0, next = 0x0, state = 0, barrier = 2, notify = 0x0}
e = 
seq = 2
clock = 1
cs = 0
shared = 0
oldstate = 
tmp = 
fut = 0x3fff9cf73804
#5  0x3fffa0bef6f8 in QWaitConditionPrivate::wait_relative (time=30,
this=0x3fffa0761c00) at thread/qwaitcondition_unix.cpp:133
ti = {tv_sec = 5699834, tv_nsec = 684002528}
ti = 
#6  QWaitConditionPrivate::wait (time=30, this=0x3fffa0761c00) at
thread/qwaitcondition_unix.cpp:141
code = 
code = 
#7  QWaitCondition::wait (this=, mutex=0x3fffa07614f8,
time=30) at thread/qwaitcondition_unix.cpp:215
__PRETTY_FUNCTION__ = "bool QWaitCondition::wait(QMutex*, long unsigned
int)"
returnValue = 
#8  0x3fffa2d914d0 in QTest::WatchDog::run (this=0x3fffa07614e0) at
qtestcase.cpp:988
t = 
locker = {val = 70367141303545}
__PRETTY_FUNCTION__ = "virtual void QTest::WatchDog::run()"
#9  0x3fffa0beec88 in QThreadPrivate::start (arg=0x3fffa07614e0) at
thread/qthread_unix.cpp:368
__cb = {__f = 0x3fffa0bed04c , __x =
0x3fffa07614e0, __next = 0x0}
thr = 0x3fffa07614e0
data = 
#10 0x3fffa2ed283c in start (p=0x3fff9cf73a88) at
src/thread/pthread_create.c:147
self = 0x3fff9cf73a88
#11 0x3fffa2ede5a8 in __clone () at src/thread/powerpc64/clone.s:43
No locals.

Thread 2 (LWP 57001):
#0  __cp_end () at src/thread/powerpc64/syscall_cp.s:32
No locals.
#1  0x3fffa2ed2374 in __syscall_cp_c (nr=167, u=-1, v=0, w=0, x=0, y=0,
z=0) at src/thread/pthread_cancel.c:35
self = 
r = 
st = 0
#2  0x3fffa2ed10d8 in __syscall_cp (nr=, u=,
v=, w=, x=, y=,
z=)
at src/thread/__syscall_cp.c:20
No locals.
#3  0x3fffa2ec00b4 in poll (fds=, n=,
timeout=) at src/select/poll.c:10
No locals.
#4  0x3fff9f35a6e0 in _xcb_conn_wait (c=0x122e6fec0, cond=,
vector=0x0, count=0x0) at xcb_conn.c:479
ret = 
fd = {fd = 3, events = 1, revents = 0}
#5  0x3fff9f35d074 in xcb_wait_for_event (c=) at
xcb_in.c:697
ret = 0x0
#6  0x3fff9d327a98 in QXcbEventReader::run (this=0x3fffa2d75a60) at
qxcbconnection.cpp:1330
event = 0x0
#7  

[frameworks-solid] [Bug 365923] Solid udisks2 backend fails to compile on musl libc: dev_t requires sys/types.h

[awilfox]

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

A. Wilcox (awilfox)  changed:

   What|Removed |Added

   Version Fixed In||5.37.0
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||2382c3f8d3669c473130f4baefb
   ||68d244dcb5cbc

--- Comment #2 from A. Wilcox (awilfox)  ---
Fixed in
https://cgit.kde.org/solid.git/commit/?id=2382c3f8d3669c473130f4baefb68d244dcb5cbc

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

[frameworks-kio] [Bug 365925] KIO KPAC fails to build on musl libc: _BSD_SOURCE or _GNU_SOURCE needs to be defined

[awilfox]

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

A. Wilcox (awilfox)  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
   Version Fixed In||5.37.0
 Status|NEEDSINFO   |RESOLVED
  Latest Commit||15451d505fdbc37b5d027f8ad1b
   ||a6aeb6314cc2d

--- Comment #2 from A. Wilcox (awilfox)  ---
Fixed in
https://cgit.kde.org/kio.git/commit/src/kpac?id=15451d505fdbc37b5d027f8ad1ba6aeb6314cc2d

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

[kate] [Bug 397298] New: Kate crashes with segmentation fault when hovering over folded code segment

[awilfox]

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

Bug ID: 397298
   Summary: Kate crashes with segmentation fault when hovering
over folded code segment
   Product: kate
   Version: 18.04.3
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: part
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: awil...@adelielinux.org
  Target Milestone: ---

Steps to reproduce:

1. Create a reStructuredText document with some headings.
2. Collapse the headings.
3. Continue to move mouse over the > in the left side bar where the line
numbers are, showing the folded content in a tooltip.


Environment:

Crashes every time on my POWER9 workstation.  Does not seem to crash on x86_64.
 Stack trace seems to pin the issue to Qt, but I'm not sure how to submit this
bug upstream.  I'm terribly unfamiliar with the way this all fits together.

Linux gwyn 4.14.56-mc9-easy-p8 #1 SMP Tue Aug 7 04:13:37 CDT 2018 ppc64
GNU/Linux

musl libc (powerpc64) Version 1.1.19

Kate 18.04.3 under Qt 5.9.6 LTS with Frameworks 5.48.0


Backtrace:


Thread 1 "kate" received signal SIGSEGV, Segmentation fault.
QGraphicsItem::scene (this=0x28) at graphicsview/qgraphicsitem.cpp:1585
1585graphicsview/qgraphicsitem.cpp: No such file or directory.
(gdb) bt
#0  QGraphicsItem::scene (this=0x28) at graphicsview/qgraphicsitem.cpp:1585
#1  0x36902520 in mapToGlobalTransform (w=0x100cde180) at
kernel/qwidget.cpp:12532
#2  0x3690275c in QWidget::mapFromGlobal (this=,
pos=...) at kernel/qwidget.cpp:12582
#3  0x368bac8c in QApplicationPrivate::dispatchEnterLeave
(enter=0x100cde180, leave=, globalPosF=...) at
kernel/qapplication.cpp:2351
#4  0x368bb880 in QApplicationPrivate::sendMouseEvent
(receiver=0x100cde180, event=0x3fffe200, alienWidget=0x0,
nativeWidget=0x100cde180, buttonDown=0x36f0c460 ,
lastMouseReceiver=..., spontaneous=)
at kernel/qapplication.cpp:2684
#5  0x36943cb8 in QWidgetWindow::handleMouseEvent (this=0x100d036a0,
event=0x3fffe738) at kernel/qwidgetwindow.cpp:629
#6  0x36946f68 in QWidgetWindow::event (this=0x100d036a0,
event=0x3fffe738) at kernel/qwidgetwindow.cpp:250
#7  0x368b12f4 in QApplicationPrivate::notify_helper (this=, receiver=0x100d036a0, e=0x3fffe738) at kernel/qapplication.cpp:3722
#8  0x368bcba0 in QApplication::notify (this=0x3fffef20,
receiver=0x100d036a0, e=0x3fffe738) at kernel/qapplication.cpp:3094
#9  0x35c07010 in QCoreApplication::notifyInternal2
(receiver=0x100d036a0, event=0x3fffe738) at
kernel/qcoreapplication.cpp:1024
#10 0x36233b58 in QCoreApplication::sendSpontaneousEvent
(event=0x3fffe728, receiver=0x100d036a0) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#11 QGuiApplicationPrivate::processMouseEvent (e=0x100abcc80) at
kernel/qguiapplication.cpp:1952
#12 0x36235f60 in QGuiApplicationPrivate::processWindowSystemEvent
(e=) at kernel/qguiapplication.cpp:1733
#13 0x361f6d64 in QWindowSystemInterface::sendWindowSystemEvents
(flags=...) at kernel/qwindowsysteminterface.cpp:946
#14 0x31924314 in userEventSourceDispatch (source=) at
qeventdispatcher_glib.cpp:77
#15 0x33c5c2a0 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#16 0x33c5c5e8 in ?? () from /usr/lib/libglib-2.0.so.0
#17 0x33c5c71c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#18 0x35c8a5b4 in QEventDispatcherGlib::processEvents
(this=0x33c72260 , flags=...) at
kernel/qeventdispatcher_glib.cpp:423
#19 0x319245f0 in QPAEventDispatcherGlib::processEvents
(this=, flags=...) at qeventdispatcher_glib.cpp:122
#20 0x35c03a14 in QEventLoop::processEvents (this=,
flags=...) at kernel/qeventloop.cpp:134
#21 0x35c041f0 in QEventLoop::exec (this=0x3fffeca8, flags=...) at
kernel/qeventloop.cpp:212
#22 0x35c11fa8 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1297
#23 0x36228118 in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1679
#24 0x368b1100 in QApplication::exec () at kernel/qapplication.cpp:2910
#25 0x0001000314e8 in main (argc=, argv=) at
/usr/src/packages/user/kate/src/kate-18.04.3/kate/main.cpp:595


Further display information:

Version
===
KWin version: 5.12.6
Qt Version: 5.9.6
Qt compile version: 5.9.6
XCB compile version: 1.13

Operation Mode: X11 only

X11
===
Vendor: The X.Org Foundation
Vendor Release: 1200
Protocol Version/Revision: 11/0
SHAPE: yes; Version: 0x11
RANDR: yes; Version: 0x14
DAMAGE: yes; Version: 0x11
Composite: yes; Version: 0x4
RENDER: yes; Version: 0xb
XFIXES: yes; Version: 0x50
SYNC: yes; Version: 0x31
GLX: yes; Version: 0x0

Screens
===
Multi-Head: no
Active screen follows mouse:  yes
Number of Screens: 1

Screen 0:
-
Name: DVI-0

[frameworks-ki18n] [Bug 365917] ki18n fails to link on musl libc due to _nl_msg_cat_cntr

[awilfox]

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

A. Wilcox (awilfox)  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #5 from A. Wilcox (awilfox)  ---
I didn't have a Phabricator account at the time I reported this bug, and I lost
track of this bug when I brought the other patches over to Phabricator.  Sorry!

Yes, GNU libintl on Alpine will override musl.  We're shipping gettext-tiny in
Adélie now, which has a tiny libintl.a containing only this symbol and a few
others that are needed.  However, since "libintl is part of libc", ki18n still
won't link to it, and still fails with this error.

Thank you for the style notes, Michael; I'll be sure to keep them in mind for
any future patches I write.

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

[analitza] [Bug 393487] range(0, 1, 0.2) fails test on x86 (misses 1)

[awilfox]

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

A. Wilcox (awilfox)  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from A. Wilcox (awilfox)  ---
That patch fixes the test suite on 32-bit x86.

Any 32-bit x86 Docker image of Alpine or Adélie should allow you to easily
repro this.

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

[plasmashell] [Bug 391863] plasmashell gets in endless loop while screen is locked

[awilfox]

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

--- Comment #7 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
Wow, so one of our other developers found hidden deep in a Gerrit thread that
you lot actually *did* try to merge this fix in to 5.9 and Qt didn't let you.

Well, that doesn't change any of what I said, but it does mean I mostly aimed
it at the wrong project.  That does explain why they make the comments so
ridiculously hard to read in Qt's review system.

I still feel that telling people to use Qt 5.11 to fix a bug instead of telling
them to apply the patch to 5.9 /is/ unacceptable, but at least you tried to
apply the patch directly to 5.9 upstream.

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

[plasmashell] [Bug 391863] plasmashell gets in endless loop while screen is locked

[awilfox]

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

--- Comment #6 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
I am beginning to genuinely regret choosing KDE as our primary desktop
environment.

It feels like nobody in this entire project - or the Qt project for that matter
- has any understanding of what "LTS" means.  It means "long-term support" and
it means you have to actually fix crashing/locking bugs like this *in the long
term release*.

I can take the patch from bug 383828 and backport it to Qt 5.9, but if I do
that and it still happens, nobody will listen to me because it's not "Qt 5.11",
it's "Qt 5.9 with the necessary patch".  Time and time again this is all I get
from the KDE team AND the Qt team.

Stop using the name "LTS" if you aren't actually going to support releases for
the long term.  Qt 5.11 is not stable under some applications, it has many
other bugs, it has no long guarantee of support which is what we *need*, and
*it is not even released yet*.  Requiring an UNRELEASED VERSION of a library
for your Long Term Support release is completely UNACCEPTABLE.

Yes, I realise Qt is completely useless, and they have been for years, and I've
been dealing with bugs in Qt Declarative so long I've wondered why KDE ever
migrated to QML (as I'm sure you lot have at some points as well), and they
probably wouldn't even backport this to 5.9, but you could have at least
*ASKED* them to.

"The KDE® Community is a free software community dedicated to creating an open
and user-friendly computing experience" -> directly from KDE.org.  Telling
people that their bugs are fixed if they go install a beta library that will
crash in other horrible ways is not a user-friendly computing experience.  The
project goals of Adélie Linux, just like the project goals of KDE, is to bring
truly libre computing to the masses.  Our beta testers have praised our efforts
at fighting to have good, stable releases across the board, and have said it
has made us one of the most stable distros left.  My vision is to have
computing accessible to all, regardless of experience or ability.  Using beta
crap is not fulfiling that vision nor is it fulfiling the goals of the KDE
Community.

Now, I'm going to backport that patch to 5.9 this week, and then I'm going to
push a Qt update, and then we'll see if it happens again.  Hopefully it
doesn't, but if it does, then this bug is being reopened, and no, "upgrade to a
beta" is NOT an acceptable resolution.

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

[analitza] [Bug 393487] New: range(0, 1, 0.2) fails test on x86 (misses 1)

[awilfox]

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

Bug ID: 393487
   Summary: range(0, 1, 0.2) fails test on x86 (misses 1)
   Product: analitza
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: core
  Assignee: aleix...@kde.org
  Reporter: awil...@adelielinux.org
  Target Milestone: ---

I'm the KDE maintainer for the Adélie Linux distro, a newer distribution (based
on Alpine) that uses the musl libc.  While building analitza 17.12.2 for the
32-bit x86 architecture:


* Start testing of CommandsTest *
Config: Using QtTest library 5.9.3, Qt 5.9.3 (i386-little_endian-ilp32 shared
(dynamic) release build; by GCC 6.4.0)
PASS   : CommandsTest::initTestCase()
PASS   : CommandsTest::testCorrect(simple range)
PASS   : CommandsTest::testCorrect(range(a,b))
FAIL!  : CommandsTest::testCorrect(range(a,b)) Compared values are not the same
   Actual   (last.toString()): "list { 0, 0.2, 0.4, 0.6, 0.8 }"
   Expected (result) : "list { 0, 0.2, 0.4, 0.6, 0.8, 1 }"
   Loc:
[/usr/src/packages/user/analitza/src/analitza-17.12.2/analitza/tests/commandstest.cpp(422)]


This is the only test that fails.  Trying a simple C program:

#include 

int main(void)
{
for(double x = 0.0; x <= 1.0; x += 0.2)
printf("%.02f\n", x);
return 0;
}


does produce the intended result:

0.00
0.20
0.40
0.60
0.80
1.00


so it doesn't seem like the architecture itself is the problem.  I will note
that Analitza passes its test suite successfully on x86_64, 32-bit PowerPC, and
64-bit PowerPC.  I'm not sure how else to help debug this failure.

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

[kwin] [Bug 379681] Crash after turning off compositions with Alt+Shift+F12

[awilfox]

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

--- Comment #12 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
Completely unrelated.  I'm using libepoxy 1.4.3.  In fact, here's an exact
version of every relevant package on this system (and yes, this is still
happening every time I run ffplay):

* Qt 5.9.3, vanilla, unpatched
* Plasma Workspace/Desktop 5.12.2 LTS, vanilla, unpatched
* Mesa 17.3.1, with a patch to make the build system use Python 3, and another
patch to fix a stack overflow in disk_cache
* libepoxy 1.4.3, vanilla, unpatched
* X.Org Server 1.19.6, with a single unrelated patch related to musl on ARM
(this is an x86_64 system)
* xf86-video-amdgpu 1.4.0, vanilla, unpatched
* Linux kernel 4.14.19, mc patchset, otherwise unpatched

They're distro packages, but I'm the distro maintainer, and I run the build
servers, so I'm confident enough this is close enough to "compiled sources".

In fairness, the /segmentation fault/ isn't really KDE's fault; Qt Declarative
sucks bad.  It does a lot of unsafe things in its atexit handlers that it
REALLY should not do.  However, the only reason exit() is called is because of
an interaction between Plasma's BlurEffect dtor and libepoxy.  Which one is the
culprit, I don't know, but I do know that the issue/patch
(a8c3faaa1990d98047e3c566409200604105fa9c) is not relevant to this issue, for
many reasons:

* this is open source amdgpu
* amd, not nvidia
* 1.4.3, not 1.5.0
* epoxyinfo don't crash here

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

[kwin] [Bug 379681] Crash after turning off compositions with Alt+Shift+F12

[awilfox]

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

A. Wilcox (awilfox) <awil...@adelielinux.org> changed:

   What|Removed |Added

Version|git master  |5.12.2
   Platform|Neon Packages   |Compiled Sources

--- Comment #10 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
For what it's worth, I'm still seeing this every time I run `ffplay`, and I'm
now running Plasma 5.12.2 LTS release tarballs with no patches applied.

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

[plasmashell] [Bug 391863] plasmashell gets in endless loop while screen is locked

[awilfox]

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

--- Comment #4 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
Created attachment 111552
  --> https://bugs.kde.org/attachment.cgi?id=111552=edit
KWin supportInformation from my workstation

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

[plasmashell] [Bug 391863] plasmashell gets in endless loop while screen is locked

[awilfox]

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

A. Wilcox (awilfox) <awil...@adelielinux.org> changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #3 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
I've just had this happen on my own workstation, while I was using it.  There's
pretty much no shared configuration between the two machines.

The first machine:
- Intel Haswell GPU
- Konsole
- KMahjongg
- Firefox
- Breeze decos
- Had kscreenlocker running when it got stuck.
- Only task manager and digital clock widgets.

My workstation:
- Radeon R9 270
- Pidgin
- Konsole
- Firefox
- Kate
- Aurora (plastik) decos
- Was in active use when it got stuck.
- Icon-only Task Manager, Thermal Monitor, Resources Monitor, Digital Clock
widgets; CPU showed an even 50% load (which means 4 cores at 100%, since this
is an 8 core Xeon) at time of lock.

Packages on my system include:
musl libc (x86_64) Version 1.1.19
qt5-qtbase-5.9.3-r1
plasma-desktop-5.12.2-r0
mesa-17.3.1-r1
libdrm-2.4.89-r2

Linux ciall 4.14.19-mc4-easy #1 SMP Sat Mar 10 08:42:58 UTC 2018 x86_64
GNU/Linux


I have a core file from this lock as well.  I left it for 30 minutes at 100%
CPU usage before I took the core file then killed the process and restarted
Plasma Shell.  The backtrace was in QML this time:

(gdb) bt
#0  0x7f63234d5c0b in QMetaObject::indexOfProperty(char const*) const ()
from /usr/lib/libQt5Core.so.5
#1  0x7f632649cf65 in ?? () from /usr/lib/libQt5Qml.so.5
#2  0x7f63264a427c in ?? () from /usr/lib/libQt5Qml.so.5
#3  0x7f63263f439a in
QV4::QObjectWrapper::findProperty(QV4::ExecutionEngine*, QQmlContextData*,
QV4::String*, QV4::QObjectWrapper::RevisionMode, QQmlPropertyData*) const ()
from /usr/lib/libQt5Qml.so.5
#4  0x7f63263f95e6 in QV4::QObjectWrapper::getQmlProperty(QQmlContextData*,
QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*, bool) const () from
/usr/lib/libQt5Qml.so.5
#5  0x7f63263f9b81 in QV4::QObjectWrapper::get(QV4::Managed const*,
QV4::String*, bool*) () from /usr/lib/libQt5Qml.so.5
#6  0x7f6326423731 in ?? () from /usr/lib/libQt5Qml.so.5
#7  0x7f6326423798 in
QV4::Runtime::method_getElement(QV4::ExecutionEngine*, QV4::Value const&,
QV4::Value const&) () from /usr/lib/libQt5Qml.so.5
#8  0x7f627acfa9cd in ?? ()
#9  0x7f626d6f37e0 in ?? ()
#10 0x7f630f6a1508 in ?? ()
#11 0x7f626cab2a60 in ?? ()
#12 0x7f630f6a1498 in ?? ()
#13 0x7f626deb8500 in ?? ()
#14 0x7f626deb8500 in ?? ()
#15 0x in ?? ()
(gdb) c
Continuing.
^C
Thread 1 "plasmashell" received signal SIGINT, Interrupt.
0x7f6326212780 in memcpy@plt () from /usr/lib/libQt5Qml.so.5
(gdb) bt
#0  0x7f6326212780 in memcpy@plt () from /usr/lib/libQt5Qml.so.5
#1  0x7f632633addf in
QV4::PersistentValueStorage::mark(QV4::ExecutionEngine*) () from
/usr/lib/libQt5Qml.so.5
#2  0x7f632622d28c in QV4::MemoryManager::mark() () from
/usr/lib/libQt5Qml.so.5
#3  0x7f632622dc64 in QV4::MemoryManager::runGC() () from
/usr/lib/libQt5Qml.so.5
#4  0x7f632622f8a8 in QV4::MemoryManager::allocString(unsigned long) ()
from /usr/lib/libQt5Qml.so.5
#5  0x7f632631e7a1 in QV4::ExecutionEngine::newString(QString const&) ()
from /usr/lib/libQt5Qml.so.5
#6  0x7f632632234b in QV4::ExecutionEngine::fromVariant(QVariant const&) ()
from /usr/lib/libQt5Qml.so.5
#7  0x7f63263226e0 in QV4::ExecutionEngine::fromVariant(QVariant const&) ()
from /usr/lib/libQt5Qml.so.5
#8  0x7f63263f8a00 in
QV4::QObjectWrapper::getProperty(QV4::ExecutionEngine*, QObject*,
QQmlPropertyData*, bool) () from /usr/lib/libQt5Qml.so.5
#9  0x7f63263f967d in QV4::QObjectWrapper::getQmlProperty(QQmlContextData*,
QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*, bool) const () from
/usr/lib/libQt5Qml.so.5
#10 0x7f63263f9b81 in QV4::QObjectWrapper::get(QV4::Managed const*,
QV4::String*, bool*) () from /usr/lib/libQt5Qml.so.5
#11 0x7f6326423731 in ?? () from /usr/lib/libQt5Qml.so.5
#12 0x7f6326423798 in
QV4::Runtime::method_getElement(QV4::ExecutionEngine*, QV4::Value const&,
QV4::Value const&) () from /usr/lib/libQt5Qml.so.5
#13 0x7f627acfa9cd in ?? ()
#14 0x7f626d5f2180 in ?? ()
#15 0x7f630f6a1508 in ?? ()
#16 0x7f626c406320 in ?? ()
#17 0x7f630f6a1498 in ?? ()
#18 0x7f626cc91860 in ?? ()
#19 0x7f626cc91860 in ?? ()
#20 0x in ?? ()


Unfortunately, since Qt 5 Declarative libraries are stripped even when Qt is
configured with -no-strip, I can't get a reliable trace beyond that.  (Perhaps
there's a trick there that I'm unaware of; the libQt5Qml.so.5.9.3.debug file is
just 2,528 bytes.)

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

[plasmashell] [Bug 391863] plasmashell gets in endless loop while screen is locked

[awilfox]

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

--- Comment #2 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
I said Plasma 5.12.2; that includes all the KDE Plasma packages.

KF 5.43.0.  Qt 5.9.3.  Kernel 4.14.19.  Mesa 17.3.1.

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

[Skanlite] [Bug 369433] FTBFS invalid prepsocessing directive on comments in header.

[awilfox]

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

--- Comment #4 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
It's the same contents as version.h.cmake and it is an in-tree build.

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

[plasmashell] [Bug 391863] New: plasmashell gets in endless loop while screen is locked

[awilfox]

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

Bug ID: 391863
   Summary: plasmashell gets in endless loop while screen is
locked
   Product: plasmashell
   Version: 5.12.2
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: awil...@adelielinux.org
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Just saw this on a workstation running Adélie, a Linux distribution built on
musl libc.  The frames do return (frame 3; finish shows a return code of -18),
so this isn't a hang, but it seems to be stuck in a loop because every time I
break in, it's the same exact stack trace.  Computer was locked with
kscreenlocker at 12 noon for a meeting; just after 14:00 it was unlocked and
like this.  The clock widget shows 13:04.  No background applications were
running beyond Firefox and Konsole, and it's a stock configuration of Plasma
5.12.2 on a Haswell IGP.


I've taken a core dump but I'd rather not send it unless it would be useful to
debugging; it's very large (5.2 GB).


Note also the CPU and RAM usage of Plasma Shell and D-Bus:

10150 twilcox7   0 5551.9m 2.857g 118.0 18.3   1524:13 R plasmashell
 1751 twilcox1   0 4897.7m 2.987g  23.3 19.1   1038:25 S dbus-daemon


(gdb) bt full
#0  0x7f7e35134954 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
No symbol table info available.
#1  0x7f7e3a38aa88 in KActivities::ActivitiesCache::currentActivityChanged
(this=, _t1=...) at
/usr/src/packages/user/kactivities/src/kactivities-5.43.0/build/src/lib/KF5Activities_autogen/EWIEGA46WW/moc_activitiescache_p.cpp:400
_a = {0x0, 0x55889a9f2c80}
#2  0x7f7e351350cb in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
No symbol table info available.
#3  0x7f7e3a38783d in
OrgKdeActivityManagerActivitiesInterface::CurrentActivityChanged (_t1=...,
this=0x55881de20540) at
/usr/src/packages/user/kactivities/src/kactivities-5.43.0/build/src/lib/activities_interface.moc:407
_a = {0x7ffda37f7dd0, 0x55881de20540}
#4  OrgKdeActivityManagerActivitiesInterface::qt_static_metacall
(_o=_o@entry=0x55881de20540, _c=_c@entry=QMetaObject::InvokeMetaMethod,
_id=_id@entry=9, _a=_a@entry=0x7ffda37f7dd0)
at
/usr/src/packages/user/kactivities/src/kactivities-5.43.0/build/src/lib/activities_interface.moc:192
_t = 0x55881de20540
#5  0x7f7e3a3886e9 in OrgKdeActivityManagerActivitiesInterface::qt_metacall
(this=0x55881de20540, _c=QMetaObject::InvokeMetaMethod, _id=9,
_a=0x7ffda37f7dd0) at
/usr/src/packages/user/kactivities/src/kactivities-5.43.0/build/src/lib/activities_interface.moc:330
No locals.
#6  0x7f7e355900f2 in ?? () from /usr/lib/libQt5DBus.so.5
No symbol table info available.
#7  0x7f7e35135991 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
No symbol table info available.
#8  0x7f7e360d816c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
No symbol table info available.
#9  0x7f7e360dfa69 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
No symbol table info available.
#10 0x7f7e35108980 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
No symbol table info available.
#11 0x7f7e3510b75d in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
No symbol table info available.
#12 0x7f7e3515f583 in ?? () from /usr/lib/libQt5Core.so.5
No symbol table info available.
#13 0x7f7e2fe1e77a in g_main_dispatch (context=0x7f7e3944c0c0) at
gmain.c:3148
dispatch = 0x7f7e3515f570
prev_source = 0x0
was_in_call = 0
user_data = 0x0
callback = 0x0
cb_funcs = 
cb_data = 
need_destroy = 
source = 0x7f7e32d32240
current = 0x7f7e2c4abe00
i = 0
#14 g_main_context_dispatch (context=context@entry=0x7f7e3944c0c0) at
gmain.c:3813
No locals.
#15 0x7f7e2fe1ea08 in g_main_context_iterate
(context=context@entry=0x7f7e3944c0c0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3886
max_priority = 0
timeout = 0
some_ready = 1
nfds = 8
allocated_nfds = 
fds = 
#16 0x7f7e2fe1eabf in g_main_context_iteration (context=0x7f7e3944c0c0,
may_block=1) at gmain.c:3947
retval = 
#17 0x7f7e3515eb4f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
No symbol table info available.
#18 0x7f7e351068ea in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
No symbol table info available.
#19 0x7f7e3510f934 in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
No symbol table info available.
#20 

[Skanlite] [Bug 369433] FTBFS invalid prepsocessing directive on comments in header.

[awilfox]

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

A. Wilcox (awilfox) <awil...@adelielinux.org> changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Resolution|FIXED   |---
 CC||awil...@adelielinux.org
 Status|RESOLVED|REOPENED

--- Comment #2 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
We're hitting this on all architectures (x86_64, x86, ppc64, ppc) trying to
build Skanlite 2.0.1 from source on Adélie.

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

[kalarmcal] [Bug 391400] kalarmcal-17.12.2 can't build with KF5 KHolidays

[awilfox]

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

A. Wilcox (awilfox) <awil...@adelielinux.org> changed:

   What|Removed |Added

 Resolution|WORKSFORME  |DOWNSTREAM

--- Comment #4 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
I see the problem; the package manager was seeing stale 17.08.2 in repo and it
figured that was higher number than 5.43.0.  Sorry for the noise.

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

[kalarmcal] [Bug 391400] New: kalarmcal-17.12.2 can't build with KF5 KHolidays

[awilfox]

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

Bug ID: 391400
   Summary: kalarmcal-17.12.2 can't build with KF5 KHolidays
   Product: kalarmcal
   Version: 5.7.3
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: awil...@adelielinux.org
  Target Milestone: ---

Created attachment 90
  --> https://bugs.kde.org/attachment.cgi?id=90=edit
(Temporary patch)

I'm the Adélie Linux KDE maintainer, and we can't make a package of kalarmcal
as shipped since the transition to KHolidays being a Framework package:

CMake Error at CMakeLists.txt:44 (find_package):
  Could not find a configuration file for package "KF5Holidays" that is
  compatible with requested version "5.7.2".

  The following configuration files were considered but not accepted:

/usr/lib/cmake/KF5Holidays/KF5HolidaysConfig.cmake, version: 5.6.2


I've temporarily patched it to accept 5.6.2, since that is the latest ABI
version for KHolidays now (even in git master).

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

[frameworks-kio] [Bug 391367] New: KIO 5.43: FTBFS with musl libc on 64-bit platforms

[awilfox]

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

Bug ID: 391367
   Summary: KIO 5.43: FTBFS with musl libc on 64-bit platforms
   Product: frameworks-kio
   Version: 5.43.0
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: fa...@kde.org
  Reporter: awil...@adelielinux.org
CC: kdelibs-b...@kde.org
  Target Milestone: ---

musl is strictly POSIX conformant, which means it uses int for msg_iovlen and
socklen_t for msg_controllen in the msghdr struct.  (See
http://git.musl-libc.org/cgit/musl/commit/arch/x86_64/bits/socket.h?id=7168790763cdeb794df52be6e3b39fbb021c5a64
for more information.)

POSIX defines msghdr as containing "at least" the standard members.  (See
http://pubs.opengroup.org/onlinepubs/009696699/basedefs/sys/socket.h.html for
citation.)

Since the new shared fd code in KIO (non-conformantly) assumes the members and
layout of msghdr in its ctor, it FTBFS on 64-bit musl platforms (including
x86_64, ppc64, aarch64):

In file included from
/usr/src/packages/user/kio/src/kio-5.43.0/src/ioslaves/file/fdreceiver.cpp:23:0:
/usr/src/packages/user/kio/src/kio-5.43.0/src/ioslaves/file/sharefd_p.h: In
constructor 'FDMessageHeader::FDMessageHeader()':
/usr/src/packages/user/kio/src/kio-5.43.0/src/ioslaves/file/sharefd_p.h:78:37:
error: invalid conversion from 'char (*)[24]' to 'int' [-fpermissive]
 , msg{nullptr, 0,  , 1,  _buf, sizeof cmsg_buf, 0}
 ^
/usr/src/packages/user/kio/src/kio-5.43.0/src/ioslaves/file/sharefd_p.h:78:55:
error: invalid conversion from 'long unsigned int' to 'void*' [-fpermissive]
 , msg{nullptr, 0,  , 1,  _buf, sizeof cmsg_buf, 0}
   ^~~~
/usr/src/packages/user/kio/src/kio-5.43.0/src/ioslaves/file/sharefd_p.h:78:66:
warning: missing initializer for member 'msghdr::__pad2'
[-Wmissing-field-initializers]
 , msg{nullptr, 0,  , 1,  _buf, sizeof cmsg_buf, 0}
  ^
/usr/src/packages/user/kio/src/kio-5.43.0/src/ioslaves/file/sharefd_p.h:78:66:
warning: missing initializer for member 'msghdr::msg_flags'
[-Wmissing-field-initializers]

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

[konsole] [Bug 391318] New: Konsole crash when saving very large output log

[awilfox]

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

Bug ID: 391318
   Summary: Konsole crash when saving very large output log
   Product: konsole
   Version: 17.08.2
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: awil...@adelielinux.org
  Target Milestone: ---

Application: konsole (17.08.2)
 (Compiled from sources)
Qt Version: 5.9.1
Frameworks Version: 5.41.0
Operating System: Linux 4.14.8-mc2-easy x86_64

-- Information about the crash:
This is on Adelie Linux, a Linux distribution based on the musl libc.

- What I was doing when the application crashed:
I was attempting to save an output log (around 1.3 GB) of a very large build
job, and Konsole crashed.

-- Backtrace:
Application: Konsole (konsole), signal: Aborted
[KCrash Handler]
#8  0x7f70611c3127 in __syscall4 (a4=, a3=,
a2=, a1=, n=) at
./arch/x86_64/syscall_arch.h:38
#9  __restore_sigs (set=set@entry=0x7ffce9b669f0) at src/signal/block.c:43
#10 0x7f70611c327a in raise (sig=sig@entry=6) at src/signal/raise.c:13
#11 0x7f706118ff1e in abort () at src/exit/abort.c:9
#12 0x7f705cf7a028 in __gnu_cxx::__verbose_terminate_handler() () from
/usr/lib/libstdc++.so.6
#13 0x7f705cf76e7a in __cxxabiv1::__terminate(void (*)()) () from
/usr/lib/libstdc++.so.6
#14 0x7f705cf76ec4 in std::terminate() () from /usr/lib/libstdc++.so.6
#15 0x7f705cf773f8 in __cxa_throw () from /usr/lib/libstdc++.so.6
#16 0x7f705d344e62 in qBadAlloc() () from /usr/lib/libQt5Core.so.5
#17 0x7f705d3e0345 in QString::reallocData(unsigned int, bool) () from
/usr/lib/libQt5Core.so.5
#18 0x7f7060ca78c8 in QString::reserve (asize=1177486864,
this=0x7ffce9b66be8) at /usr/include/QtCore/qstring.h:1089
#19 Konsole::PlainTextDecoder::decodeLine (this=0x56297a0c91c0,
characters=0x7f7060f244a0 ,
count=1177486864) at
/usr/src/packages/user/konsole/src/konsole-17.08.2/src/TerminalCharacterDecoder.cpp:83
#20 0x7f7060c8347c in Konsole::Screen::copyLineToStream
(this=this@entry=0x56297bcbdcc0, line=line@entry=549888, start=,
count=1177486864, count@entry=-1, decoder=decoder@entry=0x56297a0c91c0,
appendNewLine=appendNewLine@entry=true, preserveLineBreaks=true,
trimTrailingSpaces=false) at
/usr/src/packages/user/konsole/src/konsole-17.08.2/src/Screen.cpp:1280
#21 0x7f7060c8373a in Konsole::Screen::writeToStream (this=0x56297bcbdcc0,
decoder=0x56297a0c91c0, startIndex=, endIndex=,
preserveLineBreaks=true, trimTrailingSpaces=false) at
/usr/src/packages/user/konsole/src/konsole-17.08.2/src/Screen.cpp:1164
#22 0x7f7060c9cfcd in Konsole::SaveHistoryTask::jobDataRequested
(this=, job=, data=...) at
/usr/src/packages/user/konsole/src/konsole-17.08.2/src/SessionController.cpp:1795
#23 0x7f705d57170b in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#24 0x7f705be76154 in KIO::TransferJob::dataReq(KIO::Job*, QByteArray&) ()
from /usr/lib/libKF5KIOCore.so.5
#25 0x7f705be76dc7 in KIO::TransferJob::slotDataReq() () from
/usr/lib/libKF5KIOCore.so.5
#26 0x7f705be779e1 in ?? () from /usr/lib/libKF5KIOCore.so.5
#27 0x7f705d5713c7 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#28 0x7f705be47e2e in KIO::SlaveInterface::dispatch(int, QByteArray const&)
() from /usr/lib/libKF5KIOCore.so.5
#29 0x7f705be463a8 in KIO::SlaveInterface::dispatch() () from
/usr/lib/libKF5KIOCore.so.5
#30 0x7f705be4b269 in KIO::Slave::gotInput() () from
/usr/lib/libKF5KIOCore.so.5
#31 0x7f705bed93a5 in ?? () from /usr/lib/libKF5KIOCore.so.5
#32 0x7f705d5713c7 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#33 0x7f705bde5a5e in ?? () from /usr/lib/libKF5KIOCore.so.5
#34 0x7f705d571fd1 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#35 0x7f705e517fdc in QApplicationPrivate::notify_helper (this=, receiver=0x56297a2e25c0, e=0x56297a1d1e60) at
kernel/qapplication.cpp:3717
#36 0x7f705e51f8d9 in QApplication::notify (this=0x7f7060f27fe0,
receiver=0x56297a2e25c0, e=0x56297a1d1e60) at kernel/qapplication.cpp:3476
#37 0x7f705d544fc0 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#38 0x7f705d547d9d in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#39 0x7f705d59b3e3 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /usr/lib/libQt5Core.so.5
#40 0x7f7057747a9a in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#41 0x7f7057747d28 in ?? () from /usr/lib/libglib-2.0.so.0
#42 0x7f7057747ddf in g_main_context_iteration 

[kwin] [Bug 379681] Crash after turning off compositions with Alt+Shift+F12

[awilfox]

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

--- Comment #9 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
5.8.7 release tarball with three backported patches from the 5.11 branch:

404f2675f8ca5496a5e528825078b1ce27669cd7
From: Marco Martin <notm...@gmail.com>
Date: Mon, 20 Mar 2017 17:01:39 +0100

fix compilation on old gcc

[ed: This is needed on gcc 6 as well on some platforms due to int being signed
by default.]


052fa2e4ee329810f62c29e546254fb45bf8a375
From: Takahiro Hashimoto <kenya...@gmail.com>
Date: Thu, 27 Oct 2016 09:43:21 +0900

[plugins/qpa] support use of modularized qtplatformsupport from Qt 5.8

[ed: We need this because we use Qt 5.9 LTS.]


e302f87598de6853147c872b631e9a1fe4864f42
From: Fabian Vogt <fab...@ritter-vogt.de>
Date: Sat, 23 Dec 2017 23:30:07 +0100

Properly detect Gallium drivers with newer Mesa

[ed: We need this because otherwise R300 doesn't do NPOT workaround properly on
Mesa 17.x]

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

[kpat] [Bug 389540] New: KPatience: crash on exit after winning Spider Solitaire game

[awilfox]

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

Bug ID: 389540
   Summary: KPatience: crash on exit after winning Spider
Solitaire game
   Product: kpat
   Version: 3.6
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: co...@kde.org
  Reporter: awil...@adelielinux.org
CC: kde-games-b...@kde.org
  Target Milestone: ---

Application: kpat (3.6)
 (Compiled from sources)
Qt Version: 5.9.1
Frameworks Version: 5.41.0
Operating System: Linux 4.14.8-mc2-easy x86_64

-- Information about the crash:
This computer is running Adelie Linux, which uses the musl libc.  The crash
occurs in musl's free() method - here is the relevant two lines from musl code:

/* Crash on corrupted footer (likely from buffer overflow) */
if (next->psize != self->csize) a_crash();

This suggests that the Spider solver had a small buffer overflow.

- What I was doing when the application crashed:
Quitting the application.

-- Backtrace:
Application: KPatience (kpat), signal: Segmentation fault
[KCrash Handler]
#8  a_crash () at ./arch/x86_64/atomic_arch.h:108
#9  free (p=0x5592d381b180) at src/malloc/malloc.c:476
#10 0x7f71829a83c5 in operator delete(void*) () from
/usr/lib/libstdc++.so.6
#11 0x7f71829a841e in operator delete[](void*) () from
/usr/lib/libstdc++.so.6
#12 0x5592d307208e in Solver::~Solver (this=0x5592d381a280,
__in_chrg=) at
/usr/src/packages/user/kpat/src/kpat-17.08.2/patsolve/patsolve.cpp:915
#13 0x5592d3087afb in SpiderSolver::~SpiderSolver (this=0x5592d381a280,
__in_chrg=) at
/usr/src/packages/user/kpat/src/kpat-17.08.2/patsolve/spidersolver.h:25
#14 SpiderSolver::~SpiderSolver (this=0x5592d381a280, __in_chrg=) at
/usr/src/packages/user/kpat/src/kpat-17.08.2/patsolve/spidersolver.h:25
#15 0x5592d304f9d0 in DealerScene::~DealerScene (this=0x5592d3805d60,
__in_chrg=) at
/usr/src/packages/user/kpat/src/kpat-17.08.2/dealer.cpp:605
#16 0x5592d308cd9e in Spider::~Spider (this=0x5592d3805d60,
__in_chrg=) at
/usr/src/packages/user/kpat/src/kpat-17.08.2/kpat_autogen/EWIEGA46WW/../../spider.h:45
#17 Spider::~Spider (this=0x5592d3805d60, __in_chrg=) at
/usr/src/packages/user/kpat/src/kpat-17.08.2/kpat_autogen/EWIEGA46WW/../../spider.h:45
#18 0x5592d3063772 in MainWindow::~MainWindow
(this=this@entry=0x5592d3465460, __in_chrg=,
__vtt_parm=) at
/usr/src/packages/user/kpat/src/kpat-17.08.2/mainwindow.cpp:142
#19 0x5592d3063891 in MainWindow::~MainWindow (this=0x5592d3465460,
__in_chrg=, __vtt_parm=) at
/usr/src/packages/user/kpat/src/kpat-17.08.2/mainwindow.cpp:145
#20 0x7f7182fa5ff0 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#21 0x7f71843bb4eb in QWidget::event (this=this@entry=0x5592d3465460,
event=event@entry=0x5592d5863320) at kernel/qwidget.cpp:9244
#22 0x7f71844b3beb in QMainWindow::event (this=this@entry=0x5592d3465460,
event=event@entry=0x5592d5863320) at widgets/qmainwindow.cpp:1557
#23 0x7f7185f8916b in KMainWindow::event (this=this@entry=0x5592d3465460,
ev=ev@entry=0x5592d5863320) at
/usr/src/packages/user/kxmlgui/src/kxmlgui-5.41.0/src/kmainwindow.cpp:865
#24 0x7f7185fce939 in KXmlGuiWindow::event (this=0x5592d3465460,
ev=0x5592d5863320) at
/usr/src/packages/user/kxmlgui/src/kxmlgui-5.41.0/src/kxmlguiwindow.cpp:119
#25 0x7f7184376fdc in QApplicationPrivate::notify_helper (this=, receiver=0x5592d3465460, e=0x5592d5863320) at
kernel/qapplication.cpp:3717
#26 0x7f718437e8d9 in QApplication::notify (this=0x7ffc10d64860,
receiver=0x5592d3465460, e=0x5592d5863320) at kernel/qapplication.cpp:3476
#27 0x7f7182f78fc0 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#28 0x7f7182f7bd9d in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#29 0x7f7182fcf3e3 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /usr/lib/libQt5Core.so.5
#30 0x7f717cdb2a9a in g_main_dispatch (context=0x7f7180616540) at
gmain.c:3148
#31 g_main_context_dispatch (context=context@entry=0x7f7180616540) at
gmain.c:3813
#32 0x7f717cdb2d28 in g_main_context_iterate
(context=context@entry=0x7f7180616540, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3886
#33 0x7f717cdb2ddf in g_main_context_iteration (context=0x7f7180616540,
may_block=1) at gmain.c:3947
#34 0x7f7182fce9af in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#35 0x7f7182f76f2a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#36 0x7f7182f7ff74 in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#37 0x5592d3045238 in main (argc=, argv=) at
/usr/src/packages/user/kpat/src/kpat-17.08.2/main.cpp:339

Reported using DrKonqi

-- 
You are receiving this mail 

[kwin] [Bug 379681] Crash after turning off compositions with Alt+Shift+F12

[awilfox]

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

A. Wilcox (awilfox) <awil...@adelielinux.org> changed:

   What|Removed |Added

 CC||awil...@adelielinux.org

--- Comment #6 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
As the original filer of 352548, please reopen this bug; it isn't a duplicate.

However, I *can* duplicate *this* bug myself.  Every time I open `ffplay` (as
noted in 388473), KWin seems to think it needs to disable compositing.  And
every time KWin tries to disable compositing, I receive this crash.

I do have libepoxy debug symbols and I can provide a full backtrace from
DrKonqi:

Application: KWin (kwin_x11), signal: Segmentation fault
[KCrash Handler]
#8  0x7fb8cd7cefdd in QQmlMetaType::qmlSingletonTypes() () from
/usr/lib/libQt5Qml.so.5
#9  0x7fb8cd7a56e7 in QQmlEngine::~QQmlEngine() () from
/usr/lib/libQt5Qml.so.5
#10 0x7fb8cd7a5791 in QQmlEngine::~QQmlEngine() () from
/usr/lib/libQt5Qml.so.5
#11 0x7fb8d5b2f09e in __funcs_on_exit () at src/exit/atexit.c:26
#12 0x7fb8d5b2559a in exit (code=code@entry=1) at src/exit/exit.c:30
#13 0x7fb8d5b31d95 in verrx (status=1, fmt=,
ap=ap@entry=0x7ffecc3057e8) at src/legacy/err.c:34
#14 0x7fb8d5b31ff7 in errx (status=status@entry=1,
fmt=fmt@entry=0x7fb8ce4d7970 "Couldn't find current GLX or EGL context.\n") at
src/legacy/err.c:65
#15 0x7fb8ce490a73 in epoxy_get_proc_address (name=0x7fb8ce4e9fcb
<entrypoint_strings+9515> "glDeleteProgram") at dispatch_common.c:780
#16 0x7fb8ce4b8b95 in epoxy_glDeleteProgram_resolver () at
gl_generated_dispatch.c:78351
#17 epoxy_glDeleteProgram_global_rewrite_ptr (program=16) at
gl_generated_dispatch.c:45276
#18 0x7fb8d2262a45 in KWin::BlurEffect::~BlurEffect (this=0x560887464680,
__in_chrg=) at
/usr/src/packages/user/kwin/src/kwin-5.8.7/effects/blur/blur.cpp:85
#19 0x7fb8d2262b21 in KWin::BlurEffect::~BlurEffect (this=0x560887464680,
__in_chrg=) at
/usr/src/packages/user/kwin/src/kwin-5.8.7/effects/blur/blur.cpp:88
#20 0x7fb8d55c4451 in KWin::EffectsHandlerImpl::unloadAllEffects
(this=this@entry=0x56088841b260) at
/usr/src/packages/user/kwin/src/kwin-5.8.7/effects.cpp:240
#21 0x7fb8d55c451d in KWin::EffectsHandlerImpl::~EffectsHandlerImpl
(this=0x56088841b260, __in_chrg=) at
/usr/src/packages/user/kwin/src/kwin-5.8.7/effects.cpp:223
#22 0x7fb8d55c4701 in KWin::EffectsHandlerImpl::~EffectsHandlerImpl
(this=0x56088841b260, __in_chrg=) at
/usr/src/packages/user/kwin/src/kwin-5.8.7/effects.cpp:224
#23 0x7fb8d55847d5 in KWin::Compositor::finish
(this=this@entry=0x56088746b920) at
/usr/src/packages/user/kwin/src/kwin-5.8.7/composite.cpp:394
#24 0x7fb8d5584f82 in KWin::Compositor::suspend (this=0x56088746b920,
reason=) at
/usr/src/packages/user/kwin/src/kwin-5.8.7/composite.cpp:573
#25 0x7fb8d3038fd1 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#26 0x7fb8d3d4bfdc in QApplicationPrivate::notify_helper (this=, receiver=0x56088746b920, e=0x56088f571ea0) at
kernel/qapplication.cpp:3717
#27 0x7fb8d3d538d9 in QApplication::notify (this=0x7ffecc3060c0,
receiver=0x56088746b920, e=0x56088f571ea0) at kernel/qapplication.cpp:3476
#28 0x7fb8d300bfc0 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#29 0x7fb8d300ed9d in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#30 0x7fb8d305ec27 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#31 0x7fb8be7f01bf in QUnixEventDispatcherQPA::processEvents
(this=, flags=...) at qunixeventdispatcher.cpp:68
#32 0x7fb8d3009f2a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#33 0x7fb8d3012f74 in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#34 0x7fb8d590a25c in kdemain (argc=, argv=0x7ffecc3061b8)
at /usr/src/packages/user/kwin/src/kwin-5.8.7/main_x11.cpp:466
#35 0x7fb8d5b2e866 in __libc_start_main (main=0x5608871776d0 ,
argc=3, argv=0x7ffecc3061b8) at src/env/__libc_start_main.c:74
#36 0x560887177718 in _start_c (p=) at crt/crt1.c:17
#37 0x5608871776f0 in _start ()

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

[frameworks-kfilemetadata] [Bug 375472] kfilemetadata test scripts have unnecessary dependency on Python 2

[awilfox]

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

A. Wilcox (awilfox) <awil...@adelielinux.org> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
URL||https://phabricator.kde.org
   ||/D4377
   Version Fixed In||5.37.0
  Latest Commit||76ed16d7943791c851eaafd
   ||9afedd3127b02
 Resolution|--- |FIXED

--- Comment #1 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
Fixed in commit 76ed16d7943791c851eaafd9afedd3127b02
Author: A. Wilcox <mailto:awil...@adelielinux.org>
AuthorDate: Tue Jul 11 21:41:34 2017 +0200
Commit: Matthieu Gallien <matthieu_gall...@yahoo.fr>
CommitDate: Sat Jul 29 16:51:36 2017 +0200

Fix Python dependency in test scripts for KFileMetaData (bug 375472)

Summary:
KFileMetaData test scripts are usable in both deprecated Python 2, and new
Python 3.  This removes 'python2' from the shebang and uses the regular
'python' interpreter, thereby removing the requirement of Python 2 being on a
system to be able to test KFileMetaData.

Additionally, it removes unused imports.

Test Plan:
This patch was applied to:
* 5.23
* 5.26
* 5.29

It was tested on Linux kernel 4.4 using:
* x86_64
* x86_32
* PowerPC

With the following Python versions:
* 2.7.10
* 3.4.4
* 3.5.1

It was tested on glibc and musl libc.

Reviewers: mgallien

Reviewed By: mgallien

Subscribers: #frameworks

Tags: #frameworks

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

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

[drkonqi] [Bug 362965] DrKonqi crashes opening DrKonqi on every crash...

[awilfox]

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

A. Wilcox (awilfox) <awil...@adelielinux.org> changed:

   What|Removed |Added

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

--- Comment #2 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
This appears to have been fixed upstream in Qt 5.9, and nothing to do with
DrKonqi.  Sorry for the noise.

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

[kwin] [Bug 388473] New: KWin crashes during window switching after previous crash

[awilfox]

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

Bug ID: 388473
   Summary: KWin crashes during window switching after previous
crash
   Product: kwin
   Version: 5.8.7
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: awil...@adelielinux.org
  Target Milestone: ---

Application: kwin_x11 (5.8.7)

Qt Version: 5.9.1
Frameworks Version: 5.41.0
Operating System: Linux 4.14.8-mc2-easy x86_64

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

Note: All my Plasma/KWin settings are the default ones from KDE upstream.  I
haven't changed any effects or settings other than focus follows mouse, and
using plastiK Aurorae theme.

There's another crash in KWin that I am trying to debug involving ffplay. 
While attempting to debug that crash, I used Alt+Tab to cycle through windows
to reach Firefox.  KWin had already crashed one time.  I noticed that on the
thumbnail bar (left third of screen), the Firefox window that was at the bottom
of the list had no thumbnail.  When I reached it, and it became highlighted,
KWin immediately crashed.  Upon relaunching, the Firefox window still had no
thumbnail, and using Alt+Tab again caused the same crash with the same
backtrace.  Repeated once again, and now thumbnails are no longer showing up
because compositing was disabled.  Re-enabling compositing now causes Alt+Tab
to always crash.



Version
===
KWin version: 5.8.7
Qt Version: 5.9.1
Qt compile version: 5.9.1
XCB compile version: 1.12

Operation Mode: X11 only

Build Options
=
KWIN_BUILD_DECORATIONS: yes
KWIN_BUILD_TABBOX: yes
KWIN_BUILD_ACTIVITIES: yes
HAVE_INPUT: yes
HAVE_DRM: yes
HAVE_GBM: yes
HAVE_X11_XCB: yes
HAVE_EPOXY_GLX: yes
HAVE_WAYLAND_EGL: yes

X11
===
Vendor: The X.Org Foundation
Vendor Release: 11903000
Protocol Version/Revision: 11/0
SHAPE: yes; Version: 0x11
RANDR: yes; Version: 0x14
DAMAGE: yes; Version: 0x11
Composite: yes; Version: 0x4
RENDER: yes; Version: 0xb
XFIXES: yes; Version: 0x50
SYNC: yes; Version: 0x31
GLX: yes; Version: 0x0

Decoration
==
Plugin: org.kde.kwin.aurorae
Theme: kwin4_decoration_qml_plastik
Blur: 1
onAllDesktopsAvailable: false
alphaChannelSupported: true
closeOnDoubleClickOnMenu: false
decorationButtonsLeft: 5, 4, 3, 7, 0
decorationButtonsRight: 6
borderSize: 2
gridUnit: 10
font: Noto Sans,10,-1,0,50,0,0,0,0,0
smallSpacing: 2
largeSpacing: 10

Options
===
focusPolicy: 1
nextFocusPrefersMouse: false
clickRaise: true
autoRaise: false
autoRaiseInterval: 750
delayFocusInterval: 300
shadeHover: false
shadeHoverInterval: 250
separateScreenFocus: false
placement: 4
focusPolicyIsReasonable: true
borderSnapZone: 10
windowSnapZone: 10
centerSnapZone: 0
snapOnlyWhenOverlapping: false
rollOverDesktops: true
focusStealingPreventionLevel: 1
legacyFullscreenSupport: false
operationTitlebarDblClick: 5000
operationMaxButtonLeftClick: 5000
operationMaxButtonMiddleClick: 5015
operationMaxButtonRightClick: 5014
commandActiveTitlebar1: 0
commandActiveTitlebar2: 30
commandActiveTitlebar3: 2
commandInactiveTitlebar1: 4
commandInactiveTitlebar2: 30
commandInactiveTitlebar3: 2
commandWindow1: 7
commandWindow2: 8
commandWindow3: 8
commandWindowWheel: 31
commandAll1: 10
commandAll2: 3
commandAll3: 14
keyCmdAllModKey: 16777251
showGeometryTip: false
condensedTitle: false
electricBorderMaximize: true
electricBorderTiling: true
electricBorderCornerRatio: 0.25
borderlessMaximizedWindows: false
killPingTimeout: 5000
hideUtilityWindowsForInactive: true
inactiveTabsSkipTaskbar: false
autogroupSimilarWindows: false
autogroupInForeground: true
compositingMode: 1
useCompositing: true
compositingInitialized: true
hiddenPreviews: 1
glSmoothScale: 2
colorCorrected: false
xrenderSmoothScale: false
maxFpsInterval: 1666
refreshRate: 0
vBlankTime: 600
glStrictBinding: true
glStrictBindingFollowsDriver: true
glCoreProfile: false
glPreferBufferSwap: 101
glPlatformInterface: 1
windowsBlockCompositing: true

Screen Edges

desktopSwitching: false
desktopSwitchingMovingClients: false
cursorPushBackDistance: 1x1
timeThreshold: 150
reActivateThreshold: 350
actionTopLeft: 0
actionTop: 0
actionTopRight: 0
actionRight: 0
actionBottomRight: 0
actionBottom: 0
actionBottomLeft: 0
actionLeft: 0

Screens
===
Multi-Head: no
Active screen follows mouse:  yes
Number of Screens: 1

Screen 0:
-
Name: DVI-0
Geometry: 0,0,1920x1080
Refresh Rate: 60


Compositing
===
Compositing is active
Compositing Type: OpenGL
OpenGL vendor string: X.Org
OpenGL renderer string: AMD CAICOS (DRM 2.50.0 / 4.14.8-mc2-easy, LLVM 4.0.0)
OpenGL version string: 3.0 Mesa 17.3.1
OpenGL platform interface: GLX
OpenGL shading language version string: 1.30
Driver: Unknown
GPU class: Unknown
OpenGL version: 3.0
GLSL version: 

[kmime] [Bug 385479] New: KMime DateFormatterTest fails with fancy format

[awilfox]

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

Bug ID: 385479
   Summary: KMime DateFormatterTest fails with fancy format
   Product: kmime
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: awil...@adelielinux.org
  Target Milestone: ---

12/17 Test #12: kmime-dateformattertest ..***Failed0.00 sec
* Start testing of DateFormatterTest *
Config: Using QtTest library 5.9.1, Qt 5.9.1 (x86_64-little_endian-lp64 shared
(dynamic) release build; by GCC 6.4.0)
PASS   : DateFormatterTest::initTestCase()
FAIL!  : DateFormatterTest::testFancyFormat() Compared values are not the same
   Actual   (f.dateString(dt)) : "Today 12:34"
   Expected (QString::fromLatin1("Today 12:34:56")): "Today 12:34:56"
   Loc:
[/usr/src/packages/user/kmime/src/kmime-17.08.1/autotests/dateformattertest.cpp(40)]
PASS   : DateFormatterTest::testLocalizedFormat()
PASS   : DateFormatterTest::cleanupTestCase()
Totals: 3 passed, 1 failed, 0 skipped, 0 blacklisted, 0ms
* Finished testing of DateFormatterTest *


Internally, fancy format uses QLocale::ShortFormat, which is of course
non-portable.  This could mean anything, and on Mac OS X and Windows it is even
user-customisable.  I would personally either not test Fancy Format, or if you
must test Fancy Format for the "Today" / "Yesterday" feature, then call
QTime::toString(ShortFormat) on the 12:34:56 time specified for that part of
the return value instead of relying on the format being hh:mm:ss.

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

[www.kde.org] [Bug 385252] Plasma 5.8 announcement / source pages are not working correctly

[awilfox]

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

A. Wilcox (awilfox) <awil...@adelielinux.org> changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED

--- Comment #6 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
I apologise if my message came off as insulting.  It probably should have been
phrased differently.  I was frustrated due to the fact our entire team was
blocking on this and wasting three days of our time trying to hunt down the
tarballs.  Also, I really didn't know if the sysadmin team did know what LTS
meant; a lot of people I meet (even in IT roles) do not, so I was trying to
make it as clear as possible.

I meant no offense and I thank both you and Ben for resolving these matters so
we can ship stable Plasma in our distro.  Thank you very much.

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

[www.kde.org] [Bug 385252] Plasma 5.8 announcement / source pages are not working correctly

[awilfox]

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

--- Comment #4 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
Excuse me, but are you kidding?

Have you considered maybe not shipping point updates to
plasma-workspace-wallpapers and oxygen-icons when they don't change content,
instead of REMOVING the current *LTS* release from the stable mirror?

The KDE system admins do understand what the term 'LTS' means, right?  It means
"long term support".  Long term.  Not short term.

The Plasma team has definitely committed[1] to releasing more LTS patches,
through at least April 2018.  They understand what LTS means, and understand
that distributions rely on stability so that they may package your software and
bring you the users that donate to your causes and make your community so
vibrant.

Since 5.8.8 is due in a few days shy of three weeks (2017-10-18), I suppose I
don't have much of a case for you moving the 5.8.7 release back to stable,
unless there is a major issue that causes the 5.8.8 release to slip.  (It
doesn't look like this will be the case, judging from the current backlog.) 
But you *must not* "archive" 5.8.8 to "save space" until April 2018.  Is this
clear?  5.8.8 is a Long Term Support release and must be supported Long Term.

Thank you for your understanding.

[1]: https://community.kde.org/Schedules/Plasma_5

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

[www.kde.org] [Bug 385252] New: Plasma 5.8 announcement / source pages are not working correctly

[awilfox]

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

Bug ID: 385252
   Summary: Plasma 5.8 announcement / source pages are not working
correctly
   Product: www.kde.org
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kde-...@kde.org
  Reporter: awil...@adelielinux.org
  Target Milestone: ---

The release page for 5.8.7 ( https://www.kde.org/announcements/plasma-5.8.7.php
) links to "Source Info" page ( https://www.kde.org/info/plasma-5.8.7.php )
that says "NOT OUT YET" and all links for the tarballs return a 404 Not Found
error.  The release page for 5.8.6 (
https://www.kde.org/announcements/plasma-5.8.7.php ) links to "Source Info"
page for 5.9.2.

This has delayed the ability for us (Adélie Linux) to package and release a
desktop based on KDE Plasma 5.  Thankfully a helpful IRC user (demm on
freenode) directed me to Attic/ where 5.8.7 has been [accidentally?] moved, so
that I could at least start the packaging process (however I hope these URLs
will be stable/ again, at least for 5.8.8).  The tarballs themselves have been
moved to Attic/ despite 5.8 being LTS branch and 5.8.7 being the current
release of it.

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

[extra-cmake-modules] [Bug 373175] _XOPEN_SOURCE needs to be defined when using -std=iso9899:1990

[awilfox]

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

A. Wilcox (awilfox) <awil...@adelielinux.org> changed:

   What|Removed |Added

Version|5.28.0  |5.38.0

--- Comment #1 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
Just checked and this still applies cleanly to 5.38.0, and is still needed.

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

[konsole] [Bug 381945] New: Konsole segfault after pulling tab out and resizing window

[awilfox]

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

Bug ID: 381945
   Summary: Konsole segfault after pulling tab out and resizing
window
   Product: konsole
   Version: 16.08.3
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: awil...@adelielinux.org
  Target Milestone: ---

Application: konsole (16.08.3)
 (Compiled from sources)
Qt Version: 5.6.1
Frameworks Version: 5.28.0
Operating System: Linux 4.10.0-rc5-ciall x86_64
Distribution (Platform): Gentoo Packages

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

I had pulled a tab out of one window into a new window.  The new window was
maximised, so I resized the window so that I could see the main window under
the tab.  Konsole then segfaulted.

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8d8917e7c0 (LWP 27553))]

Thread 8 (Thread 0x7f8d5f6cb700 (LWP 27560)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f8d6d9b3b8d in cnd_wait (cond=0x1452860, mtx=0x1452838) at
/var/tmp/portage/media-libs/mesa-13.0.0/work/mesa-13.0.0/include/c11/threads_posix.h:159
#2  0x7f8d6d9b40c7 in util_queue_thread_func (input=0x14549d0) at
/var/tmp/portage/media-libs/mesa-13.0.0/work/mesa-13.0.0/src/gallium/auxiliary/util/u_queue.c:76
#3  0x7f8d6d9b4712 in impl_thrd_routine (p=0x14549f0) at
/var/tmp/portage/media-libs/mesa-13.0.0/work/mesa-13.0.0/include/c11/threads_posix.h:87
#4  0x7f8d82330434 in start_thread (arg=0x7f8d5f6cb700) at
pthread_create.c:333
#5  0x7f8d88c528fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f8d5fecc700 (LWP 27559)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f8d6d9b3b8d in cnd_wait (cond=0x1452860, mtx=0x1452838) at
/var/tmp/portage/media-libs/mesa-13.0.0/work/mesa-13.0.0/include/c11/threads_posix.h:159
#2  0x7f8d6d9b40c7 in util_queue_thread_func (input=0x1454a10) at
/var/tmp/portage/media-libs/mesa-13.0.0/work/mesa-13.0.0/src/gallium/auxiliary/util/u_queue.c:76
#3  0x7f8d6d9b4712 in impl_thrd_routine (p=0x14574e0) at
/var/tmp/portage/media-libs/mesa-13.0.0/work/mesa-13.0.0/include/c11/threads_posix.h:87
#4  0x7f8d82330434 in start_thread (arg=0x7f8d5fecc700) at
pthread_create.c:333
#5  0x7f8d88c528fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f8d606cd700 (LWP 27558)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f8d6d9b3b8d in cnd_wait (cond=0x1452860, mtx=0x1452838) at
/var/tmp/portage/media-libs/mesa-13.0.0/work/mesa-13.0.0/include/c11/threads_posix.h:159
#2  0x7f8d6d9b40c7 in util_queue_thread_func (input=0x14549d0) at
/var/tmp/portage/media-libs/mesa-13.0.0/work/mesa-13.0.0/src/gallium/auxiliary/util/u_queue.c:76
#3  0x7f8d6d9b4712 in impl_thrd_routine (p=0x14549f0) at
/var/tmp/portage/media-libs/mesa-13.0.0/work/mesa-13.0.0/include/c11/threads_posix.h:87
#4  0x7f8d82330434 in start_thread (arg=0x7f8d606cd700) at
pthread_create.c:333
#5  0x7f8d88c528fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f8d60ece700 (LWP 27557)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f8d6d9b3b8d in cnd_wait (cond=0x1452860, mtx=0x1452838) at
/var/tmp/portage/media-libs/mesa-13.0.0/work/mesa-13.0.0/include/c11/threads_posix.h:159
#2  0x7f8d6d9b40c7 in util_queue_thread_func (input=0x1457a70) at
/var/tmp/portage/media-libs/mesa-13.0.0/work/mesa-13.0.0/src/gallium/auxiliary/util/u_queue.c:76
#3  0x7f8d6d9b4712 in impl_thrd_routine (p=0x1457a90) at
/var/tmp/portage/media-libs/mesa-13.0.0/work/mesa-13.0.0/include/c11/threads_posix.h:87
#4  0x7f8d82330434 in start_thread (arg=0x7f8d60ece700) at
pthread_create.c:333
#5  0x7f8d88c528fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f8d618d4700 (LWP 27556)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f8d6d9b3b8d in cnd_wait (cond=0x1451590, mtx=0x1451568) at
/var/tmp/portage/media-libs/mesa-13.0.0/work/mesa-13.0.0/include/c11/threads_posix.h:159
#2  0x7f8d6d9b40c7 in util_queue_thread_func (input=0x1450f10) at
/var/tmp/portage/media-libs/mesa-13.0.0/work/mesa-13.0.0/src/gallium/auxiliary/util/u_queue.c:76
#3  0x7f8d6d9b4712 in impl_thrd_routine (p=0x1452240) at
/var/tmp/portage/media-libs/mesa-13.0.0/work/mesa-13.0.0/include/c11/threads_posix.h:87
#4  0x7f8d82330434 in start_thread (arg=0x7f8d618d4700) at
pthread_create.c:333
#5  

[kde] [Bug 376660] New: Plasma 5 has unsafe, non-portable behaviour while exiting cleanly

[awilfox]

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

Bug ID: 376660
   Summary: Plasma 5 has unsafe, non-portable behaviour while
exiting cleanly
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: awil...@adelielinux.org
  Target Milestone: ---

Application: kdeinit5 (5.8.4)
 (Compiled from sources)
Qt Version: 5.6.1
Frameworks Version: 5.28.0
Operating System: Linux 4.10.0-rc5-ciall x86_64
Distribution (Platform): Gentoo Packages

-- Information about the crash:
I was attempting to relaunch KWin since it had become very laggy (as it does
after two weeks or so of running).  I used `kshell5 kwin_x11 --replace` which
worked fine, but the exiting KWin (the one that was being replaced) crashed.

There are so many unsafe things occurring during teardown, I don't even know
where to begin...

- It should definitely not be attempting to *create* pixmaps in an object's
destructor.
- Actually, it is very unsafe to make *any* XIO calls without a custom error
handler, because nested exit(3) calls are undefined in POSIX and are known to
cause infinite recursion on some implementations.  And exit(3) is exactly what
is done by the default XIO error handler.
- It looks like a lot of the ridiculous unsafe beahviour is actually
originating in Qt, so I will likely file a further bug there.  If/when I do, I
will update this bug with a link there.

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kdeinit5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f49a1383780 (LWP 4423))]

Thread 9 (Thread 0x7f49614c5700 (LWP 4436)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f498f368eaa in QTWTF::TCMalloc_PageHeap::scavengerThread
(this=0x7f498f44b820 ) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x7f498f368e26 in QTWTF::TCMalloc_PageHeap::runScavengerThread
(context=0x7f498f4598f4 ) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x7f499e259434 in start_thread (arg=0x7f49614c5700) at
pthread_create.c:333
#4  0x7f499f97b8fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7f4968d16700 (LWP 4433)):
#0  0x7f499f974503 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f499fec0f74 in qt_safe_select (nfds=18, fdread=0x7f4964000a78,
fdwrite=0x7f4964000d08, fdexcept=0x7f4964000f98, orig_timeout=)
at kernel/qcore_unix.cpp:75
#2  0x7f499fec1b0b in QEventDispatcherUNIXPrivate::doSelect
(this=0x7f49640008e0, flags=..., timeout=0x0) at
kernel/qeventdispatcher_unix.cpp:192
#3  0x7f499fec2b9d in QEventDispatcherUNIX::processEvents
(this=0x7f49640008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#4  0x7f499fe74001 in QEventLoop::processEvents (flags=..., this=) at kernel/qeventloop.cpp:128
#5  QEventLoop::exec (this=0x7f4968d15e50, flags=...) at
kernel/qeventloop.cpp:204
#6  0x7f499fcc95e9 in QThread::exec (this=) at
thread/qthread.cpp:500
#7  0x7f498c179bf6 in QQmlThreadPrivate::run (this=0x29e3050) at
qml/ftw/qqmlthread.cpp:141
#8  0x7f499fcccd24 in QThreadPrivate::start (arg=0x29e3050) at
thread/qthread_unix.cpp:341
#9  0x7f499e259434 in start_thread (arg=0x7f4968d16700) at
pthread_create.c:333
#10 0x7f499f97b8fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f4969517700 (LWP 4432)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f49736c7b8d in cnd_wait (cond=0x26da690, mtx=0x26da668) at
/var/tmp/portage/media-libs/mesa-13.0.0/work/mesa-13.0.0/include/c11/threads_posix.h:159
#2  0x7f49736c80c7 in util_queue_thread_func (input=0x26dc810) at
/var/tmp/portage/media-libs/mesa-13.0.0/work/mesa-13.0.0/src/gallium/auxiliary/util/u_queue.c:76
#3  0x7f49736c8712 in impl_thrd_routine (p=0x26df310) at
/var/tmp/portage/media-libs/mesa-13.0.0/work/mesa-13.0.0/include/c11/threads_posix.h:87
#4  0x7f499e259434 in start_thread (arg=0x7f4969517700) at
pthread_create.c:333
#5  0x7f499f97b8fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f4969d18700 (LWP 4431)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f49736c7b8d in cnd_wait (cond=0x26da690, mtx=0x26da668) at
/var/tmp/portage/media-libs/mesa-13.0.0/work/mesa-13.0.0/include/c11/threads_posix.h:159
#2  0x7f49736c80c7 in util_queue_thread_func (input=0x26df8a0) at
/var/tmp/portage/media-libs/mesa-13.0.0/work/mesa-13.0.0/src/gallium/auxiliary/util/u_queue.c:76
#3  0x7f49736c8712 in impl_thrd_routine 

[konsole] [Bug 362197] Scrollback buffer loses data when it grows large enough

[awilfox]

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

A. Wilcox (awilfox) <awil...@adelielinux.org> changed:

   What|Removed |Added

 CC||awil...@adelielinux.org

--- Comment #1 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
I actually hit this.  As a distro maintainer, I started a shell session on 11
December to start porting our base system to PowerPC.  I then started building
Qt 5.7 (and all its dependencies).  Then KDE Frameworks 5.  While building
Phonon, I noticed weird corruption of the build results.

I am using Konsole 16.08.3 with KF 5.28.  When I saved the shell output, it was
in very weird pieces/chunks, like this (the first few lines of the resultant
file, unedited):


storyn.
/t
mp/envi
onment'.
ch is o
 non-c
ass type ‘int’
operator=(const QStyleOptionGraphicsItem&)’ first required here
64 -ggdb -mcpu=G3 -fno-omit-frame-pointer -Wall -Wextra -Wsign-compare -Wundef
-Wpointer-arith -Wvolatile-registe



It seems to me that somewhere, a signed 32-bit integer is being used:

-rw---  1 awilcox awilcox 2147485900 Jan 23 16:03
/tmp/konsole-hF4401.history

That `ls -l` was run at 16:15 and Phonon was still building, so all the output
was just being lost.  Actually, the previous output was also being corrupted.

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

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

[awilfox]

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

--- Comment #52 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
If it helps any, I can relay that I am using Translucency, but none of the
Dialogue (Base, Parent, etc) effects are enabled.

Again, on amdgpu.ko with a Radeon R9 270.  I will gladly test the patch on my
system; though I run in to this so rarely that I can't reliably reproduce it, I
can still ensure it does not do any further damage either.

My system is always under heavy load because the I/O is crap due to buggy/bad
SATA drivers.  So I cannot comment on whether that causes it or not.

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

[frameworks-kfilemetadata] [Bug 375472] New: kfilemetadata test scripts have unnecessary dependency on Python 2

[awilfox]

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

Bug ID: 375472
   Summary: kfilemetadata test scripts have unnecessary dependency
on Python 2
   Product: frameworks-kfilemetadata
   Version: 5.29.0
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: pinak.ah...@gmail.com
  Reporter: awil...@adelielinux.org
  Target Milestone: ---

Created attachment 103608
  --> https://bugs.kde.org/attachment.cgi?id=103608=edit
Universal Python patch for KFileMetadata 5.23-5.29

The test scripts for external extractor and external writer use a simple Python
script.  This is great, but there are two issues with the scripts:

- unnecessary imports of {os.path,os,subprocess}
- shebang uses /usr/bin/python2 when the scripts function on Python 3.4 and 3.5

Attached patch should work, and has been tested on the following matrix:

- KFileMetadata 5.23, 5.26, and 5.29.
- glibc and musl libcs on Linux 4.4 kernel
- x86, x86_64, ppc
- Python 2.7, Python 3.4.4, Python 3.5.2

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

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

[awilfox]

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

--- Comment #40 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
(In reply to Martin Gräßlin from comment #37)
> The problem is: we developers are not able to reproduce the issue. If we try
> the steps outlined in this bug and its many duplicates it just doesn't
> crash. There is an important part of the puzzle still missing. Something is
> different for our users and for us trying to investigate.
> 
> We need your support to figure out what it is. Once we find the key it will
> be easy to fix. That is the proper way forward. Ranting won't fix the issue
> but just demotivates those working on it. Please remember that I and most
> KDE developers are volunteers working in their free time on it.

I want to help!  What can I provide?

(In reply to marc from comment #38)
> - it appears only with Intel on-chip card [HD graphics]

Maybe you miss my comment #34:
> OpenGL renderer string: Gallium 0.4 on AMD PITCAIRN

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Curacao PRO [Radeon R7 370 / R9 270/370 OEM]

I am using a R9 270 and amdgpu.ko.  I have not used composition for months
until a few weeks ago to see if Mesa 13.0 finally fixes my OpenGL woes.  It
seems to have fixed most of them, but then I get this error.  So I report it.

I wish to be of more assistance, but I do not know what to provide.  I continue
to use my WINE-based task scheduler, and have pressed F10 hundreds of times
since the crash, and don't have it any more.  It is indeed very random.  I can
say I am using the beautiful plastiK window decorations with Breeze widget
styles.  I know that plastiK has been source of bugs in the past.  But still,
it is the only decoration that I truly enjoy, so I continue to use it.

Maybe that is a difference?

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

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

[awilfox]

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

A. Wilcox (awilfox) <awil...@adelielinux.org> changed:

   What|Removed |Added

 CC||awil...@adelielinux.org

--- Comment #34 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
I have a task scheduler (for my life, not my computer: Above & Beyond) that
runs in 32-bit WINE.  When I pressed F10 to insert a done item - which I have
done thousands of times before - this time I received a segmentation fault like
the one reported in comment 15.

I have SupportInformation, .xsession-errors, and full core dump (xz compressed:
6,170.5 KiB from original 3,077.5 MiB) available if any would be helpful.

KWin version: 5.8.4
Qt Version: 5.6.1
Qt compile version: 5.6.1
Compositing is active
Compositing Type: OpenGL
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD PITCAIRN (DRM 3.8.0 /
4.9.0-rc8-ciall, LLVM 3.9.0)
OpenGL version string: 4.3 (Core Profile) Mesa 13.0.0
OpenGL platform interface: EGL
OpenGL shading language version string: 4.30
OpenGL version: 4.3
GLSL version: 4.30
Mesa version: 13.0
X server version: 1.18.4
Linux kernel version: 4.9
Direct rendering: Requires strict binding: no
GLSL shaders:  yes
Texture NPOT support:  yes
Virtual Machine:  no
OpenGL 2 Shaders are used
Painting blocks for vertical retrace:  no

Backtrace of the crash I experienced:

Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0456822800 (LWP 14617))]

Thread 11 (Thread 0x7f04077fe700 (LWP 14641)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0453286eaa in QTWTF::TCMalloc_PageHeap::scavengerThread
(this=0x7f0453369820 ) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x7f0453286e26 in QTWTF::TCMalloc_PageHeap::runScavengerThread
(context=0x7f04533778f4 <QTWTF::pageheap_memory+57556>) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x7f04563a8434 in start_thread (arg=0x7f04077fe700) at
pthread_create.c:333
#4  0x7f04560ef8fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7f041e0ad700 (LWP 14638)):
#0  0x7f04560e8503 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f0454085f74 in qt_safe_select (nfds=20, fdread=0x7f0418000a78,
fdwrite=0x7f0418000d08, fdexcept=0x7f0418000f98, orig_timeout=)
at kernel/qcore_unix.cpp:75
#2  0x7f0454086b0b in QEventDispatcherUNIXPrivate::doSelect
(this=0x7f04180008e0, flags=..., timeout=0x0) at
kernel/qeventdispatcher_unix.cpp:192
#3  0x7f0454087b9d in QEventDispatcherUNIX::processEvents
(this=0x7f04180008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#4  0x7f0454039001 in QEventLoop::processEvents (flags=..., this=) at kernel/qeventloop.cpp:128
#5  QEventLoop::exec (this=0x7f041e0acdd0, flags=...) at
kernel/qeventloop.cpp:204
#6  0x7f0453e8e5e9 in QThread::exec (this=) at
thread/qthread.cpp:500
#7  0x7f044f17dbf6 in QQmlThreadPrivate::run (this=0xedb7f0) at
qml/ftw/qqmlthread.cpp:141
#8  0x7f0453e91d24 in QThreadPrivate::start (arg=0xedb7f0) at
thread/qthread_unix.cpp:341
#9  0x7f04563a8434 in start_thread (arg=0x7f041e0ad700) at
pthread_create.c:333
#10 0x7f04560ef8fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7f041ed40700 (LWP 14637)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f04350cfb8d in cnd_wait (cond=0x1139760, mtx=0x1139738) at
/var/tmp/portage/media-libs/mesa-13.0.0/work/mesa-13.0.0/include/c11/threads_posix.h:159
#2  0x7f04350d00c7 in util_queue_thread_func (input=0x113b8f0) at
/var/tmp/portage/media-libs/mesa-13.0.0/work/mesa-13.0.0/src/gallium/auxiliary/util/u_queue.c:76
#3  0x7f04350d0712 in impl_thrd_routine (p=0x113e3f0) at
/var/tmp/portage/media-libs/mesa-13.0.0/work/mesa-13.0.0/include/c11/threads_posix.h:87
#4  0x7f04563a8434 in start_thread (arg=0x7f041ed40700) at
pthread_create.c:333
#5  0x7f04560ef8fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7f041f541700 (LWP 14636)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f04350cfb8d in cnd_wait (cond=0x1139760, mtx=0x1139738) at
/var/tmp/portage/media-libs/mesa-13.0.0/work/mesa-13.0.0/include/c11/threads_posix.h:159
#2  0x7f04350d00c7 in util_queue_thread_func (input=0x113e980) at
/var/tmp/portage/media-libs/mesa-13.0.0/work/mesa-13.0.0/src/gallium/auxiliary/util/u_queue.c:76
#3  0x7f04350d0712 in impl_thrd_routine (p=0x113e9a0) at
/var/tmp/portage/media-libs/mesa-13.0.0/work/mesa-13.0.0/include/c11/threads_posix.h:87
#4  0x7f04563a8434 in start_thread (arg=0x7f041f54

[extra-cmake-modules] [Bug 373175] New: _XOPEN_SOURCE needs to be defined when using -std=iso9899:1990

[awilfox]

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

Bug ID: 373175
   Summary: _XOPEN_SOURCE needs to be defined when using
-std=iso9899:1990
   Product: extra-cmake-modules
   Version: 5.28.0
  Platform: Compiled Sources
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: alex.me...@kde.org
  Reporter: awil...@adelielinux.org
CC: ecm-bugs-n...@kde.org
  Target Milestone: ---

Created attachment 102573
  --> https://bugs.kde.org/attachment.cgi?id=102573=edit
KDECompilerSettings: Ensure POSIX correctness

When building on non-glibc Unix platforms, such as Solaris, NetBSD, and
Linux/musl or Linux/uclibc, multiple components of KF5 fail to build.  This is
because -std=iso9899:1990 is specified (for strict C90 compliance) but
_XOPEN_SOURCE is not defined, so none of the POSIX interfaces are exported.  I
have seen this reported in at least:

* kscreenlocker
* plasma-workspace

The attached patch resolves this issue on all our build boxes; additionally,
applying it to my glibc builder did not change the already working result.

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

[valgrind] [Bug 359202] Add musl libc configure/compile

[awilfox]

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

A. Wilcox (awilfox) <awil...@adelielinux.org> changed:

   What|Removed |Added

 CC||awil...@adelielinux.org

--- Comment #3 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
Created attachment 102572
  --> https://bugs.kde.org/attachment.cgi?id=102572=edit
Updated patch for 3.10.1

I've taken the patch that was posted here and updated it to apply cleanly to
3.10.1.  I've only tested memcheck, but it works great.

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

[frameworks-knotifications] [Bug 348414] Crash in KNotification::flags() (NotifyByAudio::onAudioFinished)

[awilfox]

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

--- Comment #70 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
(In reply to RJVB from comment #69)
> So I think we may be looking at something akin to GUI widgets being deleted
> while events are still pending (or can still be generated for them) because
> of `delete widget;` instead using `widget->deleteLater();`. It's weird that
> this would be required for alerts with an asynchronous nature (which sound
> alerts have by definition if they play through a sound daemon?), but I
> presume this could be a side-effect of providing an application's widget as
> the parent for a QObject inherited by a (hypothetical) KNotifications
> instance.
> 
> I hope I'm not rambling too much here, but this would explain the random
> nature of the crash: it depends on system load and to what extent the sound
> alert can be processed sufficiently to be able to cope with its
> infrastructure being taken down under its feet. With the dolphin crash I
> just had something like this was clearly going on: the laptop had just been
> woken from sleep, no sounds had been played yet, it was updating the locate
> and/or apt databases (etc), so pulseaudio must have taken just long enough
> to be swapped in to allow me to accept the warning message before the alert
> sound had even started to play.

The system that I experienced my most recent crash on is used as a buildbox and
was building Firefox when the crash happened.  System load was high and my wait
time was low; I hit Alt+F4 and immediately Alt+D to 'D'iscard the unsaved
changes in KWrite.  I'm not sure the dialogue even popped.

> Another potentially relevant observation: I use the VLC phonon backend
> (latest version, git master/head).

I'm not running -HEAD, but I am running Phonon-VLC as well - version 0.9.0
here.

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

[frameworks-knotifications] [Bug 348414] Crash in KNotification::flags() (NotifyByAudio::onAudioFinished)

[awilfox]

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

--- Comment #67 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
After months of not having this error, I have just hit it again closing an
unsaved file in KWrite:

Thread 1 (Thread 0x7fde50bba780 (LWP 6985)):
[KCrash Handler]
#6  0x7fde3ef727b4 in KNotification::flags (this=0x371f6e0) at
/var/tmp/portage/kde-frameworks/knotifications-5.26.0/work/knotifications-5.26.0/src/knotification.cpp:233
#7  0x7fde3ef90cc8 in NotifyByAudio::onAudioFinished (this=0x2fa3d90) at
/var/tmp/portage/kde-frameworks/knotifications-5.26.0/work/knotifications-5.26.0/src/notifybyaudio.cpp:147
#8  0x7fde4dd19e50 in QMetaObject::activate (sender=0x30261a0,
signalOffset=, local_signal_index=,
argv=) at kernel/qobject.cpp:3730
#9  0x7fde4dd1336f in QObject::event (this=0x30261a0, e=) at
kernel/qobject.cpp:1256
#10 0x7fde4e582792 in QApplicationPrivate::notify_helper (this=, receiver=0x30261a0, e=0x3667800) at kernel/qapplication.cpp:3804
#11 0x7fde4e5845c2 in QApplication::notify (this=,
receiver=0x30261a0, e=0x3667800) at kernel/qapplication.cpp:3163
#12 0x7fde4dceb73b in QCoreApplication::notifyInternal2
(receiver=0x30261a0, event=0x3667800) at kernel/qcoreapplication.cpp:1015
#13 0x7fde4dcec2f8 in QCoreApplication::sendEvent (receiver=0x30261a0,
event=0x3667800) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:225
#14 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0,
data=0x241b610) at kernel/qcoreapplication.cpp:1650
#15 0x7fde4dd395a3 in postEventSourceDispatch (s=0x247e490) at
kernel/qeventdispatcher_glib.cpp:270
#16 0x7fde48790dcd in g_main_dispatch (context=) at
/var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3154
#17 g_main_context_dispatch (context=) at
/var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3769
#18 0x7fde487910f9 in g_main_context_iterate (context=,
block=, dispatch=, self=) at
/var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3840
#19 0x7fde4879117e in g_main_context_iteration (context=,
may_block=1) at
/var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3901
#20 0x7fde4dd390fc in QEventDispatcherGlib::processEvents (this=0x2484df0,
flags=...) at kernel/qeventdispatcher_glib.cpp:417
#21 0x7fde4dce8001 in QEventLoop::processEvents (flags=..., this=) at kernel/qeventloop.cpp:128
#22 QEventLoop::exec (this=0x7ffe4dfe1b30, flags=...) at
kernel/qeventloop.cpp:204
#23 0x7fde4dcebd63 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1285
#24 0x00410460 in main (argc=, argv=) at
/var/tmp/portage/kde-apps/kwrite-16.08.1/work/kate-16.08.1/kwrite/main.cpp:284

As noted in the backtrace I am still on KF 5.26.  I will upgrade to 5.28 and
see if this persists.  Oddly I have been on 5.26 since 22 September with no
crash until now.  uptime(1) shows only 10 days 2 hours 41 minutes, so it
doesn't look related to that either.  Just random.

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

[konsole] [Bug 372058] New: Konsole crashes when attempting to save output to a file

[awilfox]

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

Bug ID: 372058
   Summary: Konsole crashes when attempting to save output to a
file
   Product: konsole
   Version: 16.08.1
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: awil...@adelielinux.org
  Target Milestone: ---

Application: konsole (16.08.1)
 (Compiled from sources)
Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.8.0-rc5-ciall x86_64
Distribution (Platform): Gentoo Packages

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

I was attempting to save the output of a terminal to a file.  I accidentally
typed into the "file type" box instead of the "file name" box.  I backspaced
and then went to the file name box.  I started to type a file name and when I
did, it crashed.

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff87935f7c0 (LWP 18833))]

Thread 5 (Thread 0x7ff84f551700 (LWP 31695)):
#0  0x7ff878e287fd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7ff86ee62f01 in poll_func (ufds=0x7ff8480141a0, nfds=3, timeout=-1,
userdata=0x641b980) at
/var/tmp/portage/media-sound/pulseaudio-9.0/work/pulseaudio-9.0/src/pulse/thread-mainloop.c:69
#2  0x7ff86ee5474d in pa_mainloop_poll (m=0x641b860) at
/var/tmp/portage/media-sound/pulseaudio-9.0/work/pulseaudio-9.0/src/pulse/mainloop.c:844
#3  0x7ff86ee54d3a in pa_mainloop_iterate (m=0x641b860, block=, retval=0x0) at
/var/tmp/portage/media-sound/pulseaudio-9.0/work/pulseaudio-9.0/src/pulse/mainloop.c:926
#4  0x7ff86ee54de0 in pa_mainloop_run (m=0x641b860, retval=0x0) at
/var/tmp/portage/media-sound/pulseaudio-9.0/work/pulseaudio-9.0/src/pulse/mainloop.c:944
#5  0x7ff86ee632cc in thread (userdata=0x15c41d30) at
/var/tmp/portage/media-sound/pulseaudio-9.0/work/pulseaudio-9.0/src/pulse/thread-mainloop.c:100
#6  0x7ff86a3c9854 in internal_thread_func (userdata=0x641bb00) at
/var/tmp/portage/media-sound/pulseaudio-9.0/work/pulseaudio-9.0/src/pulsecore/thread-posix.c:81
#7  0x7ff8724f6434 in start_thread (arg=0x7ff84f551700) at
pthread_create.c:333
#8  0x7ff878e318fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7ff851f3d700 (LWP 18836)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7ff85dc82eed in cnd_wait (cond=0x241c2b8, mtx=0x241c290) at
/var/tmp/portage/media-libs/mesa-12.0.3/work/mesa-12.0.3/include/c11/threads_posix.h:159
#2  0x7ff85dc82e9a in pipe_semaphore_wait (sema=0x241c290) at
/var/tmp/portage/media-libs/mesa-12.0.3/work/mesa-12.0.3/src/gallium/auxiliary/os/os_thread.h:259
#3  0x7ff85dc82756 in radeon_drm_cs_emit_ioctl (param=0x241be40) at
/var/tmp/portage/media-libs/mesa-12.0.3/work/mesa-12.0.3/src/gallium/winsys/radeon/drm/radeon_drm_winsys.c:710
#4  0x7ff85dc82e52 in impl_thrd_routine (p=0x241c4b0) at
/var/tmp/portage/media-libs/mesa-12.0.3/work/mesa-12.0.3/include/c11/threads_posix.h:87
#5  0x7ff8724f6434 in start_thread (arg=0x7ff851f3d700) at
pthread_create.c:333
#6  0x7ff878e318fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7ff85f980700 (LWP 18835)):
#0  0x7ff878e247dd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7ff870a80e7f in g_wakeup_acknowledge (wakeup=0x22ac7b0) at
/var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gwakeup.c:210
#2  0x7ff870a3d9e6 in g_main_context_check (context=0x7ff858000990,
max_priority=2147483647, fds=0x7ff8580013c0, n_fds=1) at
/var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3632
#3  0x7ff870a3e0ea in g_main_context_iterate (context=,
block=, dispatch=, self=) at
/var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3837
#4  0x7ff870a3e17e in g_main_context_iteration (context=,
may_block=1) at
/var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3901
#5  0x7ff875b0a11c in QEventDispatcherGlib::processEvents
(this=0x7ff8580008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#6  0x7ff875ab9001 in QEventLoop::processEvents (flags=..., this=) at kernel/qeventloop.cpp:128
#7  QEventLoop::exec (this=0x7ff85f97fe00, flags=...) at
kernel/qeventloop.cpp:204
#8  0x7ff87590e5e9 in QThread::exec (this=) at
thread/qthread.cpp:500
#9  0x7ff87942f430 in QDBusConnectionManager::run (this=0x7ff879491260
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:189
#10 0x7ff875911d24 in QThreadPrivate::start (arg=0x7ff879491260 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at

[plasmashell] [Bug 342763] Crash In Task Manager Item Changed

[awilfox]

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

A. Wilcox (awilfox) <awil...@adelielinux.org> changed:

   What|Removed |Added

 CC||awil...@adelielinux.org

--- Comment #237 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
Using "Icons-Only Task Manager" under Plasma 5.7 and seeing this, along with a
lot of other oddities, when I close windows that are grouped.

Most of the time, the icons just move around wildly for no reason.  For
instance, if I have three Kate windows open, and I close one, suddenly Kate has
moved to the end, and when I try to drag it back to where it was, two other
icons jump out of place.  It's all quite messy (and not happening in 5.6).

Backtrace of the crash I experienced when closing one of five KWrites I had
open:

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

Thread 15 (Thread 0x7f746bb81700 (LWP 18783)):
#0  0x7f7520d2b7fd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f751cba40c7 in g_main_context_poll (priority=0, context=, timeout=, fds=, n_fds=) at
/var/tmp/portage/dev-libs/glib-2.48.1-r1/work/glib-2.48.1/glib/gmain.c:4135
#2  g_main_context_iterate (context=, block=,
dispatch=, self=) at
/var/tmp/portage/dev-libs/glib-2.48.1-r1/work/glib-2.48.1/glib/gmain.c:3835
#3  0x7f751cba419e in g_main_context_iteration (context=,
may_block=1) at
/var/tmp/portage/dev-libs/glib-2.48.1-r1/work/glib-2.48.1/glib/gmain.c:3901
#4  0x7f75215d611c in QEventDispatcherGlib::processEvents
(this=0x7f74640008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5  0x7f7521585001 in QEventLoop::processEvents (flags=..., this=) at kernel/qeventloop.cpp:128
#6  QEventLoop::exec (this=0x7f746bb80d90, flags=...) at
kernel/qeventloop.cpp:204
#7  0x7f75213da5e9 in QThread::exec (this=) at
thread/qthread.cpp:500
#8  0x7f7524494978 in QQuickPixmapReader::run (this=0x15dae50) at
util/qquickpixmapcache.cpp:817
#9  0x7f75213ddd24 in QThreadPrivate::start (arg=0x15dae50) at
thread/qthread_unix.cpp:341
#10 0x7f7520834434 in start_thread (arg=0x7f746bb81700) at
pthread_create.c:333
#11 0x7f7520d348fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 14 (Thread 0x7f7470bc2700 (LWP 18782)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f7479e78de3 in cnd_wait (mtx=0x13d5538, cond=) at
/var/tmp/portage/media-libs/mesa-11.1.0/work/mesa-11.1.0/include/c11/threads_posix.h:159
#2  pipe_semaphore_wait (sema=0x13d5538) at
/var/tmp/portage/media-libs/mesa-11.1.0/work/mesa-11.1.0/src/gallium/auxiliary/os/os_thread.h:259
#3  thread_function (init_data=init_data@entry=0x13d5490) at
/var/tmp/portage/media-libs/mesa-11.1.0/work/mesa-11.1.0/src/gallium/drivers/llvmpipe/lp_rast.c:805
#4  0x7f7479e789b7 in impl_thrd_routine (p=) at
/var/tmp/portage/media-libs/mesa-11.1.0/work/mesa-11.1.0/include/c11/threads_posix.h:87
#5  0x7f7520834434 in start_thread (arg=0x7f7470bc2700) at
pthread_create.c:333
#6  0x7f7520d348fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7f74713c3700 (LWP 18781)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f7479e78de3 in cnd_wait (mtx=0x13d53d0, cond=) at
/var/tmp/portage/media-libs/mesa-11.1.0/work/mesa-11.1.0/include/c11/threads_posix.h:159
#2  pipe_semaphore_wait (sema=0x13d53d0) at
/var/tmp/portage/media-libs/mesa-11.1.0/work/mesa-11.1.0/src/gallium/auxiliary/os/os_thread.h:259
#3  thread_function (init_data=init_data@entry=0x13d5328) at
/var/tmp/portage/media-libs/mesa-11.1.0/work/mesa-11.1.0/src/gallium/drivers/llvmpipe/lp_rast.c:805
#4  0x7f7479e789b7 in impl_thrd_routine (p=) at
/var/tmp/portage/media-libs/mesa-11.1.0/work/mesa-11.1.0/include/c11/threads_posix.h:87
#5  0x7f7520834434 in start_thread (arg=0x7f74713c3700) at
pthread_create.c:333
#6  0x7f7520d348fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7f7471bc4700 (LWP 18780)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f7479e78de3 in cnd_wait (mtx=0x13d5268, cond=) at
/var/tmp/portage/media-libs/mesa-11.1.0/work/mesa-11.1.0/include/c11/threads_posix.h:159
#2  pipe_semaphore_wait (sema=0x13d5268) at
/var/tmp/portage/media-libs/mesa-11.1.0/work/mesa-11.1.0/src/gallium/auxiliary/os/os_thread.h:259
#3  thread_function (init_data=init_data@entry=0x13d51c0) at
/var/tmp/portage/media-libs/mesa-11.1.0/work/mesa-11.1.0/src/gallium/drivers/llvmpipe/lp_rast.c:805
#4  0x7f7479e789b7 in impl_thrd_routine (p=) at
/var/tmp/portage/media-libs/mesa-11.1.0/work/mesa-11.1.0/include/c11/threads_posix.h:87
#5  0x7

[kwin] [Bug 317765] dangeling pointer in unconstrained_stacking_order, strongly related to tabbox and NO compositing

[awilfox]

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

A. Wilcox (awilfox) <awil...@adelielinux.org> changed:

   What|Removed |Added

 CC||awil...@adelielinux.org

--- Comment #51 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
Created attachment 100443
  --> https://bugs.kde.org/attachment.cgi?id=100443=edit
KWin support information for KWin 5.7

This happened to me when using alt+tab, with no compositing, when a
notification appeared and disappeared while using alt+tab (I was highlighted in
WeeChat which uses notify-send to tell me).

KWin Support Information: attached

Backtrace of the crash I experienced:

Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7740287800 (LWP 3518))]

Thread 7 (Thread 0x7f76866fe700 (LWP 3655)):
#0  0x7f773dafcaa9 in QEventDispatcherUNIXPrivate::doSelect
(this=0x7f7688c0, flags=..., timeout=0x0) at
kernel/qeventdispatcher_unix.cpp:186
#1  0x7f773dafdb9d in QEventDispatcherUNIX::processEvents
(this=0x7f76800c20b0, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#2  0x7f773daaf001 in QEventLoop::processEvents (flags=..., this=) at kernel/qeventloop.cpp:128
#3  QEventLoop::exec (this=0x7f76866fddd0, flags=...) at
kernel/qeventloop.cpp:204
#4  0x7f773d9045e9 in QThread::exec (this=) at
thread/qthread.cpp:500
#5  0x7f77384babf6 in QQmlThreadPrivate::run (this=0x16d7210) at
qml/ftw/qqmlthread.cpp:141
#6  0x7f773d907d24 in QThreadPrivate::start (arg=0x16d7210) at
thread/qthread_unix.cpp:341
#7  0x7f773fe09434 in start_thread (arg=0x7f76866fe700) at
pthread_create.c:333
#8  0x7f773fb508fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f7707fff700 (LWP 3603)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f773ccfaeaa in QTWTF::TCMalloc_PageHeap::scavengerThread
(this=0x7f773cddd820 ) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x7f773ccfae26 in QTWTF::TCMalloc_PageHeap::runScavengerThread
(context=0x7f773cdeb8f4 <QTWTF::pageheap_memory+57556>) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x7f773fe09434 in start_thread (arg=0x7f7707fff700) at
pthread_create.c:333
#4  0x7f773fb508fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f770d979700 (LWP 3582)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f7713242bb3 in cnd_wait (mtx=0xec83f0, cond=) at
/var/tmp/portage/media-libs/mesa-11.1.0/work/mesa-11.1.0/include/c11/threads_posix.h:159
#2  pipe_semaphore_wait (sema=0xec83f0) at
/var/tmp/portage/media-libs/mesa-11.1.0/work/mesa-11.1.0/src/gallium/auxiliary/os/os_thread.h:259
#3  radeon_drm_cs_emit_ioctl (param=param@entry=0xec80a0) at
/var/tmp/portage/media-libs/mesa-11.1.0/work/mesa-11.1.0/src/gallium/winsys/radeon/drm/radeon_drm_winsys.c:653
#4  0x7f7713242307 in impl_thrd_routine (p=) at
/var/tmp/portage/media-libs/mesa-11.1.0/work/mesa-11.1.0/include/c11/threads_posix.h:87
#5  0x7f773fe09434 in start_thread (arg=0x7f770d979700) at
pthread_create.c:333
#6  0x7f773fb508fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f7720d5f700 (LWP 3568)):
#0  0x7f773dafcaac in QEventDispatcherUNIXPrivate::doSelect
(this=0x7f77180008e0, flags=..., timeout=0x0) at
kernel/qeventdispatcher_unix.cpp:186
#1  0x7f773dafdb9d in QEventDispatcherUNIX::processEvents
(this=0x7f77180008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#2  0x7f773daaf001 in QEventLoop::processEvents (flags=..., this=) at kernel/qeventloop.cpp:128
#3  QEventLoop::exec (this=0x7f7720d5edd0, flags=...) at
kernel/qeventloop.cpp:204
#4  0x7f773d9045e9 in QThread::exec (this=) at
thread/qthread.cpp:500
#5  0x7f77384babf6 in QQmlThreadPrivate::run (this=0xda2cd0) at
qml/ftw/qqmlthread.cpp:141
#6  0x7f773d907d24 in QThreadPrivate::start (arg=0xda2cd0) at
thread/qthread_unix.cpp:341
#7  0x7f773fe09434 in start_thread (arg=0x7f7720d5f700) at
pthread_create.c:333
#8  0x7f773fb508fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f7722e56700 (LWP 3562)):
#0  0x7f773fb49503 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f773dafbf74 in qt_safe_select (nfds=8, fdread=0x7f771c000a78,
fdwrite=0x7f771c000d08, fdexcept=0x7f771c000f98, orig_timeout=)
at kernel/qcore_unix.cpp:75
#2  0x7f773dafcb0b in QEventDispatcherUNIXPrivate::doSelect
(this=0x7f771c0008e0, flags=..., timeout=0x0) at
kernel/qeventdispatcher_unix.cpp:192
#3  0x7f773dafdb9d in QEventDispatcherUNIX::processEvents
(this=0x7f771c0008c0, flags=...) at kernel/qeventdispatcher_unix

[frameworks-kwayland] [Bug 365934] KWayland can't build under strict POSIX systems: uid_t, gid_t undeclared

[awilfox]

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

--- Comment #3 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
I appreciate your scepticism, however, I can't really test this patch on
FreeBSD...

root@renton:~/kwayland-5.5.5/build # uname -a
FreeBSD renton.foxkit.us 10.2-RELEASE-p9 FreeBSD 10.2-RELEASE-p9 #0: Thu Jan 14
01:32:46 UTC 2016
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
root@renton:~/kwayland-5.5.5/build # gmake
[  1%] Automatic moc for target KF5WaylandClient
[  1%] Built target KF5WaylandClient_automoc
[  1%] Building CXX object
src/client/CMakeFiles/KF5WaylandClient.dir/fakeinput.cpp.o
/root/kwayland-5.5.5/src/client/fakeinput.cpp:27:10: fatal error:
'linux/input.h' file not found
#include 
 ^
1 error generated.

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

[frameworks-kwayland] [Bug 365934] New: KWayland can't build under strict POSIX systems: uid_t, gid_t undeclared

[awilfox]

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

Bug ID: 365934
   Summary: KWayland can't build under strict POSIX systems:
uid_t, gid_t undeclared
   Product: frameworks-kwayland
   Version: 5.5.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: mgraess...@kde.org
  Reporter: awil...@adelielinux.org

uid_t, gid_t, and pid_t are defined in either  or  under
POSIX.

This becomes relevant on strictly compliant systems such as the musl libc, and
will continue to be a problem in the future as more C libraries clean up their
headers.  I have personally chosen to #include  in
clientconnection.h, but  is also valid.

Reproducible: Always

Steps to Reproduce:
1. Use a strictly conformant POSIX system (such as musl libc).
2. Attempt to build KWayland.

Actual Results:  
/usr/src/kde-frameworks/kwayland-5.5.5/work/kwayland-5.5.5/src/server/clientconnection.h:100:5:
error: ‘uid_t’ does not name a type
 uid_t userId() const;
 ^
/usr/src/kde-frameworks/kwayland-5.5.5/work/kwayland-5.5.5/src/server/clientconnection.h:109:5:
error: ‘gid_t’ does not name a type
 gid_t groupId() const;
 ^

Expected Results:  
Successful build.

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

[frameworks-kwayland] [Bug 365934] KWayland can't build under strict POSIX systems: uid_t, gid_t undeclared

[awilfox]

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

--- Comment #1 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
Created attachment 100229
  --> https://bugs.kde.org/attachment.cgi?id=100229=edit
Add #include  to clientconnection.h

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

[frameworks-kio] [Bug 365925] New: KIO KPAC fails to build on musl libc: _BSD_SOURCE or _GNU_SOURCE needs to be defined

[awilfox]

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

Bug ID: 365925
   Summary: KIO KPAC fails to build on musl libc: _BSD_SOURCE or
_GNU_SOURCE needs to be defined
   Product: frameworks-kio
   Version: 5.24.0
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: fa...@kde.org
  Reporter: awil...@adelielinux.org
CC: kdelibs-b...@kde.org

The proxy autoconfiguration portion of KIO fails to build against the musl libc
due to _BSD_SOURCE and _GNU_SOURCE both being undefined.  This causes the
symbol 'setgroups' to be hidden as it is not specified in POSIX.1-2008.  It
also causes NI_MAXHOST and IFF_LOOPBACK to be undefined.

I suggest adding a check for setgroups to ConfigureChecks.cmake in the kpac/
directory and defining _BSD_SOURCE if it is not available, but that is just a
suggestion.  I am not sure the desired style in the KIO project.

Reproducible: Always

Steps to Reproduce:
1. Use musl libc.
2. Attempt to build KIO's proxy autoconfiguration support.

Actual Results:  
/usr/src/kde-frameworks/kio-5.21.0/work/kio-5.21.0/src/kpac/kpac_dhcp_helper.c:
In function ‘set_gid’:
/usr/src/kde-frameworks/kio-5.21.0/work/kio-5.21.0/src/kpac/kpac_dhcp_helper.c:59:9:
error: implicit declaration of function ‘setgroups’
[-Werror=implicit-function-declaration]
 if (setgroups(1, ) == -1) {
 ^
/usr/src/kde-frameworks/kio-5.21.0/work/kio-5.21.0/src/kpac/kpac_dhcp_helper.c:
In function ‘send_request’:
/usr/src/kde-frameworks/kio-5.21.0/work/kio-5.21.0/src/kpac/kpac_dhcp_helper.c:173:19:
error: ‘NI_MAXHOST’ undeclared (first use in this function)
 char hostname[NI_MAXHOST];
   ^
/usr/src/kde-frameworks/kio-5.21.0/work/kio-5.21.0/src/kpac/kpac_dhcp_helper.c:173:19:
note: each undeclared identifier is reported only once for each function it
appears in
/usr/src/kde-frameworks/kio-5.21.0/work/kio-5.21.0/src/kpac/kpac_dhcp_helper.c:186:30:
error: ‘IFF_LOOPBACK’ undeclared (first use in this function)
 if (ifa->ifa_flags & IFF_LOOPBACK) {
  ^

Expected Results:  
Successful build.

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

[frameworks-solid] [Bug 365923] Solid udisks2 backend fails to compile on musl libc: dev_t requires sys/types.h

[awilfox]

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

--- Comment #1 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
Created attachment 100224
  --> https://bugs.kde.org/attachment.cgi?id=100224=edit
Add #include  to udisksblock.h

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

[frameworks-solid] [Bug 365923] New: Solid udisks2 backend fails to compile on musl libc: dev_t requires sys/types.h

[awilfox]

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

Bug ID: 365923
   Summary: Solid udisks2 backend fails to compile on musl libc:
dev_t requires sys/types.h
   Product: frameworks-solid
   Version: 5.24.0
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: lu...@kde.org
  Reporter: awil...@adelielinux.org
CC: kdelibs-b...@kde.org

The udisks2 backend of the Solid framework does not #include ,
which causes a compile-time error on the musl libc where dev_t is not defined
in other headers.

A patch is included that has solved this issue for us at Adélie Linux.

Reproducible: Always

Steps to Reproduce:
1. Use musl libc.
2. Attempt to build Solid.

Actual Results:  
In file included from
/usr/src/kde-frameworks/solid-5.21.0/work/solid-5.21.0/src/solid/devices/backends/udisks2/udisksdevice.cpp:24:0:
/usr/src/kde-frameworks/solid-5.21.0/work/solid-5.21.0/src/solid/devices/backends/udisks2/udisksblock.h:48:5:
error: ‘dev_t’ does not name a type
 dev_t m_devNum;
 ^

Expected Results:  
A successful build.

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

[frameworks-ki18n] [Bug 365917] ki18n fails to link on musl libc due to _nl_msg_cat_cntr

[awilfox]

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

--- Comment #1 from A. Wilcox (awilfox) <awil...@adelielinux.org> ---
Created attachment 100223
  --> https://bugs.kde.org/attachment.cgi?id=100223=edit
Patch to ki18n to check for presence of _nl_msg_cat_cntr before using it

I cannot upload to Gerrit using my KDE Identity account (awilcox) so I am
submitting the patch here.  This patch allows ki18n (tested on 5.21.0, 5.24.0,
and master) to build on both glibc (using _nl_msg_cat_cntr) and musl (without
using _nl_msg_cat_cntr).

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

[frameworks-ki18n] [Bug 365917] New: ki18n fails to link on musl libc due to _nl_msg_cat_cntr

[awilfox]

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

Bug ID: 365917
   Summary: ki18n fails to link on musl libc due to
_nl_msg_cat_cntr
   Product: frameworks-ki18n
   Version: 5.24.0
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: caslav.i...@gmx.net
  Reporter: awil...@adelielinux.org
CC: kdelibs-b...@kde.org

We're trying to package KDE Plasma 5 for our new distribution Adélie Linux,
based on the musl libc.  The musl libc provides libintl (similar to glibc) but
does not use the same internals, so even though we are using the GNU gettext
(__USE_GNU_GETTEXT = 1), the libintl included with the libc does not define
_nl_msg_cat_cntr (nor does it need it).

There is no preprocessor definition for musl (as it is an attempt to be a
strictly compliant POSIX C library - see
http://wiki.musl-libc.org/wiki/FAQ#Q:_why_is_there_no_MUSL_macro_.3F for info)
so it should likely be a CMake test to determine if the symbol is available.

Reproducible: Always

Steps to Reproduce:
1. Use musl libc.
2. Attempt to build ki18n.


Actual Results:  
/usr/src/kde-frameworks/ki18n-5.24.0/work/ki18n-5.24.0/src/kcatalog.cpp:177:
undefined reference to `_nl_msg_cat_cntr'

Expected Results:  
Successful build.

Relevant configure output:

-- Looking for __GLIBC__
-- Looking for __GLIBC__ - not found
-- Performing Test _OFFT_IS_64BIT
-- Performing Test _OFFT_IS_64BIT - Success
-- Looking for dngettext
-- Looking for dngettext - found
-- libintl is part of libc, no extra library is required.
-- Found LibIntl: /usr/include  
-- Found Gettext: /usr/bin/msgmerge (found version "0.19.7") 


Relevant build log output:

CMakeFiles/KF5I18n.dir/kcatalog.cpp.o: In function
`KCatalogPrivate::setupGettextEnv()':
/usr/src/kde-frameworks/ki18n-5.24.0/work/ki18n-5.24.0/src/kcatalog.cpp:177:
undefined reference to `_nl_msg_cat_cntr'
collect2: error: ld returned 1 exit status
src/CMakeFiles/KF5I18n.dir/build.make:276: recipe for target
'src/libKF5I18n.so.5.24.0' failed

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

[konsole] [Bug 364285] New: Konsole crashes when saving output from closing tab

[awilfox]

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

Bug ID: 364285
   Summary: Konsole crashes when saving output from closing tab
   Product: konsole
   Version: 16.04.1
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: awil...@wilcox-tech.com

Application: konsole (16.04.1)
 (Compiled from sources)
Qt Version: 5.6.0
Frameworks Version: 5.22.0
Operating System: Linux 4.7.0-rc1-ciall x86_64
Distribution (Platform): Gentoo Packages

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

I fat-fingered Ctrl+Shift+S as Ctrl+Shift+S and D.  The tab closed but the save
output dialogue still opened.  When I chose Save in the dialogue after typing a
name, this crash occurred.

The crash can be reproduced every time.

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f73b9460800 (LWP 3797))]

Thread 4 (Thread 0x7f73a767a700 (LWP 3798)):
#0  0x7f73b59e75e8 in
std::__atomic_base::compare_exchange_strong
(__m1=std::memory_order_release, __m2=std::memory_order_relaxed,
this=, __p1=, __p2=) at
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.3/include/g++-v4/bits/atomic_base.h:848
#1  std::atomic::compare_exchange_strong
(__m=std::memory_order_release, this=, __p1=,
__p2=) at
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.3/include/g++-v4/atomic:448
#2  QAtomicOps::testAndSetRelease (_q_value=...,
expectedValue=, newValue=,
currentValue=) at
../../include/QtCore/../../src/corelib/arch/qatomic_cxx11.h:167
#3  QBasicAtomicPointer::testAndSetRelease (this=,
expectedValue=, newValue=,
currentValue=) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:278
#4  QBasicMutex::fastTryUnlock (this=, current=)
at ../../include/QtCore/../../src/corelib/thread/qmutex.h:85
#5  QMutex::unlock (this=0x8a2288) at thread/qmutex.cpp:271
#6  0x7f73b5be44c1 in QMutexLocker::unlock (this=) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:138
#7  QMutexLocker::~QMutexLocker (this=) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:132
#8  QThreadData::canWaitLocked (this=0x8a2260) at
../../include/QtCore/5.6.0/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:249
#9  postEventSourcePrepare (s=0x7f73a0003200, timeout=) at
kernel/qeventdispatcher_glib.cpp:253
#10 0x7f73b010860b in g_main_context_prepare (context=,
priority=) at
/var/tmp/portage/dev-libs/glib-2.48.0-r1/work/glib-2.48.0/glib/gmain.c:3442
#11 0x7f73b0108f18 in g_main_context_iterate (context=,
block=, dispatch=, self=) at
/var/tmp/portage/dev-libs/glib-2.48.0-r1/work/glib-2.48.0/glib/gmain.c:3820
#12 0x7f73b01090ae in g_main_context_iteration (context=,
may_block=1) at
/var/tmp/portage/dev-libs/glib-2.48.0-r1/work/glib-2.48.0/glib/gmain.c:3901
#13 0x7f73b5be40dc in QEventDispatcherGlib::processEvents
(this=0x7f73a8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#14 0x7f73b5b92f85 in QEventLoop::processEvents (flags=..., this=) at kernel/qeventloop.cpp:128
#15 QEventLoop::exec (this=0x7f73a7679dc0, flags=...) at
kernel/qeventloop.cpp:204
#16 0x7f73b59e9669 in QThread::exec (this=) at
thread/qthread.cpp:503
#17 0x7f73b9533200 in QDBusConnectionManager::run (this=0x7f73b95944e0
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:181
#18 0x7f73b59ecdb4 in QThreadPrivate::start (arg=0x7f73b95944e0 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:340
#19 0x7f73b1c15434 in start_thread (arg=0x7f73a767a700) at
pthread_create.c:333
#20 0x7f73b8f328fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f73a53b6700 (LWP 3799)):
#0  0x7f73b8f297fd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f73b2037ac2 in poll (__timeout=-1, __nfds=1, __fds=0x7f73a53b5cd0)
at /usr/include/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0x8c2dc0, cond=cond@entry=0x8c2e00,
vector=vector@entry=0x0, count=count@entry=0x0) at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_conn.c:459
#3  0x7f73b203972f in xcb_wait_for_event (c=0x8c2dc0) at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_in.c:693
#4  0x7f73a6ac6d75 in QXcbEventReader::run (this=0x8b4fd0) at
qxcbconnection.cpp:1313
#5  0x7f73b59ecdb4 in QThreadPrivate::start (arg=0x8b4fd0) at
thread/qthread_unix.cpp:340
#6  0x7f73b1c15434 in start_thread (arg=0x7f73a53b6700) at
pthread_create.c:333
#7  0x7f73b8f328fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f7393eeb700 (LWP 3800)):
#0  pthread_cond_wait () at