G_VALUE_HOLDS_BOOLEAN (value)' failed

[dino99]

Binary package hint: gdm

Lucid B1 updated

got this warning into syslog:

gdm-session-worker[1165]: GLib-GObject-CRITICAL: g_value_get_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

ProblemType: Bug
Architecture: i386
Date: Thu Mar 18 10:18:13 2010
DistroRelease: Ubuntu 10.04
NonfreeKernelModules: nvidia
Package: gdm 2.29.92-0ubuntu3 [modified: var/lib/gdm/.gconf.defaults/%gconf-tree.xml]
ProcEnviron:
 LANG=fr_FR.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic-pae
SourcePackage: gdm
Uname: Linux 2.6.32-16-generic-pae i686

[Stéphane List (slist)]

On each login/poweron I've got this error in /var/log/syslog :

Apr 22 11:11:03 Ubuntu-desktop gdm-session-worker[1335]: GLib-GObject-CRITICAL: g_value_get_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[dino99 (9d9)]

since rc this error is gone now on my end, so it can be invalidated (my logs are clean)

[Sebastien Bacher (seb128)]

closing since that works now

[ishy (moodsey211)]

I have this bug on my system and it is preventing me from logging in using the GUI. I'm doing a backtrace now and will upload the file later.

[Graham Crumb (gcrumb)]

Suggest you re-open, as it's reliably happening to me on an up-to-date Lucid system (i386).

[dino99 (9d9)]

note:
to those having this problem: this issue is gone on my end with a basic system ( no wifi, no bluetooth, no compiz, only genuine lucid repo) and i regularly run: gconf-cleaner and bleachbit (as admin) to wipe oldish settings and broken things left behind.

[Aghast (svarte)]

The bug still persist for me. Logs are attached.

[David Huber (david-huber)]

I had this problem 3 times today. My screen freezes and the only way to recover it to reboot my computer.

[Ken Southerland (crowmagnumb)]

On a reboot, possibly from an auto-upgrade of one of the packages (?), I now can't log in. I get the login window, type in my login and password, it goes off thinking for about 5 or 6 seconds with the screen going black during this time, and then the computer beeps at me and I'm right back to the login screen. No message, no information.

Booting off a thumbdrive and then mounting the disk to look at /var/log/syslog I find the above message as the last message in that file. That's the only thing I can find that looks wrong.

Can anyone help me with this?

[Ken Southerland (crowmagnumb)]

Oh, I also can't get a shell open. If I login in as failSafe Gnome or xterm I get the exact same problem. So I can only mount the disk as shown but not get the specific instance up to add packages (at least I don't know how to) such as out-lined in the DebuggingProgramCrash wiki page mentioned above. :(

[Ken Southerland (crowmagnumb)]

Update:

My co-worker taught me the magic of chroot. I mounted my hard drive after booting off the thumb drive and then did ...

cd <MOUNT_POINT>
sudo chroot .

And was then able to add a user to my install using adduser.
I *can* successfully log in as that user and then su - to my regular user. But I can't seem to figure out how to run gconf-cleaner since it gives me a "cannot open display" exception no matter what I export the display to. But if I run "sudo gconf-cleaner" it runs fine. But I don't know what file I'm cleaning as the results aren't clear at all as to what it operated on. But I still can't log in as my regular user.

I'm getting ready to just copy my files over to the new user I created and start over with system configuration with this new user and eventually delete the other. But I would *much* rather know how to fix this issue and get my old user back.

[Ken Southerland (crowmagnumb)]

UPDATE:
Solved and my problem had nothing to do with this mentioned error message as it turns out. Now I can log in and this CRITICAL message still appears in my syslog.

I first copied all of my system folders (hidden dot folders) out of the way and verified that I could log in and then carefully copied them back in a few chunks at a time, logging out and back in after each edit, and finally found the culprit to be my .profile!

Somehow, possibly by an accidental edit of mine(?), a line in it that set my PATH had got truncated leaving off the trailing important bits.

export PATH="<some_path_of_mine>:$PATH"

had become ...

export PATH="<some_path_of_mine>

... with no trailing $PATH or quotation mark.

I'm really surprised that this killed my login capabilities so drastically though!!! Wow.

Sorry for the false alarm on the G_VALUE_HOLDS_BOOLEAN(value)'failed message. Although I can safely say that the message is still coming up, but what harm it is doing I don't know. :)

