[kwin] [Bug 385397] Crash (segfault) on startup at memmove

2017-10-06 Thread Martin Flöser 
https://bugs.kde.org/show_bug.cgi?id=385397

--- Comment #7 from Martin Flöser  ---
(In reply to Martin Flöser from comment #4)
> I'll backport my patch to the 5.11 branch. So will be fixed with 5.11.0

Have to correct that one. 5.11.0 was already tagged, so one week later with
5.11.1

Thanks for the beer offer :-)

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

[kwin] [Bug 385397] Crash (segfault) on startup at memmove

2017-10-06 Thread Mate Soos 
https://bugs.kde.org/show_bug.cgi?id=385397

--- Comment #6 from Mate Soos  ---
Wow, thanks! Great work :) Owe you a beer! Let me know if you are coming to CCC
(34C3) conf. Cheers,

Mate

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

[kwin] [Bug 385397] Crash (segfault) on startup at memmove

2017-10-05 Thread Martin Flöser 
https://bugs.kde.org/show_bug.cgi?id=385397

Martin Flöser  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kwi
   ||n/31b5b7f9f981ccaca001423c1
   ||a2183157bb53356
   Version Fixed In||5.11.1
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #5 from Martin Flöser  ---
Git commit 31b5b7f9f981ccaca001423c1a2183157bb53356 by Martin Flöser.
Committed on 05/10/2017 at 17:34.
Pushed by graesslin into branch 'Plasma/5.11'.

Ensure internal Wayland connection is properly setup before creating LockScreen
integration

With the new Wayland only mode we start too fast and it can happen that
the initWithWorkspace is called before the client connection is fully
setup. This would result in a crash in the idletime plugin once it tries
to create a seat.

To prevent this problem the code is split out into a dedicated method
and only invoked if all interfaces have been announced on the internal
connection.
FIXED-IN: 5.11.1

M  +33   -17   wayland_server.cpp
M  +2-0wayland_server.h

https://commits.kde.org/kwin/31b5b7f9f981ccaca001423c1a2183157bb53356

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

[kwin] [Bug 385397] Crash (segfault) on startup at memmove

2017-10-05 Thread Martin Flöser 
https://bugs.kde.org/show_bug.cgi?id=385397

Martin Flöser  changed:

   What|Removed |Added

  Flags||Wayland+, X11-

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

[kwin] [Bug 385397] Crash (segfault) on startup at memmove

2017-10-05 Thread Martin Flöser 
https://bugs.kde.org/show_bug.cgi?id=385397

--- Comment #4 from Martin Flöser  ---
I'll backport my patch to the 5.11 branch. So will be fixed with 5.11.0

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

[kwin] [Bug 385397] Crash (segfault) on startup at memmove

2017-10-05 Thread Mate Soos 
https://bugs.kde.org/show_bug.cgi?id=385397

--- Comment #3 from Mate Soos  ---
Created attachment 108189
  --> https://bugs.kde.org/attachment.cgi?id=108189=edit
hwinfo output

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

[kwin] [Bug 385397] Crash (segfault) on startup at memmove

2017-10-05 Thread Mate Soos 
https://bugs.kde.org/show_bug.cgi?id=385397

--- Comment #2 from Mate Soos  ---
Cool, thanks for picking this up. I was pretty happy I could run valgrind to be
honest. It's nice trace I think.

Using:

msoos@msoos: pacman -Qs "kwin*"
[...]
local/kwin 5.10.5-1 (plasma)
An easy to use, but flexible, composited Window Manager
local/kwindowsystem 5.37.0-1 (kf5)
Access to the windowing system

It's fairly recently updated Arch Linux, so I shouldn't be too much off. Maybe
1-2 months off but pretty close I think.

Ask away if you want more info :)

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

[kwin] [Bug 385397] Crash (segfault) on startup at memmove

2017-10-05 Thread Martin Flöser 
https://bugs.kde.org/show_bug.cgi?id=385397

--- Comment #1 from Martin Flöser  ---
which exact version are you running? I fixed a crash related to your backtrace
just the other day.

The memmove warnings look like false-positives to me, the invalid read is
directly related to your crash.

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