Bug 16785 - draklog crashed (Unmatched ( in regex; marked by <-- HERE in m/ata4: COMRESET failed)
Summary: draklog crashed (Unmatched ( in regex; marked by <-- HERE in m/ata4: COMRESET...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-19 03:20 CEST by M GT
Modified: 2020-08-16 17:06 CEST (History)
3 users (show)

See Also:
Source RPM: drakxtools-17.88.1-1.mga6
CVE:
Status comment:


Attachments
lspcidrake -v (4.28 KB, text/plain)
2015-09-19 03:20 CEST, M GT
Details
CCM (MCC) logs (44.79 KB, image/png)
2015-09-19 03:44 CEST, M GT
Details

Description M GT 2015-09-19 03:20:11 CEST
Created attachment 7017 [details]
lspcidrake -v

The "draklog" program crashed. Drakbug-16.104 caught it.

Recherche dans les journaux système avec crash après ajout du caractère (
dans la chaîne recherchée.

http://www.reverso.net/text_translation.aspx?lang=FR

Search(Research) in newspapers system = > crash after addition of the character "(" in the sought(studied) chain(channel).

Unmatched ( in regex; marked by <-- HERE in m/ata4: COMRESET failed ( <-- HERE / at /usr/libexec/draklog line 271.
Perl's trace:
drakbug::bug_handler() called from /usr/lib/perl5/vendor_perl/5.20.1/Gtk3.pm:295
Gtk3::__ANON__() called from /usr/lib/libDrakX/mygtk3.pm:1521
mygtk3::main() called from /usr/lib/libDrakX/ugtk3.pm:859
ugtk3::main() called from /usr/libexec/draklog:191

Theme name: oxygen-gtk
Kernel version = 3.19.8-desktop-3.mga5
Distribution=Mageia release 5 (Official) for x86_64
CPU=Intel(R) Core(TM) i5-4430 CPU @ 3.00GHz

Au cours d'une recherche dans les logs :

ata:4 COMRESET failed 
=> Ok

Ajout d'une parenthèse :

ata:4 COMRESET failed ( 
=> Crash

http://www.reverso.net/text_translation.aspx?lang=FR

During a search(research) in logs:

Ata:4 COMRESET failed 
= > OK

Addition of a bracket:

Ata:4 COMRESET failed (
= > Crash
Comment 1 M GT 2015-09-19 03:33:48 CEST
Par ailleurs il est à noter qu'une recherche sur 

ata4: COMRESET failed (errno=-16) 

ne retourne rien bien que cette chaîne figure dans les logs.

http://www.reverso.net/text_translation.aspx?lang=FR

Besides it should be noted that a search on 
Ata4: COMRESET failed (errno 16) 
Turn nothing, please, that this chain appears in logs.
Comment 2 M GT 2015-09-19 03:38:35 CEST
Besides it should be noted that a search on 
Ata4: COMRESET failed (errno=-16) 
Turn nothing, please, that this chain appears in logs:
Comment 3 M GT 2015-09-19 03:44:48 CEST
Created attachment 7018 [details]
CCM (MCC) logs

It should be noted that a search on 
Ata4: COMRESET failed (errno 16) 
Turn nothing, please, that this chain appears in logs.

What sees itself by making a search(research) only on COMRESET or only on failed.

CC: (none) => nmrk.n

Comment 4 M GT 2015-09-19 03:51:03 CEST
Understand (errno=-16)
It is Reverso which deletes(eliminates) "=" and "-" by translating.
Excuses.
Rémi Verschelde 2015-09-19 10:51:26 CEST

Summary: draklog crashed => draklog crashed (Unmatched ( in regex; marked by <-- HERE in m/ata4: COMRESET failed)
Assignee: bugsquad => thierry.vignaud

Comment 5 Marja Van Waes 2018-04-14 12:22:29 CEST
@ M GT,

Thank you for having taken the needed time to report this issue!

Did this bug get fixed? If so, please change it's status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set version to Cauldron and add MGA6TOO on the Whiteboard.

Thanks,
Marja

CC: (none) => marja11

Comment 6 M GT 2018-04-20 16:11:03 CEST
Recherche dans les log contenant le caractère (

Le programme « draklog » a planté avec l'erreur suivante :

  Unmatched ( in regex; marked by <-- HERE in m/Apr\s{1,2}20\s.*( <-- HERE bug.*
  / at /usr/libexec/draklog line 271.
  Perl's trace:
  drakbug::bug_handler() called from /usr/lib/perl5/vendor_perl/5.22.3/Gtk3.pm:524
  Gtk3::__ANON__() called from /usr/lib/libDrakX/mygtk3.pm:1550
  mygtk3::main() called from /usr/lib/libDrakX/ugtk3.pm:857
  ugtk3::main() called from /usr/libexec/draklog:191

Version: 5 => 6

M GT 2018-04-20 16:13:12 CEST

Source RPM: drakxtools-16.104-1.mga5 => drakxtools-17.88.1-1.mga6

Comment 7 Aurelien Oudelet 2020-08-16 17:06:25 CEST
Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It 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 6'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.

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/

Best regards,
Aurélien
Bugsquad Team

Status: NEW => RESOLVED
CC: (none) => ouaurelien
Resolution: (none) => OLD


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