does it work if you install and enable rsyslog ?

Source RPM: (none) => drakconf

Yes!

But it should be useful to tell to the user that /var/log/explanations does exist and contains more informations.
This can be done with a text which appears at the top of the pop-up window when it is opened.
Is the button "Save" useful now? It could be replaced with "Show /var/log/explanations" with kwrite or vim.

Mageia3 beta4: Just after a fresh install, the problem is still there :-(

I've pushed a change to svn that should now insist on installing a syslog-daemon. This is just a stop-gap. Long term we should ensure it's capable of talking to the journal directly (which should allow much better log experiences overall).

FWIW, I found two bugs in the mode of logdrak as used here...

1. When called with --explain=drakxtools, it searches the log for all occurrences of log items from this program. Nice in theory but not so much in practice as filtering function designed to work in the GUI helpfully makes all the tests fail and thus doesn't output any historical log snippets.

This should be fixed with this patch:


diff --git a/perl-install/standalone/logdrake b/perl-install/standalone/logdrake
index 145a38e..1977fee 100755
--- a/perl-install/standalone/logdrake
+++ b/perl-install/standalone/logdrake
@@ -264,8 +264,10 @@ sub parse_file {
       $test = sub { $_[0] !~ /$en/ };
   } elsif ($ey && !$en) {
       $test = sub { $_[0] =~ /$ey/ };
-  } else {
+  } elsif ($ey && $en) {
       $test = sub { $_[0] =~ /$ey/ && $_[0] !~ /$en/ };
+  } else {
+      $test = sub { 1 };
   }
 
   foreach (@all) {



Then it goes on to tail the file. It would appear to simply then output everything it finds in the file without handling the --explain filtering nor any other tests.

I kinda lost interest in patching it at this point. I don't see the point in fixing up years old bugs when this should get an almost complete reimplementation for the journal if anyone is truely interested.

I think this bug is sufficiently fixed for now (only issue remaining would be *starting* rsyslog or syslog-ng after installing them...)

CC: (none) => mageia, thierry.vignaud

Closing it. See also 8722

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

Reopening, fix is not complete;

I installed RC3 initially, since then updated.
I have syslog-ng installed (due to a forum tip), so viewing the logs in MCC works, and Ctrl-Alt-F12 shows log.  But with this, the MCC log window is plain empty!

It seems rsyslog is needed to the MCC own log  rsyslog.

I uninstalled syslog-ng, and in MCC main panel menu, enabled log, and now a message pops up telling syslog-daemon need to be installed.  What it actually install is rsyslog.  And only after reboot it worked.

So it seems MCC log wiewing specifically need rsyslog... It should then check for it and installit (and remove coflicting syslog-ng if it is installed)
(OR make it work with syslog-ng.)

And that popup could also tell reboot is necessary.

Status: RESOLVED => REOPENED
CC: (none) => fri
Resolution: FIXED => (none)

Please open a new bug for this as I think we should keep this one closed. The log viewer not working with syslog-ng is a separate issue to what this bug was really fixing IMHO and is arguably a regression over previous versions (tho' I cannot think of why this would be the case of the top of my head)

Keep in mind also that the MMC log window is basically a view on to the /var/log/explanations file and to be honest I think it's a really pointless thing anyway as the parsing and filtering it does on the output makes little sense to me when I poked at that code recently as noted in comment 4 above. Anyway, like I say, it's probably best done on a separate bug now if that's OK.

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

OK, -> Bug 10280