[kwin] [Bug 377225] kwin crash when saving VirtualBox settings

2017-03-07 Thread Martin Gräßlin
https://bugs.kde.org/show_bug.cgi?id=377225

Martin Gräßlin  changed:

   What|Removed |Added

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

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


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

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

[kwin] [Bug 377225] kwin crash when saving VirtualBox settings

2017-03-07 Thread Ed Greshko
https://bugs.kde.org/show_bug.cgi?id=377225

--- Comment #7 from Ed Greshko  ---
FWIW, I have reviewed the comments of
https://bugs.kde.org/show_bug.cgi?id=363224 and I can confirm that if I block
compositing when starting the VirtualBox manager the crash does not occur while
closing/saving the settings dialog.

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

[kwin] [Bug 377225] kwin crash when saving VirtualBox settings

2017-03-06 Thread Martin Gräßlin
https://bugs.kde.org/show_bug.cgi?id=377225

--- Comment #6 from Martin Gräßlin  ---
Am 2017-03-06 23:49, schrieb Christoph Feck:
> COMMENT # 5 [2] ON BUG 377225 [3] FROM CHRISTOPH FECK
> 
> Martin, do you really need more backtraces?

I'm not seeing to duplicate without knowing that it is truly the same. 
If I get a bug report with lacking debug symbols I all for a newer 
backtrace. In fact I don't even look at the backtrace if it's lacking 
debug symbols.

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

[kwin] [Bug 377225] kwin crash when saving VirtualBox settings

2017-03-06 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=377225

--- Comment #5 from Christoph Feck  ---
Martin, do you really need more backtraces? It is clear that all these
https://bugs.kde.org/buglist.cgi?product=kwin_status=NEEDSINFO=QScriptEngine%3A%3AnewQObject_type=casesubstring
are duplicates of bug 363224.

I suggest to ask reporters for exact steps to reproduce. Additionally, pointing
them to the duplicate allows them to follow what has been investigated so far,
e.g. which effects are causing it.

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

[kwin] [Bug 377225] kwin crash when saving VirtualBox settings

2017-03-04 Thread Ed Greshko
https://bugs.kde.org/show_bug.cgi?id=377225

Ed Greshko  changed:

   What|Removed |Added

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

--- Comment #4 from Ed Greshko  ---
OK  I see I can just change it to "unconfirmed".  Sorry for the noise.

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

[kwin] [Bug 377225] kwin crash when saving VirtualBox settings

2017-03-04 Thread Ed Greshko
https://bugs.kde.org/show_bug.cgi?id=377225

--- Comment #3 from Ed Greshko  ---
I have added the requested backtrace after installing the corresponding
debuginfo package.  

This bugzilla system seems a bit different from fedora's as I don't see a place
to indicate that the status "needsinfo" should be removed.

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

[kwin] [Bug 377225] kwin crash when saving VirtualBox settings

2017-03-04 Thread Ed Greshko
https://bugs.kde.org/show_bug.cgi?id=377225

--- Comment #2 from Ed Greshko  ---
Created attachment 104374
  --> https://bugs.kde.org/attachment.cgi?id=104374=edit
backtrace after installing kwin-debuginfo-5.9.3-1.fc25.x86_64

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

[kwin] [Bug 377225] kwin crash when saving VirtualBox settings

2017-03-04 Thread Martin Gräßlin
https://bugs.kde.org/show_bug.cgi?id=377225

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---
Unfortunately the backtrace is lacking debug symbols. If you are able to 
reproduce please install the debug packages provided by your 
distribution (please ask the distribution support channel on how to 
install them) and attach a new backtrace.

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