[Bug 1966610] Re: smartctl assert failure: free(): invalid pointer

2022-06-03 Thread Utkarsh Gupta
** Changed in: smartmontools (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966610 Title: smartctl assert failure: free(): invalid pointer To manage notificat

[Bug 1966610] Re: smartctl assert failure: free(): invalid pointer

2022-05-27 Thread Launchpad Bug Tracker
[Expired for smartmontools (Ubuntu) because there has been no activity for 60 days.] ** Changed in: smartmontools (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net

[Bug 1966610] Re: smartctl assert failure: free(): invalid pointer

2022-03-28 Thread Vladimir
It fails ones after reboot, and after that it repeats without error. free(): invalid pointer Program received signal SIGABRT, Aborted. __pthread_kill_implementation (no_tid=0, signo=6, threadid=140737347295296) at ./nptl/pthread_kill.c:44 44 ./nptl/pthread_kill.c: Нет такого файла или катал

[Bug 1966610] Re: smartctl assert failure: free(): invalid pointer

2022-03-28 Thread Vladimir
I managed to reproduce the error. The full listing: sudo smartctl -x /dev/nvme1 [sudo] пароль для vkovalen: smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.0-23-generic] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION ==

[Bug 1966610] Re: smartctl assert failure: free(): invalid pointer

2022-03-28 Thread Vladimir
apport information ** Tags added: apport-collected ** Description changed: smartctl -x crashed with SPCC M.2 PCIe SSD 2 Tb under /dev/nvme1n1p1 executed command: sudo smartctl -x /dev/nvme1 | grep Temp very rare. hard to reproduce. ubuntu 22.04 smartmontools 7.2-1build1 ProblemTyp

[Bug 1966610] Re: smartctl assert failure: free(): invalid pointer

2022-03-28 Thread Lena Voytek
Thank you for taking the time to report this bug and help make Ubuntu better. I tried reproducing the error but was unable to after multiple tries, which makes sense as you stated it was very rare. Have you seen this happen multiple times, and is there any additional information you have about the