Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#57125 - [telegram-desktop] Crash on initialization

Attached to Project: Community Packages
Opened by Reynaldo Allan Fulin (AllanDaemon) - Wednesday, 17 January 2018, 04:38 GMT
Last edited by Balló György (City-busz) - Wednesday, 17 January 2018, 11:22 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: The application crashes on initialization

This behavior begins after I updated the system, including this package.

* package version(s): 1.2.6-4 (on a fully updated system)

The terminal output (I removed the usual "Gtk-WARNING **: Theme parsing error" for the sake of clarity):

$ telegram-desktop
(...)
(telegram-desktop:29631): GLib-GObject-WARNING **: cannot register existing type 'GdkDisplayManager'
(telegram-desktop:29631): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed
(telegram-desktop:29631): GLib-GObject-CRITICAL **: g_object_new_with_properties: assertion 'G_TYPE_IS_OBJECT (object_type)' failed
(telegram-desktop:29631): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(telegram-desktop:29631): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(telegram-desktop:29631): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(telegram-desktop:29631): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(telegram-desktop:29631): GLib-GObject-WARNING **: cannot register existing type 'GdkDisplay'
(telegram-desktop:29631): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed
(telegram-desktop:29631): GLib-GObject-CRITICAL **: g_type_register_static: assertion 'parent_type > 0' failed
(telegram-desktop:29631): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed
(telegram-desktop:29631): GLib-GObject-CRITICAL **: g_object_new_with_properties: assertion 'G_TYPE_IS_OBJECT (object_type)' failed
[1] 29631 segmentation fault (core dumped) telegram-desktop
This task depends upon

Closed by  Balló György (City-busz)
Wednesday, 17 January 2018, 11:22 GMT
Reason for closing:  Fixed
Additional comments about closing:  telegram-desktop 1.2.6-5
Comment by Reynaldo Allan Fulin (AllanDaemon) - Wednesday, 17 January 2018, 04:56 GMT
One more important info: I removed all orphan packages also on the update, including the libappindicator-gtk3. I just found this https://bugs.archlinux.org/task/56803 that is related but don't seem to be fixed.
Comment by Doug Newgard (Scimmia) - Wednesday, 17 January 2018, 04:59 GMT
So if you install libappindicator-gtk3 it works again?
Comment by Balló György (City-busz) - Wednesday, 17 January 2018, 11:21 GMT
Somehow the application tries to load both gtk2 and gtk3 at the same time, which causes this problem. Now I removed the gtk2 loading code in version 1.2.6-5, which should fix the problem, and libappindicator-gtk3 doesn't need to be installed.

Loading...