[Dx-packages] [Bug 1575655] Re: the network indicator shows the wrong status
1) Question Mark ? In the status of Network Manager of Ubuntu Linux even though Network Get Connected…..! 2) In Ubuntu Linux Wrong Status of the Network Manager 3) Ubuntu Linux - Network Manager Status – Showing “?” 4) why does a question mark ? Appear in the status of Ubuntu Network Manager …. 5) wrong status in the Network Manager Indicator in Ubuntu Linux This status of Question Mark “?” Sign or a “?” indicator in the Network Manager Applet despite the network status connected “is not an error in Network Manager” you need to change the settings of connectivity checking to OFF How to get rid of that “?” Status in the nm-applet is goto Goto to Settings/Privacy/Connectivity Checking – and Switch it off. ** Attachment added: "Ubuntu Network Manger issue Showing "?"" https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1575655/+attachment/5355068/+files/Screenshot%20from%202020-04-16%2008-06-07.png -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-applet in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1575655 Title: the network indicator shows the wrong status Status in indicator-applet package in Ubuntu: Confirmed Bug description: Description: Ubuntu 16.04 LTS Release: 16.04 indicator-applet: Installed: (none) Candidate: 12.10.2+15.04.20141127.2-0ubuntu1 Version table: 12.10.2+15.04.20141127.2-0ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages The network indicator sometimes shows the icon for wired connections and sometimes claims wifi without connection even though I'm consistently connected over wifi. I don't mean to say that it switches between these two or that always is wrong. But sometimes my connected to wifi symbol changes to wired. Other times it will change to the no connection wifi. The info is correct on boot, but switches over time, possibly after suspension. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: indicator-applet (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 27 14:54:42 2016 InstallationDate: Installed on 2016-04-08 (18 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) SourcePackage: indicator-applet UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1575655/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()
** Also affects: accountsservice (Ubuntu Focal) Importance: High Assignee: Iain Lane (laney) Status: Triaged ** Changed in: accountsservice (Ubuntu Focal) Milestone: None => ubuntu-20.04.1 -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1843982 Title: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user() Status in accountsservice: New Status in accountsservice package in Ubuntu: Triaged Status in accountsservice source package in Focal: Triaged Status in accountsservice package in Debian: Confirmed Bug description: https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781 https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7 ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 14 10:29:16 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-05-24 (112 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=nb_NO.UTF-8 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0 g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1843982/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1867996] Re: Segfault in app_indicator_set_icon_full [patch attached]
Both patches have been applied, so no need for further bug. cfr https://bazaar.launchpad.net/~indicator-applet- developers/libappindicator/trunk/revision/295 -- You received this bug notification because you are a member of DX Packages, which is subscribed to libappindicator in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1867996 Title: Segfault in app_indicator_set_icon_full [patch attached] Status in libappindicator package in Ubuntu: Fix Released Status in libappindicator package in Arch Linux: New Bug description: [ Impact ] 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) [ Test case ] - Run discord application - It must not crash in ubuntu (or when indicators are enabled) [ Regression potential ] Very low, icons might not appear in some cases, if any. - 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1867996/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1872947] [NEW] The computer powers off even before the critical or low battery percentage is reached and no low power indication is shown. It shutsdown abruptly.
Public bug reported: The computer powers off even before the critical or low battery percentage is reached and no low power indication is shown. It shuts down abruptly. Tried to reinstall the package through apt to fix the problem, but no avail. This is most probably a bug in the indicator-power package. Info about release: OS Ubuntu Focal Fossa (development branch) GNOME Version3.36.1 OS Type 64 bit indicator-power: Installed: 12.10.6+17.10.20170829.1-0ubuntu5 Candidate: 12.10.6+17.10.20170829.1-0ubuntu5 Version table: *** 12.10.6+17.10.20170829.1-0ubuntu5 500 500 http://in.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: indicator-power 12.10.6+17.10.20170829.1-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 15:29:24 2020 InstallationDate: Installed on 2020-04-12 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-power (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1872947 Title: The computer powers off even before the critical or low battery percentage is reached and no low power indication is shown. It shutsdown abruptly. Status in indicator-power package in Ubuntu: New Bug description: The computer powers off even before the critical or low battery percentage is reached and no low power indication is shown. It shuts down abruptly. Tried to reinstall the package through apt to fix the problem, but no avail. This is most probably a bug in the indicator-power package. Info about release: OS Ubuntu Focal Fossa (development branch) GNOME Version3.36.1 OS Type 64 bit indicator-power: Installed: 12.10.6+17.10.20170829.1-0ubuntu5 Candidate: 12.10.6+17.10.20170829.1-0ubuntu5 Version table: *** 12.10.6+17.10.20170829.1-0ubuntu5 500 500 http://in.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: indicator-power 12.10.6+17.10.20170829.1-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 15:29:24 2020 InstallationDate: Installed on 2020-04-12 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1872947/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1867996] Re: Segfault in app_indicator_set_icon_full [patch attached]
This is getting far too confusing because multiple patches for multiple bugs are being conflated. I produced a fairly straightforward patch that fixed an issue I directly saw in people's backtraces, and other issues I identified that are similar. This is what this bug report is for. The later patch that supposedly fixes something else is not mine, hasn't been tested by me, purports to solve an issue I personally haven't seen in a way that has no similarities to the bug I opened this report for (other than it occurs in Discord as well). Please open a separate bug report with backtraces that demonstrate *that* problem, and with *that* patch attached. This avoids confusion and possible backing out of my patch together with the second, unrelated patch in case said unrelated patch has introduced a new problem. -- You received this bug notification because you are a member of DX Packages, which is subscribed to libappindicator in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1867996 Title: Segfault in app_indicator_set_icon_full [patch attached] Status in libappindicator package in Ubuntu: Fix Released Status in libappindicator package in Arch Linux: New Bug description: [ Impact ] 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) [ Test case ] - Run discord application - It must not crash in ubuntu (or when indicators are enabled) [ Regression potential ] Very low, icons might not appear in some cases, if any. - 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1867996/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp