Bug 32310

Its weird the application should ask for rights , it happens?

Español:

Miguel, a tu reporte le faltan detalles , ¿que es exactamente lo que estabas haciendo?
Me parece que estabas intentando hacer algo en el asistente de particionado, pero ya que no lo especificas solo adivino.
Si el idioma es problema puedo ayudarte, solo trata de expresarte claramente y yo traduciré.

English
Miguel, your report lack of details, what is exactly what you was doing?
I think you was trying to make something with the wizard for disk partition, but i just guess. 
If language is a issue i can help, just try be clear and i make the translation

Status: NEW => NEEDINFO

(In reply to katnatek from comment #2)
> Español:
> 
> Miguel, a tu reporte le faltan detalles , ¿que es exactamente lo que estabas
> haciendo?
> Me parece que estabas intentando hacer algo en el asistente de particionado,
> pero ya que no lo especificas solo adivino.
> Si el idioma es problema puedo ayudarte, solo trata de expresarte claramente
> y yo traduciré.
> 
> English
> Miguel, your report lack of details, what is exactly what you was doing?
> I think you was trying to make something with the wizard for disk partition,
> but i just guess. 
> If language is a issue i can help, just try be clear and i make the
> translation

Disculpen por la falta de información, es el primer reporte qué realizo entonces seguro se me han pasado cosas...

Lo que intentaba hacer uno partición ya que el gestor de archivos no me la mostraba, tenía VirtualBox abierto y tal vez firefox; pero concretamente lo que estaba haciendo era ver las opciones de la herramienta de particionado.

Muchas gracias por el apoyo y espero haber aclarado algo.

Translation of Comment#3 :

Excuse me for the lack of information, its the first report i made surly i forgot stuffs...

What i was trying to do is one partition, due the file manager not showing it, i was opened VirtualBox and maybe firefox; but i was trying to see the options of the partitioning tool

(In reply to Miguel Angel González Moreno from comment #3)
Español:

Yo sospecho que podría tratarse de algún problema de memoria, lo primero que deberías hacer es realizarle alguna prueba de memoria al equipo.

Otras cosas que podrías probar es tener menos aplicaciones abiertas
Ejecutar directamente la herramienta, Alt+F2, teclear diskdrake y presionar Enter (o hacerlo desde una consola para ver los mensajes).

Finalmente la plantilla que aparece al abrir un nuevo reporte esta para que tengas una idea de la información minima que se espera en el reporte, y solo cuando tienes mas experiencia y en caso de que el reporte no encaje bien en la plantilla puedes omitirla siempre y cuando des suficientes detalles en tu reporte.

English:

I think that could be of some memory trouble, the first that you should do is make a memory test to your system.

Other things that you could try is have less applications opened
Run directly diskdrake, Alt+F2, type diskdrake and press Enter (or do it fro a console for see the messages),

Finally the template in the new reports is for give you a idea of the minimal information expected in the report, and just when you have more experience and in case that the report not fits well in the template you can skip, only if you give enough details in the report

Thank you katnatek for handling this at present.

We have several bugs "drakconf crashed", but not in the situation Miguel describes; rather, randomly and once-off. It is important to know whether the crash happened just once, or repeatedly. If the latter, can Miguel reproduce it?

If it is something that happened just once, it can never be resolved.

CC: (none) => lewyssmith

Traducción del comentario comment#6 de Lewis Smith

Tenemos varios reportes titulados "drakconf crashed", pero ninguno en la situación que Miguel describe, algo aleatoria y puntual. Es importante saber si el fallo solo ocurrio una vez, o si puede repetirse. Miguel ¿Puedes reproducirlo? (si repites lo que estabas haciendo en drakconf ¿vuelve a pasar lo mismo?)

En xaso de ser algo que paso solo una vez no podrá solucionarse

From the initial comment:

"you must be root to run this program"

This is not a real crash - it is just drakconf complaining because it is being run without root privileges.

There are two drakconf executables, the real one in /usr/libexec and a wrapper script in /usr/bin that prompts the user to enter the root password before running the real drakconf.

So the question to ask is how Miguel is running drakconf.

CC: (none) => mageia

Traducción del comentario comment#8

Del comentario inicial:
"you must be root to run this program"

Esto no es un fallo real - solo es drakconf quejandose de ser ejecutado si permisos de root (administrador).

Hay dos ejecutables de drakconf, el verdadero en /usr/libexec y un script intermediario en /usr/bin que le pide al usuario introducir la contraseña de root antes de ejecutar el drakconf real.

Así que la pregunta a realizar es ¿Como esta ejecutando drakconf Miguel?.

[No need to xlate this comment]
Thank you Martin. I incorrectly believed the 'crash' despite the context of asking for a password. This looks like being 'invalid', but it would be nice to cheer up the reporter.

(In reply to Lewis Smith from comment #10)
> [No need to xlate this comment]
> Thank you Martin. I incorrectly believed the 'crash' despite the context of
> asking for a password. This looks like being 'invalid', but it would be nice
> to cheer up the reporter.

Not necessary invalid it could be some hardware issue disk or memory, i don't really think exist a way by default of run drakconf and not be asked by password

(In reply to katnatek from comment #11)
> (In reply to Lewis Smith from comment #10)
> > [No need to xlate this comment]
> > Thank you Martin. I incorrectly believed the 'crash' despite the context of
> > asking for a password. This looks like being 'invalid', but it would be nice
> > to cheer up the reporter.
> 
> Not necessary invalid it could be some hardware issue disk or memory, i
> don't really think exist a way by default of run drakconf and not be asked
> by password

Nope. Martin is right. If you execute /usr/libexec/drakconf the program will crash with the message seen by Miguel.

Only if you start /usr/bin/drakconf you get a request to enter the root password and drakconf starts.

Español:
Miguel ¿podrías responder la pregunta del comentario comment#9?

Es importante saber  como ejecutaste drakconf, algunos de los participantes sospechan que no lo hiciste de la forma adecuada y que tal vez el reporte no sea valido

English:
Can you answer the question in comment#9?
Its important to know how did you run drakconf, some of participants suspects you don't do it in a right way and maybe this report is invalid

(In reply to katnatek from comment #5)
> (In reply to Miguel Angel González Moreno from comment #3)
> Español:
> 
> Yo sospecho que podría tratarse de algún problema de memoria, lo primero que
> deberías hacer es realizarle alguna prueba de memoria al equipo.
> 
> Otras cosas que podrías probar es tener menos aplicaciones abiertas
> Ejecutar directamente la herramienta, Alt+F2, teclear diskdrake y presionar
> Enter (o hacerlo desde una consola para ver los mensajes).
> 
> Finalmente la plantilla que aparece al abrir un nuevo reporte esta para que
> tengas una idea de la información minima que se espera en el reporte, y solo
> cuando tienes mas experiencia y en caso de que el reporte no encaje bien en
> la plantilla puedes omitirla siempre y cuando des suficientes detalles en tu
> reporte.
> 
> English:
> 
> I think that could be of some memory trouble, the first that you should do
> is make a memory test to your system.
> 
> Other things that you could try is have less applications opened
> Run directly diskdrake, Alt+F2, type diskdrake and press Enter (or do it fro
> a console for see the messages),
> 
> Finally the template in the new reports is for give you a idea of the
> minimal information expected in the report, and just when you have more
> experience and in case that the report not fits well in the template you can
> skip, only if you give enough details in the report

Buenas noches, les pido disculpa por la demora en la respuesta, le hice tests de memoria al equipo y todo normal. Al ejecutar diskdrake desde la terminal me devuelve lo siguiente:

Too late to run INIT block at /usr/lib64/per15/vendor_perl/Glib/Object/Instrospection.pm line 257.
Ignore the following Glib::Object::Instrospection & Gtk3 warnings
Subroutine Gtk3::main redefined at /usr/share/perl5/vendor_perl/Gtk3.pm line 539.

A pesar de esto el programa se ejecutó sin problemas.

(In reply to katnatek from comment #9)
> Traducción del comentario comment#8
> 
> Del comentario inicial:
> "you must be root to run this program"
> 
> Esto no es un fallo real - solo es drakconf quejandose de ser ejecutado si
> permisos de root (administrador).
> 
> Hay dos ejecutables de drakconf, el verdadero en /usr/libexec y un script
> intermediario en /usr/bin que le pide al usuario introducir la contraseña de
> root antes de ejecutar el drakconf real.
> 
> Así que la pregunta a realizar es ¿Como esta ejecutando drakconf Miguel?.

Primero que nada lamento la demora en la respuesta; y respondiendo a la pregunta, lo ejecuté desde el centro de control, o sea, ya al inicio ingresé la contraseña de root; pero el aviso solicitando que ingrese la contraseña apareció en una ventana aparte, ya cuando estaba viendo las particiones...será que abrí el centro de control dos veces y esa solicitud sea de uno de los intentos?
Ojalá pudiese aportarles más información, lo lamento y gracias a todos!

Español:
@Miguel considerando tu ultima respuesta es muy posible, si al ejecutarlo nuevamente ya no tienes este error lo comprobaras, solo se un poco paciente y no oprimas mas de una vez el icono

English:
@Miguel take in count your last answer that is very possible, if you run again and not have this error you make sure, just be a few patient and don't click on the icon more than once.

(In reply to katnatek from comment #16)
> Español:
> @Miguel considerando tu ultima respuesta es muy posible, si al ejecutarlo
> nuevamente ya no tienes este error lo comprobaras, solo se un poco paciente
> y no oprimas mas de una vez el icono
> 
> English:
> @Miguel take in count your last answer that is very possible, if you run
> again and not have this error you make sure, just be a few patient and don't
> click on the icon more than once.

Si, hasta el momento el error no se ha repetido, así que supongo pudo haber sido eso mismo. 
Gracias a todos y espero si me toca reportar un error, poder hacerlo mejor la próxima 🙏

@Marthin Whitake and @sturmvogel

Considering what Miguel answer i think you are right and is a invalid bug

What Miguel did was click two times in drakconf icon , type password the first time
password was required and just close the window in the second time.

With the work load of Miguel's system the time he make that is not amazing that drakconf delay a few or lot more than usual and that is what maybe cause this

Created attachment 14007 [details]
Crash dialogue from /usr/libexec/drakconf

From comment 8:
"This is not a real crash - it is just drakconf complaining because it is being run without root privileges.
There are two drakconf executables, the real one in /usr/libexec and a wrapper script in /usr/bin that prompts the user to enter the root password before running the real drakconf."

/usr/bin/drakconf is the one users run.
/usr/libexec/drakconf is the backend which does the work.

Correcting my own comment 10, this really is a crash (see the attached dialogue) from running directly /usr/libexec/drakconf. The fact that it is asking for a password is correct, no error there. But what Miguel reported was factually correct, although it remains unclear how he gets there.

Dilemma:
1) Do we say "You should not be running /usr/libexec/drakconf directly, so the fact that it crashes is irrelevant = Invalid bug.
2) Or should we accept that if you do run that directly, it should not crash = New bug for mageiatools?

Opinions from CCs please (not from Miguel).

(In reply to Lewis Smith from comment #19)
> But what Miguel reported
> was factually correct, although it remains unclear how he gets there.
Sorry, I overlooked:
(In reply to katnatek from comment #18)
> What Miguel did was click two times in drakconf icon , type password the
> first time
> password was required and just close the window in the second time.
Trying this, I cannot (Xfce) see a 'drakconf' individual icon. Is it one of those inside MCC? If so, the password business is sorted in advance for MCC.
Trying 'run drakconf' from the application menu pops the password dialogue, then opens MCC at the 'manage software' section. Which does not look right.

> (In reply to katnatek from comment #18)
> > What Miguel did was click two times in drakconf icon , type password the
> > first time
> > password was required and just close the window in the second time.
> Trying this, I cannot (Xfce) see a 'drakconf' individual icon. Is it one of
> those inside MCC? If so, the password business is sorted in advance for MCC.
> Trying 'run drakconf' from the application menu pops the password dialogue,
> then opens MCC at the 'manage software' section. Which does not look right.

drakconf is just other name for mcc, i think the bug will be hard to reproduce
And the fact that Miguel say that clicking just once the icon this not happen
make me thing that can be closed as invalid but i let that to you and others

Thanks for the enlightenment!
Unless Miguel can reproduce the fault, and describe more precisely how, we can indeed close this (he can re-open it if he comes up with that information).
In any case, the error reported was trivial and did not affect functionality.

Status: NEEDINFO => RESOLVED
Resolution: (none) => INVALID