Bug 355807 - Dialog to mark report as related does nothing
Summary: Dialog to mark report as related does nothing
Status: RESOLVED FIXED
Alias: None
Product: drkonqi
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
: 356458 356722 356822 357766 360981 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-11-23 19:39 UTC by Elias Probst
Modified: 2019-07-03 12:35 UTC (History)
19 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
ksmserver-20160210-093312.kcrash.txt (4.37 KB, text/plain)
2016-02-12 08:04 UTC, Dennis Schridde
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Elias Probst 2015-11-23 19:39:59 UTC
When using in the "Look for Possible Duplicate Reports" view the following functionality:
→ Open selected report
→ Suggest this crash is related
→ Completely sure: attach my information to this report
→ Continue
absolutely nothing happens. The button just triggers no action at all.

Running latest KF5/P5 from git master + Qt 5.5.1.
Comment 1 Christoph Feck 2015-11-23 22:13:51 UTC
Can you confirm your checkout contains the patch mentioned in bug 354110? If yes, we need to reopen and investigate further.
Comment 2 Elias Probst 2015-11-23 23:05:30 UTC
I can confirm the patch is part of my build (44f61b48b0355d461f40f581b84c5a02cf764e45, ~12h old).
Comment 3 Dennis Schridde 2016-02-12 08:04:27 UTC
Created attachment 97160 [details]
ksmserver-20160210-093312.kcrash.txt

Since I replaced my old, DIV-connected monitor (HannsG HW223D, 1680x1050) with a new one connected via HDMI (LG 29UM67, 2560x1080), ksmserver was crashing whenever the monitor went to standby and later back on. Today is the first time that not ksmserver, but plasmashell (and apparently some others, like kwin_x11 and yakuake) crashed.

I am using Qt 5.5.1, KF 5.18.0, KA 5.12.1, Plasma 5.5.4, Linux 4.4.1, X.Org-Server 1.18.1.
Comment 4 Dennis Schridde 2016-02-12 08:08:27 UTC
(In reply to Dennis Schridde from comment #3)
Sorry, that was the original bugreport, I was trying to create using DrKonqi...

My actual comment on this issue is just a "same here", using Qt 5.5.1, KF 5.18.0, KA 5.12.1, Plasma 5.5.4.
Comment 5 Alexander Potashev 2016-03-21 21:32:35 UTC
*** Bug 356722 has been marked as a duplicate of this bug. ***
Comment 6 Alexander Potashev 2016-03-21 21:34:37 UTC
*** Bug 356822 has been marked as a duplicate of this bug. ***
Comment 7 Alexander Potashev 2016-03-21 21:35:44 UTC
*** Bug 357766 has been marked as a duplicate of this bug. ***
Comment 8 Alexander Potashev 2016-03-21 21:38:38 UTC
*** Bug 356458 has been marked as a duplicate of this bug. ***
Comment 9 Alexander Potashev 2016-03-21 21:40:10 UTC
Possibly introduced in https://commits.kde.org/plasma-workspace/a007f294b4991c6f5730e0ec8d9d20f36e31acab
Comment 10 Ian 2016-04-15 06:27:56 UTC
I can confirm that this is still happening on openSUSE Tumbleweed (20160412) 
KDE Frameworks 5.21.0
Qt 5.5.1 (built against 5.5.1)
Comment 11 Chris Williamson 2016-04-27 20:51:35 UTC
I am also experiencing this issue in Kubuntu 15.10.
Comment 12 Con Kolivas 2016-04-28 12:52:31 UTC
Now experiencing this with Kubuntu 16.04 as well.
Comment 13 OliPro007 2016-05-02 22:34:20 UTC
I'm also experiencing this in a fresh, standard install of Kubuntu 16.04, with the constant random crashes of plasmashell, I cannot join my report to an existing one.
Comment 14 rebug789 2016-12-30 20:54:44 UTC
Similar bug for me if i select "Completely sure: attach my information to this report" and continue and after select next on the primary windows i'm told that i 
have selected nothing.

plasma :5.8.5
kde frameworks :5.29
qt:5.7.1
kernel: 4.8.13-1 Arch 64bits
Comment 15 Christoph Feck 2017-01-30 20:40:34 UTC
*** Bug 360981 has been marked as a duplicate of this bug. ***
Comment 16 sedrubal 2017-01-31 23:37:10 UTC
Same here.

plasma 5.8.5

I think this bug persists for over 1 year and nobody cares. I think this is a very important bug: Because of this there are many (!) duplicates on bugs.kde.org. Bug maintainer always have to close bugs a duplicate which wouldn't have been opened when this feature would work.
Comment 17 Dennis Schridde 2017-07-27 09:58:47 UTC
Also affects KDE neon User LTS.  Perfectly reproducible every time.
Comment 18 Harald Sitter 2019-07-03 12:35:29 UTC
This should be solved in 5.17 (at least; possibly earlier) as part of the backend API rework this was tested and is working as expected.