Description of problem: I you try to add a printer with MCC/hardware, all the system crashes the moment you click on the add button Version-Release number of selected component (if applicable): Mageia 6 sta1 x86_64 Plasma How reproducible: every time Steps to Reproduce: 1. 2. 3.
I cannot reproduce this in a cauldron (also using Plasma5) that was installed some months ago, and last updated today, and don't understand what can be so different between 6sta1 and my cauldron. Anyway, assigning to all packagers collectively, since there is no maintainer for this package.
Source RPM: drakconf => system-config-printerKeywords: (none) => 6sta1CC: (none) => marja11Assignee: bugsquad => pkg-bugs
I also have a cauldron (mga5 upgraded), the behaviour is different, in MCC/hardware a click on "Set up the printer .." gives a pop up error message: Warning This program has exited abnormally
Blocks: (none) => 18367
Still valid with Mageia 6 sta1 x86_64 Plasma from May 20 on a DELL latitude laptop. On a home-made desktop, the system doesn't crash but doesn't make the installation either.
With Mageia-6-sta1-x86_64-DVD from May 20, the bug is solved in a UEFI station but still valid in a BIOS one
Keywords: (none) => 6RC
Regression with mga6rc, not only the system crashes but can boot no more, after the connection screen, the system freeze just after the fifth bubble.
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
Bug still present with system-config-printer-1.5.7-5.mga6.x86_64 Dell latitude D630, real hw, BIOS firmware, Cauldron up to date.
(In reply to André DESMOTTES from comment #7) > Bug still present with system-config-printer-1.5.7-5.mga6.x86_64 > Dell latitude D630, real hw, BIOS firmware, Cauldron up to date. This is still that cauldron that was started from 6sta1?
Please attach output.txt to this report, that is the result of starting (as root): journalctl -af 2>&1 |tee output.txt letting it run and then getting the crash. Btw, in comment #0 it says "all the system crashes", but the summary says "MCC crashes". Is it only MCC, or really everything?
(In reply to Marja van Waes from comment #8) > (In reply to André DESMOTTES from comment #7) > > Bug still present with system-config-printer-1.5.7-5.mga6.x86_64 > > Dell latitude D630, real hw, BIOS firmware, Cauldron up to date. > > This is still that cauldron that was started from 6sta1? It is a mga6-RC where I changed the sources to Cauldron ones.
(In reply to Marja van Waes from comment #9) > Please attach output.txt to this report, that is the result of starting (as > root): > > journalctl -af 2>&1 |tee output.txt > > letting it run and then getting the crash. > > Btw, in comment #0 it says "all the system crashes", but the summary says > "MCC crashes". > > Is it only MCC, or really everything? It is the whole software that crashes, it is impossible to power off or reboot properly, the only way is a long push on the power on button. After that, it is impossible to reboot, the connection screen never shows up, so it is impossible to redo the crash, it needs a new install. In progress
On another mga6 installation up to date (included system-config-printer-1.5.7-5.mga6.x86_64), I entered the command: journalctl -af 2>&1 |tee output.txt under root then, I tried to install a printer and the system crashed, I rebooted, this time the connection was possible, I found the file /root/output.txt, it is empty.
(In reply to André DESMOTTES from comment #11) > > It is the whole software that crashes, it is impossible to power off or > reboot properly, Did you try to switch to a text tty with ctrl+alt+F2 ? > the only way is a long push on the power on button. Don't the Magic keys (keep Alt+SysRq pressed, then type "r s e i u b") work to reboot, either ? > After that, it is impossible to reboot, the connection screen never shows > up, so it is impossible to redo the crash, it needs a new install. > In progress That sounds awful :-( Is it possible, from a still working install, to mount the root partition of that installation and check with journalctl -a /path/to/that/root/partition/var/log/journal/<long_string>/ whether you can see anything useful about what happens when the system crashes/freezes? You might also want to check /path/to/that/root/partition/var/log/Xorg.0.log
Summary: MCC crashes when trying to add a printer => System freezes when trying to add a printer
It is impossible to open a text tty or to use the Magic keys, the keyboard is frozen, and the mouse as well. I already checked /var/log/Xorg.0.log and found nothing strange What do you call <long_string> ? Is it the folder with a name that looks like "/var/log/journal/8681eb44cfd84010beba82219d6d063d"? In this folder are "<long_string>" files.
(In reply to André DESMOTTES from comment #14) Thanks for the fast replies > What do you call <long_string> ? Is it the folder with a name that looks > like "/var/log/journal/8681eb44cfd84010beba82219d6d063d"? In this folder are > "<long_string>" files. In this case, if that's on that root partition, "8681eb44cfd84010beba82219d6d063d" is the long string The path to the /var/log/journal/ directory with such a long name is what's needed.
Created attachment 8332 [details] asked files
For your information, the crash was at 08h48
Thanks, André The jumping time is a bit confusing (I have that in my logs, too, sometimes) Anyway: not sure whether this indicates some instability that "helps" to get the later crash/hard freeze, but I see some of those: aug 12 08:47:57 localhost.localdomain kernel: Call Trace: aug 12 08:47:57 localhost.localdomain kernel: Call Trace: (and then the backtrace) and two sddm segfaults aug 12 08:47:47 localhost.localdomain kernel: sddm[1609]: segfault at 6e9e00 ip 00000000006e9e00 sp 00007fff78224cf8 error 15 aug 12 08:47:52 localhost.localdomain kernel: sddm[2821]: segfault at 200020 ip 0000000000200020 sp 00007fffba81f748 error 14 in sddm[400000+66000] Sorry for having forgotten the "--directory" (or "-D") option in the command /o\ This will work better: journalctl -a -D /path/to/that/root/partition/var/log/journal/<long_string>/ where "<long string>" is something like "8681eb44cfd84010beba82219d6d063d" Can you try to run it again.... there might be more information than I could get from only the system.journal and user-1000.journal in that directory... or were there no other files? Btw, did you ever reproduce this in a different DE (or even with a different DM)?
Keywords: 6sta1 => (none)
Created attachment 8334 [details] asked file I redid a crash at 10h21 (time in the taskbar) and this time the computer accepted to reboot, so I used the command: journalctl -a -D /var/log/journal/<long_string>/ 2>&1 |tee output.txt With LxQt and lightdm as DM, the behaviour is strictly the same (neither kb nor mouse)
(In reply to André DESMOTTES from comment #19) > Created attachment 8334 [details] > asked file Thanks again, André > > I redid a crash at 10h21 (time in the taskbar) and this time the computer > accepted to reboot, so I used the command: > journalctl -a -D /var/log/journal/<long_string>/ 2>&1 |tee output.txt Good.... so there's nothing in the logs (or I'm blind) :-( ("journalctl -a 2>&1 |tee output.txt" would have been valid, too, now, because you managed to boot into the same install ;-) ) I suppose you deleted a line -- Reboot -- and what followed after it, correct? > > With LxQt and lightdm as DM, the behaviour is strictly the same (neither kb > nor mouse) And in all cases (with plasma5/SDDM too) the screen does not turn black, but it is frozen (including the clock, which keeps having the time of the freeze), correct? Do you get to see the screen you should get when adding a printer, or does it not appear at all? Please try to start system-config-printer (as root) from the command line. If you drag the s-c-p window to the right, and your konsole/terminal to the left, so they are side by side, then maybe you can see a relevant error message when trying to add a printer?
@ any packager/developer Could one of you please have a look at the kernel Call Traces (there are 8 of them) in attachment #8334 [details] ? Is there any chance they are related to this bug?
(In reply to Marja van Waes from comment #20) > > I suppose you deleted a line > -- Reboot -- > and what followed after it, correct? I didn't delete anything in output.txt, just before creating a new crash, I deleted everything in /var/log/journal, to have shorter logs, it was may be a mistake ? > > > > With LxQt and lightdm as DM, the behaviour is strictly the same (neither kb > > nor mouse) > > And in all cases (with plasma5/SDDM too) the screen does not turn black, but > it is frozen (including the clock, which keeps having the time of the > freeze), correct? Yes everything is frozen, clock included. > > Do you get to see the screen you should get when adding a printer, or does > it not appear at all? See the SC here after The cursor is changed into those two small black spheres. > > Please try to start system-config-printer (as root) from the command line. > If you drag the s-c-p window to the right, and your konsole/terminal to the > left, so they are side by side, then maybe you can see a relevant error > message when trying to add a printer? A new line is added in the terminal: rmmod: ERROR: Module lp is not currently loaded
Created attachment 8335 [details] Screenshot
(In reply to André DESMOTTES from comment #22) > (In reply to Marja van Waes from comment #20) > > > > > I suppose you deleted a line > > -- Reboot -- > > and what followed after it, correct? > > I didn't delete anything in output.txt, just before creating a new crash, I > deleted everything in /var/log/journal, to have shorter logs, it was may be > a mistake ? > I don't know :-) The documented way of creating a shorter log is e.g.: journalctl -a --since="2016-08-12 10:15" --until="2016-08-12 10:25" (adjust time as needed) Of course, thanks that you didn't add unnecessary big attachments! > > > > And in all cases (with plasma5/SDDM too) the screen does not turn black, but > > it is frozen (including the clock, which keeps having the time of the > > freeze), correct? > > Yes everything is frozen, clock included. > > > > > Do you get to see the screen you should get when adding a printer, or does > > it not appear at all? > > See the SC here after > The cursor is changed into those two small black spheres. > > > > > Please try to start system-config-printer (as root) from the command line. > > If you drag the s-c-p window to the right, and your konsole/terminal to the > > left, so they are side by side, then maybe you can see a relevant error > > message when trying to add a printer? > > A new line is added in the terminal: > rmmod: ERROR: Module lp is not currently loaded Could you try starting system-config-printer in debug mode, again as root: /bin/python3 /usr/share/system-config-printer/system-config-printer.py --debug If you add " 2>&1 | tee scp-debug.txt" to the command, the output will be written to a file, which you can attach here :-)
(Of course, I meant start in debug mode + reproduce the freeze)
Created attachment 8336 [details] scp-debug.txt Made ask asked
Same behaviour with system-config-printer-1.5.7-8.mga6.
I didn't encounter this problem when adding a printer. New install, not updating.
CC: (none) => yves.brungard_mageia
After an update today september the 10th, I have a different response but still unable to install a printer: MCC > Set up the printer(s); the print job... > Message "You are about to install the following software..." system-config-printer task-printing-server task-printing-hp > Install > Message "Some requested packages cannot be installed. Python-requests-2.10.0-1mga6.noarch (due to unsatisfied pythonegg(3)(urllib3)[==1.15.1]. Continue installation anyway ? OK > nothing happens, no printer.
system-config-printer-1.5.7-8.mga6 have both urpmi and packagekit enable that cause race condition. Somehow have to work on packagekit so it can be use with s-c-p or we have to revert to what we had in mga5
Still valid?
CC: (none) => friSummary: System freezes when trying to add a printer => System freezes when trying to add a printer - race urpmi/packagekit?
Solved
Status: NEW => RESOLVEDResolution: (none) => FIXED