[Desktop-packages] [Bug 1867996] [NEW] Segfault in app_indicator_set_icon_full [patch attached]
Public bug reported: Discord and several other applications using libappindicator are widely reported to have been crashing for several years. See: https://github.com/flathub/com.discordapp.Discord/issues/30 (and others) This is the backtrace: (gdb) bt full #0 0x7fe1d5d2e00e in () at /app/lib/libappindicator.so #1 0x7fe1f5a6f3c5 in g_closure_invoke () at /lib/libgobject-2.0.so.0 #2 0x7fe1f5a813d2 in () at /lib/libgobject-2.0.so.0 #3 0x7fe1f5a8a02c in g_signal_emit_valist () at /lib/libgobject-2.0.so.0 #4 0x7fe1f5a8a40f in g_signal_emit () at /lib/libgobject-2.0.so.0 #5 0x7fe1d5d2ed4f in app_indicator_set_icon_full () at /app/lib/libappindicator.so #6 0x0077851a in () #7 0x01de7123 in () #8 0x01e4bd4e in () #9 0x01e6e34c in () #10 0x01e6e668 in () #11 0x01e6e9cb in () #12 0x01df971a in () #13 0x7fe1f354b1c7 in g_main_context_dispatch () at /lib/libglib-2.0.so.0 #14 0x7fe1f354b430 in () at /lib/libglib-2.0.so.0 #15 0x7fe1f354b4dc in g_main_context_iteration () at /lib/libglib-2.0.so.0 #16 0x01df9606 in () #17 0x01e6e0e7 in () #18 0x01e29570 in () #19 0x00c37ec8 in () #20 0x00c37d15 in () #21 0x00c1da7d in () #22 0x00a9282e in () #23 0x007892d4 in () #24 0x007896e0 in () #25 0x03b830a3 in main () Happens in all versions of libappindicator built from latest sources available on launchpad. I ran into the issue yesterday when installing Discord for the first time. I have tracked the problem down to libappindicator passing in an extra vararg item to g_signal_emit that the signal's definition in libappindicator was not declaring, causing the crash you see above in gobject's g_signal dispatch machinery. Patch is attached. I am presuming this is 'upstream' for libappindicator, whatever that may mean for what appears to be an unmaintained project. If it is not, and since it is an Ubuntu/Canonical-sourced project originally, I respectfully request that you assist in upstreaming it since this bug is causing severe breakage for users across all distros. ** Affects: libappindicator (Ubuntu) Importance: Undecided Status: New ** Affects: libappindicator (Arch Linux) Importance: Undecided Status: New ** Patch added: "Stop passing in undeclared boolean vararg" https://bugs.launchpad.net/bugs/1867996/+attachment/5338540/+files/segfault-fix.patch ** Also affects: libappindicator (Arch Linux) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libappindicator in Ubuntu. https://bugs.launchpad.net/bugs/1867996 Title: Segfault in app_indicator_set_icon_full [patch attached] Status in libappindicator package in Ubuntu: New Status in libappindicator package in Arch Linux: New Bug description: Discord and several other applications using libappindicator are widely reported to have been crashing for several years. See: https://github.com/flathub/com.discordapp.Discord/issues/30 (and others) This is the backtrace: (gdb) bt full #0 0x7fe1d5d2e00e in () at /app/lib/libappindicator.so #1 0x7fe1f5a6f3c5 in g_closure_invoke () at /lib/libgobject-2.0.so.0 #2 0x7fe1f5a813d2 in () at /lib/libgobject-2.0.so.0 #3 0x7fe1f5a8a02c in g_signal_emit_valist () at /lib/libgobject-2.0.so.0 #4 0x7fe1f5a8a40f in g_signal_emit () at /lib/libgobject-2.0.so.0 #5 0x7fe1d5d2ed4f in app_indicator_set_icon_full () at /app/lib/libappindicator.so #6 0x0077851a in () #7 0x01de7123 in () #8 0x01e4bd4e in () #9 0x01e6e34c in () #10 0x01e6e668 in () #11 0x01e6e9cb in () #12 0x01df971a in () #13 0x7fe1f354b1c7 in g_main_context_dispatch () at /lib/libglib-2.0.so.0 #14 0x7fe1f354b430 in () at /lib/libglib-2.0.so.0 #15 0x7fe1f354b4dc in g_main_context_iteration () at /lib/libglib-2.0.so.0 #16 0x01df9606 in () #17 0x01e6e0e7 in () #18 0x01e29570 in () #19 0x00c37ec8 in () #20 0x00c37d15 in () #21 0x00c1da7d in () #22 0x00a9282e in () #23 0x007892d4 in () #24 0x007896e0 in () #25 0x03b830a3 in main () Happens in all versions of libappindicator built from latest sources available on launchpad. I ran into the issue yesterday when installing Discord for the first time. I have tracked the problem down to libappindicator passing in an extra vararg item to g_signal_emit that the signal's definition in libappindicator was not declaring, causing the crash you see above in gobject's g_signal dispatch machinery. Patch is attached. I am presuming this is 'upstream' for libappindicator, whatever that may mean for what appears to be an unmaintained
[Desktop-packages] [Bug 303862] Re: Pidgin freezes when generating new OTR private key
I also experienced the bug (13.10, Pidgin 2.10.7 (libpurple 2.10.7), pidgin-otr 4.0.0-1). After doing some research I think I can conclude that the reason must be that Pidgin tries to get the initialization randomness from /dev/random and stalls until /dev/random delivers sufficient data. For me pidgin unfreezes after typing random data into an arbitrary text field for a few minutes to produce entropy for /dev/random. It would be adviseable to give a hint to the user as to what pidgin is waiting for, and how he can speed up the process (like using mouse/keyboard/whatever devices feed entropy to /dev/random). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/303862 Title: Pidgin freezes when generating new OTR private key Status in Off-the-Record Messaging plugin for pidgin: New Status in “pidgin” package in Ubuntu: Invalid Status in “pidgin-otr” package in Ubuntu: Confirmed Bug description: Binary package hint: pidgin Package: pidgin-otr (Intrepid) 3.2.0-1 Version of Ubuntu: Ubuntu 8.10 (Intrepid) Systems used: AMD XP 3200+, 1 GB DDR, 160 GB HDD running Ubuntu 8.10 HP dv9500t laptop, 2.0 Ghz Core 2 Duo, 2 GB DDR, 160 GB HDD running of Ubuntu 8.10 LiveCD When I enable the pidgin-otr plugin and attempt to generate a new private key, Pidgin pops up a dialog box telling me that a new private key is being generated. However, key generation never completes and eventually I receive a notification that Pidgin or Generating Private Key is not responding. I have attempted to generate keys for both a XMPP (GMail Account) and an AIM account with the same result, and have repeated the process on both systems multiple times. I have successfully generated keys using the same version of OTR on Windows XP SP3 on the HP dv9500t laptop. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 8.10 ExecutablePath: /usr/bin/pidgin Package: pidgin 1:2.5.2-0ubuntu1 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pidgin Uname: Linux 2.6.27-9-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/pidgin-otr/+bug/303862/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
