> but it doesn't seem to be causing any serious problem right now (?)
At the moment I have an issue where *sometimes* when I return to my
computer and the screen has gone to sleep, it takes an incredibly long
time to show me the login prompt.
Could be my graphics driver (polaris) or the login
It would be an easy fix if the assertion message printed the backtrace
of the apps calling in glib.
I wonder if the system packages are compiled in RelWithDbgInfo by
default, so that a stacktrace would be useful in release for fixing bugs
like this. I wonder if there's a way to extend G_DEBUG
I also saw many comments about this via the web, but didn't see any bugs
people could track the situation with.
The screenshot that informed my report is attached.
If there's any more information that will help find the root cause, I'm
happy to provide it.
** Attachment added: "Screenshot of
According to the Logs application, the sender of the message was gdm3,
so it seemed a reasonable guess.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740522
Title:
GLib: g_variant_new_string:
Public bug reported:
I saw this in the Logs application
gdm3
GLib: g_variant_new_string: assertion 'string != NULL' failed
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gdm3 3.26.1-3ubuntu3
Uname: Linux 4.14.7-041407-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
