Description of problem: Gnome-control-center (GNOME Settings) crashes often when I am working in the Printers page. One other bug report suggested that this might be related to having Unlocked the Printers panel. I will test that later and report the outcome here. Version-Release number of selected component (if applicable): gnome-control-center.x86_64 3.30.3-1.fc29 How reproducible: Quite often, but I do not exactly know how to reproduce Steps to Reproduce: 1. Go to GNOME Settings | Devices | Printers 2. Unlock the Printers pane 3. Click a little around 4. Switch to another application 5. Switch back to GNOME Settings and interact again with the Printer page Actual results: GNOME Settings crashes. Expected results: No crash.
This issue might be related: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/319, although I experience also crashes when I do not remove printers. Maybe it is related to new printers appearing when the are discovered in the network. See also: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/404 and https://gitlab.gnome.org/GNOME/gnome-control-center/issues/63
See also: https://retrace.fedoraproject.org/faf/reports/bthash/d69460a1ce311c79a3780517aac781d72d620e65
Here is a part of the journal when a crash occurred: apr 02 22:38:19 nyx cupsd[1723]: REQUEST localhost - root "POST / HTTP/1.1" 200 173 CUPS-Get-Devices - apr 02 22:38:19 nyx python3[21990]: io/hpmud/pp.c 627: unable to read device-id ret=-1 apr 02 22:38:19 nyx cupsd[1723]: REQUEST localhost - root "POST / HTTP/1.1" 200 316 CUPS-Get-Devices - apr 02 22:38:19 nyx cupsd[1723]: [cups-deviced] PID 21999 (gutenprint52+usb) stopped with status 1! apr 02 22:38:22 nyx cupsd[1723]: REQUEST localhost - root "POST / HTTP/1.1" 200 1768 CUPS-Get-Devices - apr 02 22:38:29 nyx gnome-shell[2810]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed apr 02 22:38:53 nyx org.fedoraproject.Config.Printing[2738]: /usr/share/system-config-printer/scp-dbus-service.py:63: PyGIDeprecationWarning: GObject.SIGNAL_RUN_LAST is deprecated; use GObject.SignalFlags.RUN_LAST instead apr 02 22:38:53 nyx org.fedoraproject.Config.Printing[2738]: 'ready': (GObject.SIGNAL_RUN_LAST, None, ()), apr 02 22:38:53 nyx org.fedoraproject.Config.Printing[2738]: /usr/share/system-config-printer/scp-dbus-service.py:64: PyGIDeprecationWarning: GObject.SIGNAL_RUN_LAST is deprecated; use GObject.SignalFlags.RUN_LAST instead apr 02 22:38:53 nyx org.fedoraproject.Config.Printing[2738]: 'error': (GObject.SIGNAL_RUN_LAST, None, apr 02 22:38:53 nyx org.fedoraproject.Config.Printing[2738]: /usr/share/system-config-printer/scp-dbus-service.py:602: DeprecationWarning: Gdk.threads_enter is deprecated apr 02 22:38:53 nyx org.fedoraproject.Config.Printing[2738]: Gdk.threads_enter () apr 02 22:38:54 nyx org.signal.Signal.desktop[2810]: {"name":"log","hostname":"nyx","pid":2,"level":30,"msg":"Sending a keepalive message","time":"2019-04-02T20:38:54.866Z","v":0} apr 02 22:39:15 nyx cupsd[1723]: REQUEST localhost - - "POST / HTTP/1.1" 200 182 Renew-Subscription client-error-not-found apr 02 22:39:17 nyx org.freedesktop.problems.applet[2738]: corrupted size vs. prev_size apr 02 22:39:17 nyx audit[25259]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=25259 comm="gnome-control-c" exe="/usr/bin/gnome-control-center" sig=6 res=1 apr 02 22:39:17 nyx systemd[1]: Started Process Core Dump (PID 22213/UID 0). apr 02 22:39:17 nyx audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@6-22213-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' apr 02 22:39:18 nyx systemd-coredump[22223]: Process 25259 (gnome-control-c) of user 1000 dumped core. Stack trace of thread 25259: #0 0x00007f2904fa653f raise (libc.so.6) #1 0x00007f2904f90895 abort (libc.so.6) #2 0x00007f2904fe9927 __libc_message (libc.so.6) #3 0x00007f2904ff025c malloc_printerr (libc.so.6) #4 0x00007f2904ff04b4 malloc_consolidate (libc.so.6) #5 0x00007f2904ff3098 _int_malloc (libc.so.6) #6 0x00007f2904ff58e6 __libc_calloc (libc.so.6) #7 0x00007f2906ac4e1e g_malloc0 (libglib-2.0.so.0) #8 0x00007f29064adf07 n/a (libgtk-3.so.0) #9 0x00007f29064c2c57 n/a (libgtk-3.so.0) #10 0x00007f29064b06e5 n/a (libgtk-3.so.0) #11 0x00007f29064af494 n/a (libgtk-3.so.0) #12 0x00007f29064af67e n/a (libgtk-3.so.0) #13 0x00007f290661180f n/a (libgtk-3.so.0) #14 0x00007f2906611f2c gtk_style_context_get_style_valist (libgtk-3.so.0) #15 0x00007f29066122ed gtk_style_context_get_style (libgtk-3.so.0) #16 0x00007f29064589b8 n/a (libgtk-3.so.0) #17 0x00007f2906ba728b n/a (libgobject-2.0.so.0) #18 0x00007f2906ba8aee g_object_newv (libgobject-2.0.so.0) #19 0x00007f29064526fa n/a (libgtk-3.so.0) #20 0x00007f2906453ce5 n/a (libgtk-3.so.0) #21 0x00007f29064557bd n/a (libgtk-3.so.0) #22 0x00007f2906ac2b62 n/a (libglib-2.0.so.0) #23 0x00007f2906ac3c86 g_markup_parse_context_parse (libglib-2.0.so.0) #24 0x00007f2906455bfe n/a (libgtk-3.so.0) #25 0x00007f2906450a40 gtk_builder_extend_with_template (libgtk-3.so.0) #26 0x00007f29066bb51f gtk_widget_init_template (libgtk-3.so.0) #27 0x0000557db639e0e0 n/a (gnome-control-center) #28 0x00007f2906bc498a g_type_create_instance (libgobject-2.0.so.0) #29 0x00007f2906ba7058 n/a (libgobject-2.0.so.0) #30 0x00007f2906ba8fde g_object_new_valist (libgobject-2.0.so.0) #31 0x00007f2906ba933d g_object_new (libgobject-2.0.so.0) #32 0x0000557db639f827 pp_printer_entry_new (gnome-control-center) #33 0x0000557db63939cd n/a (gnome-control-center) #34 0x00007f2906c7b834 n/a (libgio-2.0.so.0) #35 0x00007f2906c7b86d n/a (libgio-2.0.so.0) #36 0x00007f2906abb97b n/a (libglib-2.0.so.0) #37 0x00007f2906abf06d g_main_context_dispatch (libglib-2.0.so.0) #38 0x00007f2906abf438 n/a (libglib-2.0.so.0) #39 0x00007f2906abf4d0 g_main_context_iteration (libglib-2.0.so.0) #40 0x00007f2906c8fd25 g_application_run (libgio-2.0.so.0) #41 0x0000557db6344405 main (gnome-control-center) #42 0x00007f2904f92413 __libc_start_main (libc.so.6) #43 0x0000557db63445de _start (gnome-control-center)
I found a way to relatively consistently reproduce this crash. Note: * This procedure does not always trigger the crash, but for me in roughly 95% of the times. * I tested this with a printer (HP Color LaserJet Pro MFP M281fdw) for which printing the Test Page does not work (see bug 1694797). * I will test later if I can also reproduce this crash with a printer where printing a Test Page works fine. * There is *no* need to unlock the GNOME Settings Printers panel. Reproduce the crash by: 1. Opening GNOME Settings Printers pane 2. Select Printing Options for the printer for which printing the Test Page does not work 3. Click Test Page *twice* 4. Close Printing Options window 5. Move mouse pointer to other application window (e.g. gedit) 6. Wait until there are No Active (print) Jobs any more 7. Move pointer back to GNOME Settings 8. Wait for about 5 seconds ==> Crash journal messages: apr 03 13:41:11 nyx org.gnome.Shell.desktop[2810]: libinput error: client bug: timer event4 debounce: offset negative (-32ms) apr 03 13:41:11 nyx org.gnome.Shell.desktop[2810]: libinput error: client bug: timer event4 debounce short: offset negative (-45ms) apr 03 13:41:14 nyx cupsd[1723]: REQUEST localhost - - "POST / HTTP/1.1" 200 343 Create-Printer-Subscriptions successful-ok apr 03 13:41:19 nyx cupsd[1723]: REQUEST localhost - - "POST / HTTP/1.1" 200 6165311 CUPS-Get-PPDs - apr 03 13:41:21 nyx cupsd[1723]: REQUEST localhost - - "POST /printers/HP-ColorLaserJet-MFP-M278-M281 HTTP/1.1" 200 430 Print-Job successful-ok apr 03 13:41:21 nyx cupsd[1723]: HP-ColorLaserJet-MFP-M278-M281 jan 449 [03/Apr/2019:13:41:21 +0200] 1 1 - localhost Test Page - - apr 03 13:41:21 nyx cupsd[1723]: REQUEST localhost - - "POST /printers/HP-ColorLaserJet-MFP-M278-M281 HTTP/1.1" 200 430 Print-Job successful-ok apr 03 13:41:22 nyx cupsd[1723]: HP-ColorLaserJet-MFP-M278-M281 jan 449 [03/Apr/2019:13:41:22 +0200] total 0 - localhost Test Page - - apr 03 13:41:22 nyx cupsd[1723]: HP-ColorLaserJet-MFP-M278-M281 jan 450 [03/Apr/2019:13:41:22 +0200] 1 1 - localhost Test Page - - apr 03 13:41:32 nyx cupsd[1723]: HP-ColorLaserJet-MFP-M278-M281 jan 450 [03/Apr/2019:13:41:32 +0200] total 0 - localhost Test Page - - apr 03 13:41:33 nyx cupsd[1723]: Unable to cancel print job. apr 03 13:41:41 nyx gnome-control-center.desktop[2810]: ***MEMORY-ERROR***: gnome-control-center[11618]: GSlice: assertion failed: sinfo->n_allocated > 0 apr 03 13:41:41 nyx audit[11618]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=11618 comm="gnome-control-c" exe="/usr/bin/gnome-control-center" sig=6 res=1 apr 03 13:41:41 nyx systemd[1]: Started Process Core Dump (PID 11798/UID 0). apr 03 13:41:41 nyx audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@39-11798-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' apr 03 13:41:41 nyx systemd-coredump[11799]: Process 11618 (gnome-control-c) of user 1000 dumped core.
Another way to reproduce this crash. 1. Opening GNOME Settings Printers pane 2. Select a printer discovered by DNS-SD (these printers do not actually work) 3. Click quickly Test Page *many times* 4. Close Printing Options window 5. Move mouse pointer to other application window (e.g. gedit) Repeat step 3, 4, and 5 until you get the crash (it takes usually a bit more than five iterations until I encounter the crash)
This bug is still happening on Fedora 30, per bug #1689763 as noted in comment #5 by Jan Vlug.
Also occurring in Fedora 31, adding an OfficeJet 6960.
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Reopening based on comment #7.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.