Bug 20201

Summary:	Unable to add files/folder to new data project in k3b
Product:	Mageia	Reporter:	Bit Twister <bittwister2>
Component:	RPM Packages	Assignee:	KDE maintainers <kde>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	Normal	CC:	geiger.david68210, marja11
Version:	Cauldron	Keywords:	6sta2
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	k3b-2.10.0-3.mga6.tainted.src.rpm	CVE:
Status comment:

Description Bit Twister 2017-01-29 08:14:12 CET

Description of problem: 6_s2

Unable to add files/folder to new data project in k3b.

Version-Release number of selected component (if applicable):


How reproducible: always


Steps to Reproduce:
1. click up a terminal
2. k2b &
3. click New Data Project 
4. click/drag a file from top right to bottom right panel

Note filed did not show up in bottom right panel

5. click/drag a folder/subdir from top left side panel to bottom left panel under K3b data project

Note folder/subdir did not show up in bottom right panel.

Bit Twister 2017-01-29 08:14:32 CET

Status comment: (none) => 6_s2

Marja Van Waes 2017-01-29 10:07:58 CET

CC: (none) => marja11
Assignee: bugsquad => kde

David Walser 2017-01-29 18:04:39 CET

Keywords: (none) => 6sta2
Status comment: 6_s2 => (none)

Comment 1 Bit Twister 2017-01-29 23:04:30 CET

@ David Walser <luigi@....>   and anyone else.

Please leave the Status comment: field alone. Since no one else is using the field I am using it to indicate the last release/phase/version that I have tested that the bug is still valid.

It can also save time for whoever is checking old bugs and asking to see if the problem still exists. 

Since you modified the Keyword field with phase/version would you care to share the rationality/reason for setting that field.

What is going to be the rule for modifying phase/version keyword value during the bugs lifetime?

Status comment: (none) => 6_s2

Bit Twister 2017-01-31 18:32:53 CET

Status comment: 6_s2 => (none)

Comment 2 David GEIGER 2017-02-12 13:06:43 CET

Thanks for the report :)

This bug was already reported upstream and fixed:

https://bugs.kde.org/show_bug.cgi?id=375016


Should be fixed in next k3b update!

- k3b-2.10.0-4.mga6

CC: (none) => geiger.david68210

Comment 3 Bit Twister 2017-02-12 15:26:05 CET

Works for me.

Status: NEW => RESOLVED
Resolution: (none) => FIXED