Bug 18782 - can't add a printer
Summary: can't add a printer
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
Depends on:
Blocks: 18367
  Show dependency treegraph
Reported: 2016-06-24 13:46 CEST by Gerd Roscher
Modified: 2017-04-19 10:32 CEST (History)
3 users (show)

See Also:
Source RPM: kernel?
Status comment:

journalctl (143.22 KB, text/plain)
2016-06-28 10:57 CEST, Gerd Roscher
version (115 bytes, text/plain)
2016-06-28 10:58 CEST, Gerd Roscher
2016-07-02 (336.39 KB, text/plain)
2016-07-02 20:27 CEST, Gerd Roscher
22:45:03 (288.39 KB, text/plain)
2016-07-02 22:59 CEST, Gerd Roscher
journalctl -a --since="2016-07-02 22:44" --until="2016-07-02 22:46" > /tmp/journal.txt (3.69 KB, text/plain)
2016-07-04 09:33 CEST, Gerd Roscher

Description Gerd Roscher 2016-06-24 13:46:06 CEST
when i try to add a printer, the system is freezing. i've tried that several times and had always the same problem.

version is: 4.6.2-desktop-3.mga6 #1 SMP Thu Jun 23 09:57:42 UTC 2016 x86_64 x86 64 x86_64 GNU/Linux
Comment 1 Thierry Vignaud 2016-06-24 16:32:28 CEST
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?

Marja Van Waes 2016-06-24 16:45:03 CEST

CC: (none) => marja11
Blocks: (none) => 18367

Comment 2 Gerd Roscher 2016-06-28 10:54:49 CEST
brother DCP-7055
canon MX725
Comment 3 Gerd Roscher 2016-06-28 10:57:44 CEST
Created attachment 8080 [details]
Comment 4 Gerd Roscher 2016-06-28 10:58:19 CEST
Created attachment 8081 [details]
Comment 5 Thierry Vignaud 2016-06-28 11:17:10 CEST
At what time of your logs did you get a freeze?
Comment 6 Gerd Roscher 2016-06-28 11:32:46 CEST
freeze was at 10:30
Marja Van Waes 2016-06-29 17:01:45 CEST

Keywords: NEEDINFO => (none)

Comment 7 Gerd Roscher 2016-07-02 20:25:37 CEST
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
Comment 8 Gerd Roscher 2016-07-02 20:27:30 CEST
Created attachment 8108 [details]
Comment 9 Thierry Vignaud 2016-07-02 20:47:01 CEST
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
Comment 10 Gerd Roscher 2016-07-02 22:38:35 CEST
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
Comment 11 Gerd Roscher 2016-07-02 22:59:27 CEST
Created attachment 8112 [details]
Comment 12 Marja Van Waes 2016-07-04 08:29:58 CEST
(In reply to Gerd Roscher from comment #11)
> Created attachment 8112 [details]
> 22:45:03


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"
Comment 13 Marja Van Waes 2016-07-04 08:34:23 CEST
That's 24hrs of logs too much, please use:

journalctl -a --since="2016-07-02 22:44" --until="2016-07-02 22:46"
Comment 14 Gerd Roscher 2016-07-04 09:33:07 CEST
Created attachment 8119 [details]
journalctl -a --since="2016-07-02 22:44" --until="2016-07-02 22:46" > /tmp/journal.txt
Comment 15 Marja Van Waes 2016-07-04 10:08:54 CEST
Comment on attachment 8112 [details]

(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


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

Comment 16 Marja Van Waes 2016-08-10 19:41:28 CEST
On the 25th of July, Phillipem uploaded the following packages to 
Cauldron's core/updates_testing:




@ 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

Comment 17 Marja Van Waes 2017-04-19 10:32:04 CEST
No reply, and Cauldron changed a lot since this bug was last confirmed to be valid (July 2016)


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

Resolution: (none) => OLD

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