[Touch-packages] [Bug 1852911] Re: CriticalPowerAction=Suspend should be supported
I would like to add my voice here and say that a patch, either to upstream UPower or to Ubuntu's version would be much appreciated. I've lost work several times as neither HybridSleep nor Hibernate work on my laptop so it simply shuts down, and due to a quirk of the batter management the delay between the notification of low % and then the critical threshold and shutdown is often only mere seconds. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1852911 Title: CriticalPowerAction=Suspend should be supported Status in Upower: New Status in upower package in Ubuntu: Triaged Bug description: The action to take when the battery is critical can only be one of the following: # Possible values are: # PowerOff # Hibernate # HybridSleep Adding Suspend to that list makes perfect sense. My laptop is currently powering off on low power which is useless as I'll be losing my work anyway. Might as well suspend and allow me to notice that and connect a charger. If the thinking is that suspend uses power I can set a high enough threshold to give me some margin. The failovers are: # If HybridSleep isn't available, Hibernate will be used # If Hibernate isn't available, PowerOff will be used I'd argue Suspend should actually come before PowerOff in that list. For most laptop users having their computer suspend because they didn't notice the battery was running out is very easy to fix and takes no time. They'll just connect the charger. If however the computer needs to be completely rebooted, not only does that take a lot more time it will very likely cause lost work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: upower 0.99.10-1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 17 14:32:13 2019 InstallationDate: Installed on 2019-05-09 (191 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1852911/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1808508] Re: Valgrind doesn't work in disco [Fatal error at startup: a function redirection which is mandatory for this platform-tool combination cannot be set up.]
> we can't think of anything besides gdb, valgrind, and libunwind that uses /usr/lib/debug That seems like quite an incredible statement! I can imagine that many debugging and profiling tools will want symbols. For example, this change is breaking perf right now, as it looks for say libc symbols in /usr/lib/debug/usr/lib/x86_64-linux-gnu/, but the symbols are actually in /usr/lib/debug/lib/x86_64-linux-gnu/. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1808508 Title: Valgrind doesn't work in disco [Fatal error at startup: a function redirection which is mandatory for this platform-tool combination cannot be set up.] Status in base-files package in Ubuntu: Won't Fix Status in valgrind package in Ubuntu: Fix Released Bug description: $ valgrind /bin/ls ==25995== Memcheck, a memory error detector ==25995== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==25995== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info ==25995== Command: /bin/ls ==25995== valgrind: Fatal error at startup: a function redirection valgrind: which is mandatory for this platform-tool combination valgrind: cannot be set up. Details of the redirection are: valgrind: valgrind: A must-be-redirected function valgrind: whose name matches the pattern: strlen valgrind: in an object with soname matching: ld-linux-x86-64.so.2 valgrind: was not found whilst processing valgrind: symbols from the object with soname: ld-linux-x86-64.so.2 valgrind: valgrind: Possible fixes: (1, short term): install glibc's debuginfo valgrind: package on this machine. (2, longer term): ask the packagers valgrind: for your Linux distribution to please in future ship a non- valgrind: stripped ld.so (or whatever the dynamic linker .so is called) valgrind: that exports the above-named function using the standard valgrind: calling conventions for this platform. The package you need valgrind: to install for fix (1) is called valgrind: valgrind:On Debian, Ubuntu: libc6-dbg valgrind:On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo valgrind: valgrind: Note that if you are debugging a 32 bit process on a valgrind: 64 bit system, you will need a corresponding 32 bit debuginfo valgrind: package (e.g. libc6-dbg:i386). valgrind: valgrind: Cannot continue -- exiting now. Sorry. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: valgrind 1:3.14.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 Date: Fri Dec 14 17:06:03 2018 InstallationDate: Installed on 2018-12-04 (10 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: valgrind UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1808508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1622571] Re: NetworkManager crashed with SIGSEGV in nm_dns_manager_end_updates()
I believe I'm also having this problem. I've uploaded the whoopsie dump with apport but I can't see where it is being tracked (see http://askubuntu.com/questions/900191/where-do-i-look-to-see-if-my- whoopsie-is-being-tracked). The stack looks the same: SegvAnalysis: Segfault happened at: 0x7fc79f90e830 <__libc_start_main+240>: mov%eax,%edi PC (0x7fc79f90e830) ok source "%eax" ok destination "%edi" ok SP (0x7ffc12fba2c0) ok Reason could not be automatically determined. SourcePackage: network-manager Stacktrace: #0 0x0048cc66 in nm_dns_manager_end_updates () #1 0x7fc79d566e40 in ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 #2 0x7fc79d5668ab in ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 #3 0x7fc7a01f5cf5 in g_cclosure_marshal_generic_va () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #4 0x7fc7a01f51d4 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #5 0x7fc7a020f9a6 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x7fc7a021008f in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 This started happening when I commented out the dns=dnsmasq line in my NetworkManager.conf and indeed the crash happens in DNS related code. The often occurs after resuming from suspend, but not always - it may also just occur while using the host. Here's a link to the whoopise upload - I don't have perms to see it, but perhaps someone who does can associate it with this bug? https://errors.ubuntu.com/oops/f3ce1fb0-1957-11e7-968c-fa163e8d4bab -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1622571 Title: NetworkManager crashed with SIGSEGV in nm_dns_manager_end_updates() Status in network-manager package in Ubuntu: Confirmed Bug description: it appeared right after boot, but I do use a 4.8 kernel.. Linux jaypc 4.8.0-040800rc1-generic #201608072231 SMP Mon Aug 8 02:33:57 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.2-0ubuntu8 Uname: Linux 4.6.0-040600-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Thu Sep 8 09:01:03 2016 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-04 (160 days ago) InstallationMedia: It IpRoute: default via 192.168.11.1 dev enp3s0 proto static metric 100 169.254.0.0/16 dev enp3s0 scope link metric 1000 192.168.11.0/24 dev enp3s0 proto kernel scope link src 192.168.11.20 metric 100 IwConfig: lono wireless extensions. enp3s0no wireless extensions. NetworkManager.conf: [main] plugins=ifupdown,keyfile,ofono [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcEnviron: LANG=nl_NL.UTF-8 PATH=(custom, no user) RfKill: Can't open RFKILL control device: No such file or directory Signal: 11 SourcePackage: network-manager StacktraceTop: nm_dns_manager_end_updates () ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic_va () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: NetworkManager crashed with SIGSEGV in nm_dns_manager_end_updates() UpgradeStatus: Upgraded to yakkety on 2016-05-20 (115 days ago) UserGroups: nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 83b55d9f-56b0-3de7-8781-b60ac02d32da 802-3-ethernet 1473679209 ma 12 sep 2016 13:20:09 CEST yes 4294966297no /org/freedesktop/NetworkManager/Settings/1 yes enp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/0 NETGEAR74 2508a31f-ca9b-47cc-a9e3-8f5be4686282 802-11-wireless 1463994465 ma 23 mei 2016 11:07:45 CEST yes 0 no /org/freedesktop/NetworkManager/Settings/0 no -- -- -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp3s0 ethernet connected /org/freedesktop/NetworkManager/Devices/0 Wired connection 1