[Alex (mestia)]

I also see this message in my syslog , but it kind of harmless for me .

Lucid (Amd64)

[Will (war59312)]

Same here on Ubuntu 10.10 Server.

[Marcelo Ruiz (marcelo-javier-ruiz-yahoo)]

Same here on Ubuntu 10.10 Desktop

[ticket (tickettothemoon2004)]

Same error message appears for me.

Ubuntu 10.10 desktop
kernel 2.6.35-28-generic
GNOME 2.32.0
i3 CPU, ASUS m/b

[jupeter (piotr-plenik)]

I have same problem in my up-to-date Ubuntu 11.04 Desktop (i386).
 - kernel: 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:50 UTC 2011 i686 i686 i386 GNU/Linux
 - gnome 2.32.1

When I logout from GDM, I cannot login again.
In syslog i have error:
 gdm-session-worker[1203]: GLib-GObject-CRITICAL: g_value_get_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

[SamLittley (supersam-littley)]

I'm getting this on a fully updated natty system;

May 15 22:03:02 sml-laptop gdm-simple-greeter[25739]: Gtk-WARNING: /build/buildd/gtk+2.0-2.24.4/gtk/gtkwidget.c:5687: widget not within a GtkWindow
May 15 22:03:02 sml-laptop gdm-simple-greeter[25739]: WARNING: Unable to load CK history: no seat-id found
May 15 22:03:04 sml-laptop gdm-session-worker[25741]: GLib-GObject-CRITICAL: g_value_get_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed
May 15 22:03:07 sml-laptop gdm-session-worker[25741]: pam_sm_authenticate: Called
May 15 22:03:07 sml-laptop gdm-session-worker[25741]: pam_sm_authenticate: username = [samuel]

just crashes gdm, but it restarts and i can use it

[Gtmoraes1 (gtmoraes1)]

I'm getting this too. Its totally random. Might not happen a entire week, might happen 50 times one day.
Today it occurred on me during one presentation. Twice. Total mood breaker and "linux sucks" comments

[Ryan Kaskel (ryankaskel)]

This also happens to me, seemingly at random. In my logs:

Jun 1 10:57:22 ryan-laptop gdm-simple-greeter[28594]: Gtk-WARNING: /build/buildd/gtk+2.0-2.24.4/gtk/gtkwidget.c:5687: widget not within a GtkWindow
Jun 1 10:57:22 ryan-laptop gdm-simple-greeter[28594]: WARNING: Unable to load CK history: no seat-id found
Jun 1 10:57:23 ryan-laptop gdm-session-worker[28597]: GLib-GObject-CRITICAL: g_value_get_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed
Jun 1 10:57:26 ryan-laptop gdm-session-worker[28597]: pam_sm_authenticate: Called
Jun 1 10:57:26 ryan-laptop gdm-session-worker[28597]: pam_sm_authenticate: username = [ryan]

It never happens "50 times one day," but it might happen 0-4 times per day. I can't find any usage patterns that reliably cause GDM to restart like that.

I am using "Classic mode."

Is there anything else I can post to help resolve this bug?

Thanks,
Ryan

[cyba (marcus-kempe)]

In the middle of doing nothing special, GDM completely died. But it was possible to login again afterwards without restart.

