Bug 14737 - 4: k3b not saving sub directory files.
Summary: 4: k3b not saving sub directory files.
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Juan Luis Baptiste
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-06 05:58 CET by Bit Twister
Modified: 2015-09-23 11:47 CEST (History)
0 users

See Also:
Source RPM: k3b-2.0.3a-2.mga5.tainted.src.rpm
CVE:
Status comment:


Attachments

Description Bit Twister 2014-12-06 05:58:04 CET
Description of problem:

k3b not saving sub directory files. Example: look at
 ls $HOME/.config/akonadi/*
Those are not being saved when you try to save/burn /home/$USER.

problem also exists in Cauldron

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


How reproducible: always


Steps to Reproduce:
1. click up a terminal and run
2.   k3b &
3. close first time useage popups.
4. left click blue navigation uparrow 1 time
   at this point you should see your home directory in top right panel.

5. left click New Data Project (bottom panel)
6. left click drag your home folder from top right panel to bottom right panel
7. click Add to add hidden files? popup
8. click Cancel to Adding link to folder popup
9. Double click your folder icon in bottom right panel
   Look at the bottom right panel.
   Those files will be saved.

10. Double click .config folder icon
11. Double click akonadi folder icon

NOTE: no $HOME/.config/akonadi/* files will be saved.  :(

Over in the terminal run
12.  ls $HOME/.config/akonadi/*

Those files should have been seen in K3b bottom right panel.


Reproducible: 

Steps to Reproduce:
David Walser 2014-12-10 22:08:29 CET

Assignee: bugsquad => juan.baptiste

Comment 1 Bit Twister 2015-04-28 00:42:52 CEST
k3b-2.0.3a-2.mga5.tainted did not copy my ~/.config but did copy my ~/.cron.

Source RPM: k3b-2.0.2-12.mga4.tainted.src.rpm => k3b-2.0.3a-2.mga5.tainted.src.rpm

Comment 2 Samuel Verschelde 2015-09-21 13:18:04 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Comment 3 Bit Twister 2015-09-23 11:47:32 CEST
Works in mga 5

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


Note You need to log in before you can comment on or make changes to this bug.