Your message dated Thu, 08 May 2014 11:21:23 -0400
with message-id <[email protected]>
and subject line Re: #656948 - GLib-CRITICAL **: g_variant_new_string:
assertion `string != NULL' failed
has caused the Debian Bug report #656948,
regarding GLib-CRITICAL **: g_variant_new_string: assertion `string != NULL'
failed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
656948: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656948
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnome-settings-daemon
Version: 3.2.2-2
Severity: normal
I always get six copies of this GLib assertion failure message in my
..xsession-errors immediately upon logging in.
(gnome-settings-daemon:16016): GLib-CRITICAL **: g_variant_new_string:
assertion `string != NULL' failed
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (501, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gnome-settings-daemon depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.10.0-3
ii dpkg 1.16.1.2
ii gsettings-desktop-schemas 3.2.0-2
ii libatk1.0-0 2.2.0-2
ii libc6 2.13-24
ii libcairo-gobject2 1.10.2-6.2
ii libcairo2 1.10.2-6.2
ii libcanberra-gtk3-0 0.28-3
ii libcanberra0 0.28-3
ii libcolord1 0.1.15-3
ii libcomerr2 1.42-1
ii libcups2 1.5.0-15
ii libdbus-1-3 1.4.16-1
ii libdbus-glib-1-2 0.98-1
ii libfontconfig1 2.8.0-3.1
ii libfreetype6 2.4.8-1
ii libgconf2-4 3.2.3-1
ii libgcrypt11 1.5.0-3
ii libgdk-pixbuf2.0-0 2.24.0-2
ii libglib2.0-0 2.30.2-5
ii libgnome-desktop-3-2 3.2.1-3
ii libgnome2-common 2.32.1-2
ii libgnomekbd7 3.2.0-1
ii libgnutls26 2.12.16-1
ii libgssapi-krb5-2 1.10+dfsg~beta1-2
ii libgtk-3-0 3.2.3-1
ii libgudev-1.0-0 175-3
ii libk5crypto3 1.10+dfsg~beta1-2
ii libkrb5-3 1.10+dfsg~beta1-2
ii liblcms2-2 2.2+git20110628-2
ii libnotify4 0.7.4-1
ii libpackagekit-glib2-14 0.7.2-2
ii libpango1.0-0 1.29.4-2
ii libpolkit-gobject-1-0 0.104-1
ii libpulse-mainloop-glib0 1.1-2
ii libpulse0 1.1-2
ii libsqlite3-0 3.7.9-3
ii libupower-glib1 0.9.15-1
ii libx11-6 2:1.4.4-4
ii libxfixes3 1:5.0-4
ii libxi6 2:1.4.5-1
ii libxklavier16 5.1-3
ii nautilus-data 3.2.1-2
ii zlib1g 1:1.2.3.4.dfsg-3
Versions of packages gnome-settings-daemon recommends:
ii hwdata 0.233-1
ii pulseaudio 1.1-2
Versions of packages gnome-settings-daemon suggests:
ii gnome-screensaver 3.2.0-2+b1
ii metacity [x-window-manager] 1:2.34.1-2
ii mutter [x-window-manager] 3.2.1-2
ii x11-xserver-utils 7.6+3
-- no debconf information
--- End Message ---
--- Begin Message ---
On 05/06/2014 09:54 AM, althaser wrote:
> Hey Zack,
>
> this is an old bug.
>
> Could you please still reproduce this issue with newer
> gnome-settings-daemon version like 3.4.2+git20121218.7c1322-3+deb7u3 or
> 3.8.5-2 ?
It seems to have been fixed; a current session log does not show this
particular error message. (I see lots of other errors but I suspect
these are due to unstable's current messy combination of GNOME 3.8 and
3.12.) I will go ahead and close the bug report.
zw
--- End Message ---
