Bug 299712

Summary:	Cannot drag & drop sensor onto display panel
Product:	[Unmaintained] ksysguard	Reporter:	Andrew Wasielewski <andrew>
Component:	ksysguard	Assignee:	KSysGuard Developers <ksysguard-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	dkour, ferry.toth, mail, richard.llom, tcaswell, tgheretford
Priority:	NOR
Version First Reported In:	4.8
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Andrew Wasielewski 2012-05-09 22:36:08 UTC

Since upgrading to Fedora 16 I cannot add new sensors to a display by drag & drop from the sensor browser. The mouse cursor changes to a "plus" sign, but nothing happens when I drop the sensor in place - no error message, or anything in syslog. This happens even with an empty display panel - the only way I can add a sensor in GUI is by creating a new display from scratch. Makes no difference which sensor I select.  However existing (pre-F16) multi-sensor displays work fine, and if I edit the .sgrd files directly the sensor is displayed.

This affects all users on the system inc. root, so not profile or permissions related. KDE version is 4.8.2 (package ksysguard-4.7.2-14.fc16.x86_64). 

Reproducible: Always

Steps to Reproduce:
1. Open Ksysguard 
2. Create new display panel and drag & drop sensor from Sensor Browser
3. Try to drag & drop a 2nd sensor
Actual Results:  
2nd sensor wasn't added

Expected Results:  
2nd sensor would be added

Comment 1 Gareth Hart 2012-05-20 01:34:25 UTC

Same thing happens with Ksysguard with KDE 4.8.3 on Arch Linux. Dragging and dropping another sensor onto an existing chart does nothing.

Comment 2 Ferry 2012-05-22 16:27:36 UTC

Same with kubuntu precise (kde 4.8.3)

Ferry

Comment 3 Thomas Caswell 2012-06-12 19:17:37 UTC

I can also confirm on debian sid (4.8.3)

Comment 4 Dmitri 2012-08-10 23:38:02 UTC

Same thing here on Fedora 17 with ksysguard 4.8.4-1.fc17

Comment 5 Julian Steinmann 2018-02-24 14:54:23 UTC

Can anyone still reproduce this bug? Likely that this is now fixed.

Comment 6 Richard Llom 2019-03-11 10:59:29 UTC

Works for me.