Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
** Changed in: gdm
Status: Unknown => Expired
** Changed in: gdm
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1740522
Title:
GLib:
If this bug is a problem for you then please ask the gdm developers to
prioritize it here:
https://bugzilla.gnome.org/show_bug.cgi?id=792236
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
I have the same problem after upgrading ubuntu from 17.10 to 18.04. And GUI
doesn't start.
What should I do?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1740522
Title:
GLib:
I have this bug on Ubuntu 18.04. My log for gdm3:
Mar 19 09:50:59 hostname systemd[1]: Stopping GNOME Display Manager...
Mar 19 09:50:59 hostname gdm3[1081]: Freeing conversation 'gdm-password' with
active job
Mar 19 09:50:59 hostname gdm3[1081]: Child process -1118 was already dead.
Mar 19
That is highly likely unrelated to the log messages we're talking about.
Please ensure your two issues have two different bug reports.
** Also affects: gdm via
https://bugzilla.gnome.org/show_bug.cgi?id=792236
Importance: Unknown
Status: Unknown
--
You received this bug
> 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
Thanks. Confirmed, but it doesn't seem to be causing any serious problem
right now (?)
I can see the error against gdm3 in Ubuntu 18.04 too, by running:
journalctl /usr/sbin/gdm3
** Changed in: gdm3 (Ubuntu)
Importance: Undecided => Low
** Changed in: gdm3 (Ubuntu)
Status:
Next step: Please report the issue to the GDM developers using this
link:
https://bugzilla.gnome.org/enter_bug.cgi?product=gdm
And when done, tell us the ID of the newly-created bug.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
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
Probably both are true... A quick google shows many apps experiencing
that same assertion failure.
If you'd like to keep this bug about the gdm3 case then we'll need some
log file(s) (or screenshots?) of the problem being reported against
gdm3. I'm hoping for a little bit more contextual
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
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1740522
Title:
GLib:
Sounds like a problem with gnome-terminal:
Dec 27 12:51:56 hostname gnome-terminal-[5255]: g_variant_new_string: assertion
'string != NULL' failed
Dec 27 12:51:56 hostname gnome-terminal-[5255]: g_variant_new_variant:
assertion 'value != NULL' failed
Dec 27 12:51:56 hostname
14 matches
Mail list logo
