Waht's your printer?
Can you attach (not paste) "journalctl -b" logs?
Run eg the following as root:
journalctl -b --since=2016-06-24 > /tmp/journal.txt
(if you had such a freeze to day)

You can further restrict the journal size.
If eg it's 16:30 and you add the freeze at 16h20, you can use:
journalctl -b --since="2016-06-24 16:19" > /tmp/journal.txt

Keywords: (none) => NEEDINFO
CC: (none) => thierry.vignaud
Source RPM: (none) => kernel?

brother DCP-7055
canon MX725

Created attachment 8080 [details]
journalctl

Created attachment 8081 [details]
version

At what time of your logs did you get a freeze?

freeze was at 10:30

freeze was at 20:00:xx

version: Linux localhost.localdomain 4.6.3-desktop-1.mga6 #1 SMP Sat Jun 25 11:20:38 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Created attachment 8108 [details]
2016-07-02

Can you be more precise about the timing?
Around 20:00, there's only a time resync.
I notice nouveau warnings 11 minutes later, at 20:11:06

kernel: nouveau 0000:01:00.0: chrome[3134]: fail ttm_validate
kernel: nouveau 0000:01:00.0: chrome[3134]: validating bo list
kernel: nouveau 0000:01:00.0: chrome[3134]: validate: -12

Dear Thierry,

exactly it was 20:00:25 but the problem seems to me: if the system is frozen, there couldn't be an entry in systemctl. I also took a look to systemctl and didn't found "my time". Well, i can send you my laptop by post and you try that for yourself.

I can try one more thing: install chrony and see what happens then.

Cheers Gerd

Created attachment 8112 [details]
22:45:03

(In reply to Gerd Roscher from comment #11)
> Created attachment 8112 [details]
> 22:45:03

There's

Jul 02 22:46:36 localhost.localdomain kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.6.3-desktop-1.mga6 root=/dev/sda5 ro nokmsboot splash quiet noiswmd resume=UUID=cfaa6e45-f7a8-4c59-99d8-9b9c01d16d18 vga=788

at the top of the file, so this log starts when the system was started after the crash.

"journalctl -b" only gives the output since the newest boot. Sorry if we confused you.

Could you please try to fetch the log again with, as root:

  journalctl -a --since="2016-07-02 22:44" --until="2016-07-03 22:46"

That's 24hrs of logs too much, please use:

journalctl -a --since="2016-07-02 22:44" --until="2016-07-02 22:46"

Created attachment 8119 [details]
journalctl -a --since="2016-07-02 22:44" --until="2016-07-02 22:46" > /tmp/journal.txt

Comment on attachment 8112 [details]
22:45:03

(In reply to Gerd Roscher from comment #14)
> Created attachment 8119 [details]
> journalctl -a --since="2016-07-02 22:44" --until="2016-07-02 22:46" >
> /tmp/journal.txt

Thanks.

So there's 

Jul 02 22:44:24 localhost.localdomain cupsd[1482]: REQUEST localhost - - "POST / HTTP/1.1" 200 273 Create-Printer-Subscriptions successful-ok

And that's it.

(But at least we now know it goes wrong after this)

Attachment 8112 is obsolete: 0 => 1

On the 25th of July, Phillipem uploaded the following packages to 
Cauldron's core/updates_testing:

    system-config-printer-1.5.7-5.mga6.i586
    system-config-printer-applet-1.5.7-5.mga6.i586
    system-config-printer-udev-1.5.7-5.mga6.i586

    system-config-printer-libs-1.5.7-5.mga6.noarch

    system-config-printer-1.5.7-5.mga6.x86_64
    system-config-printer-applet-1.5.7-5.mga6.x86_64
    system-config-printer-udev-1.5.7-5.mga6.x86_64


@ Anyone reading this:

* If this bug is valid for you in cauldron, then please test whether updating your system-config-printer packages to version 1.5.7-5.mga6 fixes the problem and report back in this bug report.

* If you do not have this bug in cauldron, but you do run cauldron, then please update those packages, too, and report in bug 18367 whether they work as expected.

CC: (none) => makowski.mageia

No reply, and Cauldron changed a lot since this bug was last confirmed to be valid (July 2016)

Closing.

Please reopen if this issue is still valid in current, fully updated Cauldron

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