| Summary: | crash when switching desktops | ||
|---|---|---|---|
| Product: | [Unmaintained] plasma4 | Reporter: | kavol <kavol> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | aseigo, asraniel, darktears31 |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
kavol
2010-09-08 10:04:43 UTC
probably also a dupe of: https://bugs.kde.org/show_bug.cgi?id=200847 please post the upstream qt bug number here when you created the bugreport. thank you *** This bug has been marked as a duplicate of bug 245910 *** (In reply to comment #1) > please post the upstream qt bug number here when you created the bugreport. > thank you it is KDE application that crashed for me so it is KDE bug for me - therefore I won't report bug against Qt, no application from the Qt package crashed for me if aseigo says this is Qt bug then it is upon him to prove that it is not KDE's fault and report the bug against Qt - I won't do his job, I'm not user of Qt, I'm user of KDE, the user of Qt is the developer From the backtrace you can see that the bug happens in qt code. Also it was confirmed by a qt employe that this is a qt bug. Now, i can't reproduce the crash. probably aseigo neither. So only somebody that can reproduce it can submit it to qt. I do agree that this is an old bug and it seems like quite a lot of people are affected. But that does not change the fact that it is a qt bug and that kde can do nothing about it. So, instead of investing your time in reopening the bug here, please submit a bug to the qt bugtracker. thank you. *** This bug has been marked as a duplicate of bug 245910 *** (In reply to comment #3) > From the backtrace you can see that the bug happens in qt code. what I can see is that the Qt code is called from *KDE code* > Also it was confirmed by a qt employe that this is a qt bug. that's nice, but insufficient - some informal talk cannot replace a record in a bugtracker you can refer to > Now, i can't reproduce the crash. probably aseigo neither. me neither however, the trace & the other bugreport proves that the problem exists > So only somebody that can reproduce it can submit it to qt. please do not lie to me http://qt.nokia.com/developer/task-tracker/qt-bug-tracker-getting-started#3-creating-a-new - no mention that you *have to* be able to reproduce something in order to be allowed to report it > I do agree that this is an old bug and it seems like quite a lot of people are > affected. But that does not change the fact that it is a qt bug and that kde > can do nothing about it. once again, please DO NOT LIE TO ME there's plenty of options what KDE can do about the bug - and you can start with tracking it properly > So, instead of investing your time in reopening the bug here, please submit a > bug to the qt bugtracker. thank you. ah, but your time is better invested in telling users that you can't do anything rather than actually doing the job and processing the bug in the way that you move it towards getting resolved, ok :-) http://bugreports.qt.nokia.com/browse/QTBUG-13507 (In reply to comment #3) > From the backtrace you can see that the bug happens in qt code. > Also it was confirmed by a qt employe that this is a qt bug. I wonder who? Not me...This bug has some duplicates so perhaps it's a real bug BUT i can't reproduce and I tried many times. Unless someone gives me more help/info there is nothing i can do really. I need a testcase or at least the exact way of reproducing it...I've never have that crash so I can't fix it even though i want...Could someone try 4.7.0? > > Now, i can't reproduce the crash. probably aseigo neither. > So only somebody that can reproduce it can submit it to qt. > > I do agree that this is an old bug and it seems like quite a lot of people are > affected. But that does not change the fact that it is a qt bug and that kde > can do nothing about it. > > So, instead of investing your time in reopening the bug here, please submit a > bug to the qt bugtracker. thank you. > > *** This bug has been marked as a duplicate of bug 245910 *** Kavol,
"what I can see is that the Qt code is called from *KDE code*"
the only KDE code in the backtrace is KApplication::notify, which simply hands it off to QApplication::notify. there is no KDE code being executed here.
even if there were, we call functions in all kinds of libraries / processes. if we trigger a bug in the linux kernel, should we file the linux kernel bug here on bugs.kde.org? x.org bugs? etc...
of course not.
"the trace & the other bugreport proves that the problem exists"
no one is disputing that; we just can't solve it in the KDE code because the bug isn't there. it's not even something we could work around if we wanted to. note that this bug tracker is for issues in the KDE code base.
after that, you start stepping over the line:
"please do not lie to me"
"once again, please DO NOT LIE TO ME"
"ah, but your time is better invested in telling users that you can't do
anything rather than actually doing the job and processing the bug in the way
that you move it towards getting resolved, ok"
Beat was trying to help you and was actually doing exactly the right thing. It is not within our ability to report every bug to every upstream that you find. That is something we rely on our users to help us with. We just don't have the manpower to do otherwise, and I don't see anyone paying someone to do such between project reporting either. Maybe that's unfortunate, but it's the way it is and we in KDE are doing the best we can.
That does not justify you calling someone a liar, twice ("screaming" the second time) or making snide remarks. If you are unsure about the behavior that we expect from each other, you may consult the KDE Code of Conduct:
http://www.kde.org/code-of-conduct/
In future, please be more collaborative and less abusive of those who are doing good work that we all rely on. Thanks.
(In reply to comment #5) > Could someone try 4.7.0? I've tried to recompile SRPM taken from this build: http://koji.fedoraproject.org/koji/buildinfo?buildID=194333 on my system and update (hope that won't break my system any further) we'll see if the problem reappears ... |