Bug 1378003

contents of attachment for easier viewing:



(quassel:20631): GLib-GObject-WARNING **: cannot register existing type 'GdkDisplayManager'

(quassel:20631): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

(quassel:20631): GLib-GObject-CRITICAL **: g_object_new: assertion 'G_TYPE_IS_OBJECT (object_type)' failed

(quassel:20631): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(quassel:20631): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(quassel:20631): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(quassel:20631): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(quassel:20631): GLib-GObject-WARNING **: cannot register existing type 'GdkDisplay'

(quassel:20631): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

(quassel:20631): GLib-GObject-CRITICAL **: g_type_register_static: assertion 'parent_type > 0' failed

(quassel:20631): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

(quassel:20631): GLib-GObject-CRITICAL **: g_object_new: assertion 'G_TYPE_IS_OBJECT (object_type)' failed
^CCaught signal 2 - exiting.
Segmentation fault (core dumped)


Based on the output, it could be style/theme related

1.  under what DE are you running quassel?

2.  try running as:
quassel --style plastique
to see if current style is the problem or not, does it still not start?

1. I'm runnig Quassel under Gnome Shell.

2. I get this error message: 

quassel --style plastique

(quassel:6138): GLib-GObject-WARNING **: cannot register existing type 'GdkDisplayManager'

(quassel:6138): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

(quassel:6138): GLib-GObject-CRITICAL **: g_object_new: assertion 'G_TYPE_IS_OBJECT (object_type)' failed

(quassel:6138): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(quassel:6138): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(quassel:6138): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(quassel:6138): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(quassel:6138): GLib-GObject-WARNING **: cannot register existing type 'GdkDisplay'

(quassel:6138): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

(quassel:6138): GLib-GObject-CRITICAL **: g_type_register_static: assertion 'parent_type > 0' failed

(quassel:6138): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

(quassel:6138): GLib-GObject-CRITICAL **: g_object_new: assertion 'G_TYPE_IS_OBJECT (object_type)' failed
^CCaught signal 2 - exiting.
Segmentation fault (core dumped)
[sylvia@Amsterdam ~]$ 


But that's maybe because I don't have that style in my desktop.

A user in #quassel reported possibly similar issues running on a fresh install of Workstation (i.e. GNOME):

<Fish-Face> so there are two issues I've had: firstly setting it to use the GTK style crashes on startup, and secondly opening the font picker (whcih I assume is a GTK dialogue here) crashes it

<Fish-Face> however, the latter error gives different output, it starts with: (quasselclient:5212): Gtk-WARNING **: Unknown type PangoFontFamily specified in treemodel model

I couldn't reproduce this on KDE, however, so I installed a Fedora 24 Workstation VM. I could confirm that toggling the theme to GTK+ caused a crash.

I was suspicious of https://fedoraproject.org/wiki/Changes/QGnomePlatform, and so removed qgnomeplatform. After doing so, quassel worked fine. Reinstalling qgnomeplatform and the crash came back. The user in #quassel confirmed that this fixed things for him as well.

As a workaround, does uninstalling qgnomeplatform (i.e. "dnf remove qgnomeplatform") solve the issue?

The problem with gtk+ has been solved more than 3 months ago. Previously we had fallback to gtk+ style when adwaita-qt wasn't present, right now the fallback is fusion style. Anyway, adwaita-qt is highly recommended and supported style.

The crash in font dialog is a known bug for us, we just didn't get to it yet.

$ uname -r
4.8.15-200.fc24.x86_64


Hey just dropping in. I think I hit this.

Steps:
1. Opened Quassel
2. pressed F7 to open Settings Menu
3. clicked checkbox to select custom font.
4. clicked on the "Choose" button

Jan  1 09:57:15 demacia quassel.desktop: (quassel:13874): Gtk-WARNING **: Unknown type PangoFontFamily specified in treemodel model
Jan  1 09:57:15 demacia quassel.desktop: (quassel:13874): Gtk-WARNING **: Unknown type PangoFontFace specified in treemodel model
Jan  1 09:57:15 demacia quassel.desktop: (quassel:13874): Gtk-WARNING **: gtkliststore.c:516: Invalid type (null)
Jan  1 09:57:15 demacia quassel.desktop: (quassel:13874): Gtk-WARNING **: gtkliststore.c:516: Invalid type (null)
Jan  1 09:57:15 demacia quassel.desktop: (quassel:13874): GLib-GObject-CRITICAL **: g_value_type_transformable: assertion 'G_TYPE_IS_VALUE (src_type)' failed
Jan  1 09:57:15 demacia quassel.desktop: (quassel:13874): GLib-GObject-CRITICAL **: g_value_type_transformable: assertion 'G_TYPE_IS_VALUE (src_type)' failed
Jan  1 09:57:15 demacia quassel.desktop: (quassel:13874): GLib-GObject-WARNING **: gtype.c:4273: type id '0' is invalid
Jan  1 09:57:15 demacia quassel.desktop: (quassel:13874): GLib-GObject-WARNING **: can't peek value table for type '<invalid>' which is not currently referenced
Jan  1 09:57:15 demacia quassel.desktop: #  0 quassel              0x0000564c2078f96c Quassel::logBacktrace(QString const&)
Jan  1 09:57:15 demacia quassel.desktop: #  1 quassel              0x0000564c20767299 Quassel::handleSignal(int)
Jan  1 09:57:15 demacia quassel.desktop: #  2 libc.so.6            0x00007f5189eb27e0 0x0000000000000000
Jan  1 09:57:15 demacia quassel.desktop: #  3 libQt5Core.so.5      0x00007f518ad5764d QObject::disconnect(QObject const*, char const*, QObject const*, char const*)
Jan  1 09:57:15 demacia quassel.desktop: #  4 libQt5DBus.so.5      0x00007f51911c65b0 0x0000000000000000
Jan  1 09:57:15 demacia quassel.desktop: #  5 libQt5DBus.so.5      0x00007f51911b3672 0x0000000000000000
Jan  1 09:57:15 demacia quassel.desktop: #  6 libQt5Core.so.5      0x00007f518ab8d9ba 0x0000000000000000
Jan  1 09:57:15 demacia quassel.desktop: #  7 libpthread.so.0      0x00007f5189c695ca 0x0000000000000000
Jan  1 09:57:15 demacia quassel.desktop: #  8 libc.so.6            0x00007f5189f810ed clone

qgnomeplatform-0.2-13.20161205git.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-139caa9469

qgnomeplatform-0.2-13.20161205git.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-0cb287ff1d

qgnomeplatform-0.2-13.20161205git.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-139caa9469

qgnomeplatform-0.2-13.20161205git.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-0cb287ff1d

qgnomeplatform-0.2-13.20161205git.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.

qgnomeplatform-0.2-13.20161205git.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.