gsd-print-notifications assert failure: free(): invalid pointer

Bug #1826159 reported by Jan Wester
48
This bug affects 6 people
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

This problem occurs since upgrade to disco dingo. Have not seen this in earlier releases. It seems to be related to printers in the gnome settings.

janw-LIFEBOOK-AH532-G21{janw}(79)% lsb_release -rd
Description: Ubuntu 19.04
Release: 19.04

apt-cache policy gnome-settings-daemon
gnome-settings-daemon:
  Installerad: 3.32.0-1ubuntu1
  Kandidat: 3.32.0-1ubuntu1
  Versionstabell:
 *** 3.32.0-1ubuntu1 500
        500 http://se.archive.ubuntu.com/ubuntu disco/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: gnome-settings-daemon 3.32.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AssertionMessage: free(): invalid pointer
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 23 22:16:13 2019
ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-print-notifications
InstallationDate: Installed on 2018-02-20 (427 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-print-notifications
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=sv_SE.UTF-8
 SHELL=/bin/tcsh
Signal: 6
SourcePackage: gnome-settings-daemon
StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f247b810952 "%s\n") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (str=str@entry=0x7f247b80ea9b "free(): invalid pointer") at malloc.c:5352
 _int_free (av=<optimized out>, p=<optimized out>, have_lock=<optimized out>) at malloc.c:4181
 ()
 g_list_foreach () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gsd-print-notifications assert failure: free(): invalid pointer
UpgradeStatus: Upgraded to disco on 2019-04-19 (4 days ago)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
mtime.conffile..etc.apport.crashdb.conf: 2019-04-24T11:16:47.806271
separator:

Revision history for this message
Jan Wester (j-vester) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f247b810952 "%s\n") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (str=str@entry=0x7f247b80ea9b "free(): invalid pointer") at malloc.c:5352
 _int_free (av=<optimized out>, p=<optimized out>, have_lock=<optimized out>) at malloc.c:4181
 free_reason_data (user_data=0x7f246c0014e0) at ../plugins/print-notifications/gsd-print-notifications-manager.c:243
 g_list_foreach (list=<optimized out>, list@entry=0x564a05c2bd80, func=0x564a043b6e90 <free_reason_data>, user_data=user_data@entry=0x0) at ../../../glib/glist.c:1013

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-settings-daemon (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

information type: Private → Public
Changed in gnome-settings-daemon (Ubuntu):
status: New → Incomplete
Revision history for this message
Jan Wester (j-vester) wrote :

For the moment I do not seem to be able to reproduce this. So I guess it happened when I tried to send the report bug thing in the popup since that popup came because of another crash: _usr_lib_x86_64-linux-gnu_cups-pk-helper-mechanism.125.crash. But since that failed I edited the crashdb conf file. So it CAN be that this doesnt happen anymore. But very uncertain........

That other crash seems to happen every time pressing adding printers

Changed in gnome-settings-daemon (Ubuntu):
status: Incomplete → New
Revision history for this message
Sebastien Bacher (seb128) wrote :
Changed in gnome-settings-daemon (Ubuntu):
importance: Medium → Low
Revision history for this message
Jan Wester (j-vester) wrote :

I actually succeeded in getting this dump again. From the gnome settings up in the right corner, choose Test print. The printout went to the printer options and made a test print from the button in the left corner of the windows. That crash appeared in /var/crash despite it looks like everything works......This time I also got another crash at the same time:

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-settings-daemon (Ubuntu):
status: New → Confirmed
tags: added: focal
Revision history for this message
oldfred (oldfred) wrote :

May be related to this bug as printing issues started with it.

https://bugs.launchpad.net/ubuntu/+source/ippusbxd/+bug/1866838

Revision history for this message
oldfred (oldfred) wrote :

I seem to be getting both IPv4 & IPv6 with same hostname, so then printer does not connect.
I turned off IPv6 and now it works, but have to release it every time.

sudo nano /etc/cups/cups-browsed.conf
Changed to use only IPv4
# IPBasedDeviceURIs IPv4
IPBasedDeviceURIs IPv4

fred@fred-Z170N-focal:~$ apt show cups
Package: cups
Version: 2.3.1-9ubuntu1
Priority: optional

https://github.com/OpenPrinting/cups-filters/issues/22
https://github.com/lathiat/avahi/issues/125

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.