Bug 12081

Summary: Shutdown/restart can sometimes be slow
Product: Mageia Reporter: Michel Morisot <info>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: christian-maryse.fischer, cmrisolde, mageia, thierry.vignaud
Version: Cauldron   
Target Milestone: Mageia 4   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:

Description Michel Morisot 2013-12-22 15:15:55 CET 
Lorsque je demande l'extinction du PC , il sâarrête parfois rapidement en quelques secondes, parfois, il faut une à deux minutes pour s'éteindre.


Il bloque 1 à 2 minutes après le message concernant l'acpi:

- started load/save backlight brighness of acpi_video0
- started LSB bring up/down networking

câble réseau débranché mais connecté en wifi.


Deuxième essai:

- started load/save backlight brighness of acpi_video0

--> extinction en quelques secondes

pas de second message " started LSB bring up/down networking" pour le moment (wlan0)

Est-ce que le faite d'avoir coché l'activation des cartes réseaux (eth0 et wlan0) au démarrage" pourrait avoir une conséquence lors de l'extinction si une des cartes n'est pas connectée, ici en occurrence la eth0, je suis en wifi (wlan0).

Troisième essai avec les interfaces désactivées par défaut au démarrage, pas de changement à l'extinction (2 minutes) ni au démarrage (quelques secondes). je re-coche donc "activée au démarrage"



When I ask for the extinction of the PC, it stops sometimes quickly in a few seconds, sometimes, it is necessary one for two minutes to die out. 

It blocks 1 to 2 minutes after the message concerning the acpi: 

- started load/save backlight brighness of acpi_video0 
- started LSB bring up/down networking 

cable network disconnected but connected in wifi. 


Second test: 

- started load/save backlight brighness of acpi_video0 --> extinction in some second 

not of second message âstarted LSB bring up/down networkingâ for the moment (wlan0) 

The activation of the cards networks (eth0 and wan0) to startingâ could have a consequence during the extinction if one of the cards is not connected, here in occurrence the eth0, I am in wifi (wlan0). 

Third test with the disabled interfaces by default with starting, not of change to the extinction (2 minutes) nor with starting (a few seconds). I Re-stage coach thus âactivated with the startingâ 


source: http://www.mageialinux-online.org/forum/topic-17113+extinction-du-portable.php

Reproducible: 

Steps to Reproduce:
Michel Morisot 2013-12-22 15:41:47 CET

Target Milestone: --- => Mageia 4

Comment 1 Carolyn Rowse 2013-12-22 19:52:18 CET 
I'm now finding that Beta2 is sometimes very slow to shutdown, but I'm not getting any messages to indicate what the problem is, only that it occurs after the first bubble has disappeared from the cauldron.  I'm using MATE, but installation was from the live KDE DVD.

Carolyn

CC: (none) => isolde

Comment 2 Michel Morisot 2013-12-26 13:04:45 CET 
hello 

Currently the extinction is braked of a minute with the message preceded by a red signal flickering: 
With stop job is running for CUPS Printing Service 


However no file is on standby of impression, only one printer is configured.



******** french **********

bonjour
Actuellement l'extinction est freinée d'une minute avec le message précédé d'un signal rouge clignotant:
A stop job is running for CUPS Printing Service

Pourtant aucun fichier n'est en attente d'impression, une seule imprimante est configurée.
Thierry Vignaud 2013-12-26 19:00:27 CET

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

Comment 3 Colin Guthrie 2013-12-26 22:41:14 CET 
Typically, I'm seeing this when user jobs fail to be stopped or related to a cups option.

If you do the following:

systemctl mask cups.service


Then try to reproduce the issue (only after an initial reboot - the first one won't count) then it's related to cups.

If you still get the issue then it's related to the user session jobs not stopping which is a bit of a known issue. I have once fix in the pipeline for this but I doubt it's the only one that will be needed as there are a few corner cases still to be dealt with I think.
Colin Guthrie 2013-12-26 22:48:02 CET

Summary: When I ask for the extinction of the PC, it stops sometimes quickly in a few seconds,..... => Shutdown/restart can sometimes be slow

Comment 4 christian fischer 2014-01-22 10:57:27 CET 
Cauldron(beta2) and Mageia4 RC 
+ HP laserjet 1212nf on LAN installed with HPLIP + HP plugin.

On shutdown, my computer is complaining for 1 mn with red stars:

"[ ***] A stop job is running for CUPS Printing service "

if y do as root:
systemctl mask cups.service

then computer stop nice ( 4 s )

(idem if no printer installed)

CC: (none) => christian-maryse.fischer

Comment 5 Colin Guthrie 2014-01-22 11:39:17 CET 
Hmm, I thought this bug had been fixed.

Can you modify your /etc/cups/cups.conf config to;

BrowseLocalProtocols CUPS dnssd

to read:

BrowseLocalProtocols CUPS

(i.e. kill the dnssd bit)

Then unmask it again and make sure it's started. Does this also solve the slowness?
Comment 6 Colin Guthrie 2014-01-25 19:55:57 CET 
Did the above help?
Comment 7 christian fischer 2014-01-25 22:54:41 CET 
Hello
Bug seem fixed on my Cauldron installed from Mageia4 RC ( + updates)


On my older Cauldron installed fron Mageia4 beta2 (+ updates) bug exist.
So y do :
- Modify /etc/cups/cupsd.conf  :
BrowseLocalProtocols CUPS dnssd -> BrowseLocalProtocols CUPS

- Re-install plugin HP for laserjet M1212nf and test  OK( ? )

- Reboot  ( nice)
- Modify /etc/cups/cupsd.conf  :
BrowseLocalProtocols CUPS  -> BrowseLocalProtocols CUPS dnssd

reboot is good
Comment 8 Manuel Hiebel 2014-01-28 18:50:25 CET 
closing then

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