Description of problem: I start isodumper as normal user, enter root pwd, have it write the USB stick, and when i click [close] nothing seem to happen, but it in the terminal from where I started it it prints: Traceback (most recent call last): File "/usr/lib/isodumper/isodumper.py", line 456, in confirm_close self.close('dummy') File "/usr/lib/isodumper/isodumper.py", line 489, in close self.write_logfile() File "/usr/lib/isodumper/isodumper.py", line 508, in write_logfile logfile=open(logpath+'/isodumper.log',"w") When click the window frame close button it outputs: (isodumper.py:24148): Gtk-WARNING **: Failed to read filechooser settings from "/root/.config/gtk-2.0/gtkfilechooser.ini": Ãtkomst nekas ( "Ãtkomst nekas" = "Access denied" ) and the window disappears, but still the processes runs: isodumper - owned by root, and isodumper.py - owned by normal user. i close isodumper.py and the other go away too. Exactly the same happens when i run it as root, with the difference following messages are written out the terminal before writing stick: Error creating proxy: Anslutningen är stängd (g-io-error-quark, 18) Error creating proxy: Anslutningen är stängd (g-io-error-quark, 18) Error creating proxy: Anslutningen är stängd (g-io-error-quark, 18) Error creating proxy: Anslutningen är stängd (g-io-error-quark, 18) Error creating proxy: Anslutningen är stängd (g-io-error-quark, 18) ( "Anslutningen är stängd" = "Connection is closed" ) My system is on-line upgraded from mga4 to mga5 around beta1 Reproducible: Steps to Reproduce:
Assignee: bugsquad => yves.brungard_mageia
Thanks for reporting. The "access denied" is not the subject. The program should be exited at this step. It seems that the log file can not be written. Either the path is erroneous, or the access rights are not allowed. I don't reproduce the problem on my Mageia 4. I will try to install a cauldron.
I don't reproduce the error on a cauldron i586. What is the identifier of your user?
I do not understand "identifier" This machine is a 64bit up to date cauldron - originally mga4, updated online. I will soon try on other cauldron machines too.
using KDE
(In reply to Morgan Leijström from comment #3) > I do not understand "identifier" I mean the name of the user /home/name_of_the_user
Morgan Have you a directory ~/.isodumper created? Is it empty? What is the owner of the directory and eventually of the file isodumper.log?
Morgan, do you have always this problem? I can not do any modifications without your cooperation.
Keywords: (none) => NEEDINFO
Summary: isodumper fail to exit => isodumper crashes while writing log file
Status: NEW => UNCONFIRMEDEver confirmed: 1 => 0
Sorry for the delay, i forgot. On that computer i see i have used isodumper earlier. I do not remember if I noticed a problem then. (system have been upgraded from mga4 and now run cauldron) my /home/username/.isodumper was created 2014-06-09 owner=root, rights rwxr-xr-x contains isodumper.log dated 2014-10-01 owner=root, rights rw-r--r-- When posting this bug isodumper was version 0.32 I have not used isodumper since then. Now i see it is updated to 0.40 Now i remove .isodumper/ and start isodumper as root from terminal Output in terminal is (isodumper.py:28841): Gtk-WARNING **: Kan inte hitta temamotorn i "module_path": "oxygen-gtk", Error creating proxy: Anslutningen är stängd (g-io-error-quark, 18) (two rows of the Gtk-WARNING, five rows of the Error) Weird: While running, it do not create anything in /home/username/ nor in /root/ But when i stop it (it was dead slow, see below) it writes out log in terminal and also creates the folder and logfile in my home. Interesting (and good) it creates it in my normal user home despite i started it as root in a KDE terminal. Same when started as normal user from terminal (only difference is it pops up a dialog to log in as root) Other observations: § The issue this bug was created for i can not replicate :) You choose if we should close this and make a new one or continue here (in that case change the subject line please) However: § writing is very slow! isodumper achieve 1MB/s while dd achieve 6MB/s on the same file and target. It use less than a percent CPU, and speed seem not to be dependent on other system load. § clicking the buttons in bottom of the interface while it is writing '(i.e (i) info or Stop buttons) it takes about ten seconds for the popup to display, and if i try to close it by the (x) it takes so long time that KDE shows a popup question if i want to kill it or wait longer... § "Details" is not clickable when writing have started. It would be nice if that worked. § Detail in log file: there is no space between the word from and source file path. (at least in swedish translation)
Source RPM: isodumper-0.32-1.mga5.src.rpm => isodumper-0.40-1.mga5.src.rpm
More... § I realise it is intended not to write out log file until it finishes, but maybe it would be a good idea if it wrote continously? at least as it does not work to click "details" while it is running. § another missing space between words: when it verifies, there is no space between (the swedish word for) "Checking" and the drive name ("sdc" here) written on the progress bar.
Thanks Morgan. I think you first problem was that .isodumper was owned by root. For writing log file, I need to change the application's owner to the local user. After that, writing in the device is no more possible. This is why the log file is writing at end. What is possible is to write directly on stout. The problems you report seem all linked to the speed of the application. I know that the interface is not very responsive while writing. The same for details. For the missing spaces, can you edit them in transifex. If not, I will ask on i18n list. I will try to have a more responsive behavior. Papoteur
Yes. No idea why it was owned by root, but the current version makes me the owner. It is OK to not write the log until exits. -but can you make "Details" work while operating - or simply make it open as default. (click to close) How come it is six times slower than the dd command? (it takes more than an hour to write a DVD iso to usb stick) I thought it was kind of a wrapper to dd. Or can you make it that? (comment: i used dd with bs=1M) I am not used to transifex, so please forward my translation comments, and ask also to check for missing spaces in other places. Possibly the same mistake have also been made in other languages.
@margan Is your writing classical or for UEFI?
classical
Keywords: NEEDINFO => (none)
Whiteboard: (none) => MGA5TOO
As i have not seen it since, and it was a while ago and no one else comment here, i close it as worksforme. As for the other issues i mention in Comment 11 : it now (v 0.42, mga5) writes quickly, and "Details" work while operating. Thanks :)
Status: UNCONFIRMED => RESOLVEDResolution: (none) => WORKSFORME