Jun 16 08:43:56 nibbler ovpn-marcus_nibbler[1464]: write UDPv4 []: Network is unreachable (code=101)
Jun 16 08:44:01 nibbler gdm-session-worker[11190]: GLib-GObject-CRITICAL: g_value_get_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed
Jun 16 08:44:04 nibbler NetworkManager[1265]: <error> [1308206644.457122] [nm-manager.c:1317] user_proxy_init(): could not init user settings proxy: (3
) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name
Jun 16 08:44:04 nibbler NetworkManager[1265]: <error> [1308206644.472980] [nm-manager.c:1317] user_proxy_init(): could not init user settings proxy: (3
) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name
Jun 16 08:44:04 nibbler rtkit-daemon[2118]: Successfully made thread 11350 of process 11350 (n/a) owned by '1000' high priority at nice level -11.
Jun 16 08:44:04 nibbler rtkit-daemon[2118]: Supervising 6 threads of 2 processes of 2 users.
Jun 16 08:44:04 nibbler pulseaudio[11350]: pid.c: Stale PID file, overwriting.
Jun 16 08:43:56 nibbler ovpn-marcus_nibbler[1464]: write UDPv4 []: Network is unreachable (code=101)
Jun 16 08:44:01 nibbler gdm-session-worker[11190]: GLib-GObject-CRITICAL: g_value_get_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed
Jun 16 08:44:04 nibbler NetworkManager[1265]: <error> [1308206644.457122] [nm-manager.c:1317] user_proxy_init(): could not init user settings proxy: (3
) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name
Jun 16 08:44:04 nibbler NetworkManager[1265]: <error> [1308206644.472980] [nm-manager.c:1317] user_proxy_init(): could not init user settings proxy: (3
) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name
Jun 16 08:44:04 nibbler rtkit-daemon[2118]: Successfully made thread 11350 of process 11350 (n/a) owned by '1000' high priority at nice level -11.
Jun 16 08:44:04 nibbler rtkit-daemon[2118]: Supervising 6 threads of 2 processes of 2 users.
Jun 16 08:44:04 nibbler pulseaudio[11350]: pid.c: Stale PID file, overwriting.

Linux nibbler 2.6.35-28-generic #50-Ubuntu SMP Fri Mar 18 18:42:20 UTC 2011 x86_64 GNU/Linux
Ubuntu 10.10

[mauricep (pigaht)]

I have exactly the same message on Mint 11. Gnome crashes and returns me to the login screen. It seems to happen at random.

A discussion on the Ubuntu fora here http://ubuntuforums.org/showthread.php?t=1757487 suggests that it might have something to do with Chromium. Anyone here using another browser but still getting this crash?

Maurice

[Mooky (matthieu-gerthoffer)]

Same entry in syslog with Ubuntu 10.04 (i386 - kernel 2.6.31-11-rt), but no specific issue observed with gdm or X (gdm configured to perform autologin with a xfce session). This "CRITICAL" log entry is logged on every boot.
I tried gconf-cleaner as mentioned by dino99 but this did not help.
This bug does not seem to be reported in the gdm bug tracker.

[Vipin Nambiar (vipnambiar)]

On my Natty machine, I experience the same bug when I click on the Title Bar of VLC while a video is played. The gdm crashes and am presented with a login screen. On logging in I log in to a fresh new session with none of my earlier applications running. This issue is reproduced while trying to play videos in any of the other applications like Banshee, movie player etc

[dino99 (9d9)]

Oneiric a3 i386 + lightdm : this error is flooding xsession-errors
So gdm is not the faulty package.

[toxic (gaiduri)]

Lucid - no bug
Maverick - upgrade from Lucid - bug

Both of these machines use the nvidia driver.

The reproduction, at least for me, is quite simple; open qtconfig-qt4 and try to change a dropdown, like GUI Style. Open VLC, and almost any activity that involves input widgets will cause the session to terminate immediately. I tried creating a new user and reproduced the issue in the same manner, using qtconfig, so I don't believe it to be related to some stale/corrupt config.

I have seen various posts in various places that suggest xinerama/twinview to be the problem. I also note that despite the fact that I have the same failed assertion, and almost everything noted in #23, this issue appears as though it may have been hijacked.

Can any of you that have reported GDM session termination please try the qtconfig reproduction? If that does indeed reliably reproduce this issue does anyone have an idea how to proceed?

john

[dino99 (9d9)]

this has been fixed a while back it seems.