** Changed in: gsmartcontrol (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789454
Title:
gsmartcontrol immediately crashes while running smartctl
Well, looks like the patched version is synced from Debian to Jammy by
now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789454
Title:
gsmartcontrol immediately crashes while running smartctl
To
** Changed in: gsmartcontrol (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789454
Title:
gsmartcontrol immediately crashes while running smartctl
** Also affects: gsmartcontrol (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942427
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
No, they all have the same version as in Focal, 1.1.3-2build1.
However, I've uploaded the patch to Debian bug report, and today the
patched version was uploaded to Debian Unstable. So it will be synced to
Jammy sooner or later.
https://bugs.debian.org/942427
** Bug watch added: Debian Bug
Thanks for working on this, has this been fixed in releases later than
Ubuntu 20.04?
** Changed in: gsmartcontrol (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789454
Title:
gsmartcontrol immediately crashes while running smartctl
To manage notifications about this bug go to:
[Impact]
GSmartControl segfaults on start while scanning devices, making
the app useless. According to the upstream author, it happens due to
using some incomplete data while rendering the icons (the device scan
triggers that process).
The patch from the upstream commit fixes it, so it would be
** Attachment added: "Debdiff with the fix for Focal"
https://bugs.launchpad.net/ubuntu/+source/gsmartcontrol/+bug/1789454/+attachment/5557051/+files/gsmartcontrol-debdiff-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The desktop environment only matters for triggering the crash: it's a
random crash, it's been happening for years in various distros with
various desktops. It's already fixed in GSmartControl upstream.
https://github.com/ashaduri/gsmartcontrol/issues/13
Sorry to disappoint you :-)
But I am grateful you did not respond with the standard "tell it to your
own distro", thanks!
But since you can reproduce with 20.3 MATE as the desktop, this means
it's not about Cinnamon...
--
You received this bug notification because you are a member of Ubuntu
Ah, I hoped it would be some Ubuntu release, to make a test case for SRU. [1]
So far, I can reproduce it either in Mint 20.3 (with MATE 1.26) or in Ubuntu
MATE 20.04 with Fresh MATE PPA added [2] (again, for MATE 1.26). Not sure if a
PPA would be allowed for SRU testing, though I can try.
[1]
And some add'l info: These crashes only occur since I got version 1.1.3,
which I got when I upgraded from Sonya to Tara. I cannot reproduce which
version of gsmartcontrol was present on Sonya. But I do see that the
command line version (smartctl 7.0 2018-12-30 r4883) doesn't crash, and
I can
I do not have Ubuntu as such. I have Linux Mint (I know, now comes the
standard answer "tell this your distro", but Mint draws this directly
from Ubuntu repos.
My Mint is 20.1 (Tara), the repo is Ubuntu (archive.ubuntu.com/ubuntu),
Bionic. Drawn from Universe, version is 1.1.3-1, which is
Guys, if you can still reproduce this crash in Ubuntu 20.04 and later,
please tell your version of Ubuntu and the desktop environment you have.
The desktop environment itself isn't the cause for the crash, it's just
that some desktops in some Ubuntu versions trigger the crash and some
don't. It's
Version 1.1.3 crashes for me, too (access violation). The crash happens
when scanning is performed. If launched from command line with parameter
--no-scan, it does not crash. However, you cannot do anything useful.
When you start a manual scan, it crashes immediately. Also, smartctl
works fine...
It was working fine for me a couple of months ago. Not it crashes with a
segmentation fault.
-
george@george-Ryzen:~$ gsmartcontrol
[hz] Warning: exit: Device open failed, or device did not return an
IDENTIFY
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gsmartcontrol (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789454
As of Nov 2019, I'm getting the same crash bug, ran it through gdb and
it crashes in the same place.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789454
Title:
gsmartcontrol immediately crashes
19 matches
Mail list logo
