Bug 21893 - krename does not exit
Summary: krename does not exit
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA6-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2017-10-19 00:18 CEST by Mészáros Csaba
Modified: 2019-05-19 15:37 CEST (History)
8 users (show)

See Also:
Source RPM: krename-4.0.9-10.mga6
CVE:
Status comment:


Attachments

Description Mészáros Csaba 2017-10-19 00:18:28 CEST
Description of problem:

krename does not exit. The window closes, but the background runs there as often as you open it.
When the machine is restarted, all krename windows are displayed.

Version-Release number of selected component (if applicable):
krename-4.0.9-10.mga6

How reproducible:
100%

Steps to Reproduce:
1. open krusader
2. select the files
3. Shift F9 - open the krename and use
4. open konsole: ps aux | grep krename

Dirty workaround
1. open konsole: killall krename

But still visible:

open the konsole: ps aux | grep krename
 
file.so [kdeinit5] file local:/run/user/10001/klauncherTJ5161.1.slave-socket local:/run/user/10001/krenametK6131.1.slave-socket
Mészáros Csaba 2017-10-19 00:18:43 CEST

CC: (none) => pingvin

Marja Van Waes 2017-10-21 18:06:38 CEST

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

Comment 1 Marja Van Waes 2017-10-27 19:58:58 CEST
Mass-change status to NEW for all bugs that were filed as UNCONFIRMED between October 9 and now, and that still have that status now.

From now on all newly filed bugs will have the NEW status again, like before, regardless of who files the report.

Ever confirmed: 0 => 1
Status: UNCONFIRMED => NEW

Comment 2 Mészáros Csaba 2018-10-08 22:58:27 CEST
The problem is still present. :( (one year)
Comment 3 Cesar Vargas 2018-10-10 19:11:20 CEST
Could you give us more information please?
gdb, strace, etc.

CC: (none) => cvargas

Comment 4 Mészáros Csaba 2018-10-10 21:35:40 CEST
Hi 
The file size has big (11M), so here is the link where it is available.
https://app.box.com/s/1guzw4y72wfs5lxaf1onlumg5gpmkl1w

Thanks. Csaba
Comment 5 David GEIGER 2019-02-18 11:50:48 CET
Is this still valid with krename 5.0.0 in mga6?

CC: (none) => geiger.david68210

Comment 6 Mészáros Csaba 2019-02-18 23:42:06 CET
Ooohhh yes... after starting twice in ps.aux are present 9 krename word.
Comment 7 Yuri Galitsky 2019-05-06 15:23:37 CEST
This bug is still valid in mga7 beta3.
Seems it's related bug and this fixed in git.
https://bugs.kde.org/show_bug.cgi?id=395084

CC: (none) => ugal12v

Comment 8 David GEIGER 2019-05-06 15:50:55 CEST
Thanks for the upstream fixes!

So done for cauldron and also for mga6 in Core/Updates_testing repo.

Please test if now issue is fixed, thanks in advance!
Comment 9 Yuri Galitsky 2019-05-07 15:44:04 CEST
krename-5.0.0-7.mga7.x86_64.rpm package tested. Now it's working without any issues for me.
Comment 10 David GEIGER 2019-05-08 04:32:11 CEST
Assigning to QA now,


Advisory:
========================

Current krename don't close properly when the progress dialog is closed.
So this update fixes this issue.

========================

Packages in 6/core/updates_testing:
========================
krename-5.0.0-1.1.mga6.x86_64.rpm
krename-5.0.0-1.1.mga6.i586.rpm

Source RPM: 
========================
krename-5.0.0-1.1.mga6.src.rpm

Assignee: kde => qa-bugs
Hardware: x86_64 => All

Comment 11 PC LX 2019-05-10 18:35:45 CEST
Installed and tested without issues.

System: Mageia 6, x86_64, Plasma DE, LXQt DE, Intel CPU, nVidia GPU using nvidia340 proprietary driver.

No problems with closing krename. Closing krename does not leave any running processes. General usage seems OK. No regressions noticed.

$ uname -a 
Linux marte 4.14.116-desktop-1.mga6 #1 SMP Sat May 4 08:34:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
$ rpm -q krename
krename-5.0.0-1.1.mga6

Whiteboard: (none) => MGA6-64-OK
CC: (none) => mageia

Comment 12 Dave Hodgins 2019-05-19 09:31:49 CEST
Advisory committed to svn. Validating the update.

Keywords: (none) => advisory, validated_update
CC: (none) => davidwhodgins, sysadmin-bugs

Comment 13 Mészáros Csaba 2019-05-19 10:47:13 CEST
Hello PC LX!

I don't know if you checked it, but I still have the problem.
1 - Krusader opens
2 - Select files
3 - Push Shift F9
4 - Rename files
5 - Close the Krename window
Result: The krename window closes.
6 - Logout, or reboot
7 - The krename window is displayed in as many copies as it was previously called.

****************
$ cat /etc/release 
Mageia release 6 (Official) for x86_64

$ rpm -qa | grep task | grep plasma
task-plasma5-minimal-5.12.2-1.mga6 - (This the problem? Only minimal.)

$ rpm -qa | grep nvidia | grep driver
x11-driver-video-nvidia-current-390.87-1.mga6.nonfree

$ rpm -q krename
krename-5.0.0-1.mga6

$ uname -a
Linux csablakPC.home 4.14.106-desktop-1.mga6 #1 SMP Thu Mar 14 18:01:29 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

$ date
2019. máj. 19., vasárnap, 10.36.13 CEST

Unfortunately this is.
I've been using the double commander ever since.
Because Krusader also freezes when I press * (select files). But I have also announced this: 
https://bugs.mageia.org/show_bug.cgi?id=22353 (2018-Jan-09)

Regards: Csaba
Comment 14 David GEIGER 2019-05-19 11:00:21 CEST
(In reply to Mészáros Csaba from comment #13)
> 
> $ rpm -q krename
> krename-5.0.0-1.mga6
> 

You have to install krename-5.0.0-1.1.mga6 (not krename-5.0.0-1.mga6) from Updates_testing repo!
Comment 15 Dave Hodgins 2019-05-19 12:45:12 CEST
The update has been validated, so it will be moved from the updates testing
repo to updates soon, by one of the sysadmins.
Comment 16 Mageia Robot 2019-05-19 13:28:36 CEST
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2019-0035.html

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

Comment 17 Mészáros Csaba 2019-05-19 15:37:09 CEST
I upgraded.
juhéé !!
It's the boys. So it's good. It works. Thanks.
Now, only the Krusader freezing should be remedied. :)

Regards. Csaba

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