Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GSmartControl fails to start. Errors and warnings in terminal. #2

Closed
aritorhamo opened this issue Mar 26, 2021 · 8 comments
Closed
Assignees
Labels
bug Something isn't working fixed The issue has been fixed

Comments

@aritorhamo
Copy link

Hello!

When I try to start GSmasrtControl, it crashes. I've been using it successfully before, but the last time I used it was quite a long time ago, so I don't know when the problem started. I get to "Scanning system, please wait...", but then the window disappears. When I try to start the program from the terminal, I get the following:
.........................
[gtk] _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’
[gtk] setenv()/putenv() are not thread-safe and should not be used after threads are created
[gtk] posix_spawn avoided (workdir specified) (fd close requested)
[gtk] setenv()/putenv() are not thread-safe and should not be used after threads are created
[gtk] setenv()/putenv() are not thread-safe and should not be used after threads are created
[gtk] posix_spawn avoided (workdir specified) (fd close requested)
[gtk] setenv()/putenv() are not thread-safe and should not be used after threads are created
[hz] Warning: exit: Command line did not parse.
[app] execute_smartctl(): Smartctl binary did not execute cleanly.
[app] StorageDevice::execute_device_smartctl(): Smartctl binary did not execute cleanly.
[gtk] setenv()/putenv() are not thread-safe and should not be used after threads are created
[gtk] posix_spawn avoided (workdir specified) (fd close requested)
[gtk] setenv()/putenv() are not thread-safe and should not be used after threads are created
[hz] Warning: exit: Device open failed, or device did not return an IDENTIFY DEVICE structure.
[app] SmartctlParser::parse_full(): No ATA sections could be parsed. Returning.
[gtk] setenv()/putenv() are not thread-safe and should not be used after threads are created
[gtk] posix_spawn avoided (workdir specified) (fd close requested)
[gtk] setenv()/putenv() are not thread-safe and should not be used after threads are created
[hz] Warning: exit: Device open failed, or device did not return an IDENTIFY DEVICE structure.
[app] SmartctlParser::parse_full(): No ATA sections could be parsed. Returning.
[gtk] setenv()/putenv() are not thread-safe and should not be used after threads are created
[gtk] posix_spawn avoided (workdir specified) (fd close requested)
[gtk] setenv()/putenv() are not thread-safe and should not be used after threads are created
[hz] Warning: exit: Device open failed, or device did not return an IDENTIFY DEVICE structure.
[gtk] setenv()/putenv() are not thread-safe and should not be used after threads are created
[gtk] posix_spawn avoided (workdir specified) (fd close requested)
[gtk] setenv()/putenv() are not thread-safe and should not be used after threads are created
[hz] Warning: exit: Device open failed, or device did not return an IDENTIFY DEVICE structure.
[app] SmartctlParser::parse_full(): No ATA sections could be parsed. Returning.
[gtk] setenv()/putenv() are not thread-safe and should not be used after threads are created
[gtk] posix_spawn avoided (workdir specified) (fd close requested)
[gtk] setenv()/putenv() are not thread-safe and should not be used after threads are created
[hz] Warning: exit: Device open failed, or device did not return an IDENTIFY DEVICE structure.
[app] SmartctlParser::parse_full(): No ATA sections could be parsed. Returning.
[gtk] setenv()/putenv() are not thread-safe and should not be used after threads are created
[gtk] posix_spawn avoided (workdir specified) (fd close requested)
[gtk] setenv()/putenv() are not thread-safe and should not be used after threads are created
[hz] Warning: exit: Device open failed, or device did not return an IDENTIFY DEVICE structure.
[app] SmartctlParser::parse_full(): No ATA sections could be parsed. Returning.
Muistialueen ylitys (luotiin core-tiedosto)
.........................
The last line is something like "Memory area exceeded (core file was created)" in English.

I don't know if this is a problem with my Linux Mint 20.1 installation or GSmartControl, so I just decided to start asking here. My system seems to work without problems otherwise. Thanks!

@ashaduri
Copy link
Owner

Hello,

Please try running gsmartcontrol with --no-scan option, something like gsmartcontrol-root --no-scan. If it doesn't crash, try manually adding your devices (/dev/sda, /dev/sr0, etc...) and see which one causes the crash.
When you pinpoint the problematic device (e.g. /dev/sr0), please create output.txt like this:
sudo smartctl -x /dev/sr0 &> output.txt and attach the file here.

Please also check if you have adwaita-icon-theme installed.

Thanks

@ashaduri ashaduri self-assigned this Apr 12, 2021
@ashaduri ashaduri added the bug Something isn't working label Apr 12, 2021
@aritorhamo
Copy link
Author

aritorhamo commented Apr 18, 2021

Thanks for your reply, ashaduri. I'm sorry for the delay in my response.

When I do gsmartcontrol-root --no-scan, I get the following:

[gtk] _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’
[gtk] posix_spawn avoided (workdir specified) (fd close requested)
[gtk] setenv()/putenv() are not thread-safe and should not be used after threads are created

P.S. Is it a good practice to use "insert code" formating, when quoting the output from the terminal?

@ashaduri
Copy link
Owner

Did it crash when you ran it as gsmartcontrol-root --no-scan?

The "insert code" feature in the editor is for single lines only.

@aritorhamo
Copy link
Author

aritorhamo commented Apr 18, 2021

I'm sorry for not being more specific. No, the program didn't crash, despite the error messages shown in the terminal. When I try to add any device manually, the program crashes, with the following additional lines shown in the terminal:

[gtk] setenv()/putenv() are not thread-safe and should not be used after threads are created
[gtk] posix_spawn avoided (workdir specified) (fd close requested)
[gtk] setenv()/putenv() are not thread-safe and should not be used after threads are created
/usr/bin/gsmartcontrol-root: rivi 167: 6837 Muistialueen ylitys (luotiin core-tiedosto) pkexec --disable-internal-agent /usr/sbin/gsmartcontrol "--no-scan"

The lines are the same for all devices, except for the four digits after "167:", which are different for each device.

Here's the Output.txt file you asked for:
output.txt

I have these two Adwaita icon themes installed (but not currently in use; I'm using Mint-Y):
adwaita-icon-theme 3.36.1-2ubuntu0.20.04.2
adwaita-icon-theme-full 3.36.1-2ubuntu0.20.04.2

P.S. When I copy error messages from the terminal and paste them here, the comment system for some reason strips away "error" (surrounded by lesser-than and bigger-than signs) from the beginning of the copied lines. The word is there when I compose the comment, but isn't shown on the preview nor the final comment. Perhaps it's normal, but I thought to mention about it.

@ashaduri
Copy link
Owner

I was unable to reproduce this crash on Linux Mint 20.1 with SATA SSD. I tried MATE and Cinnamon desktops.

Can you please tell me which desktop you use?

Thanks

P.S. The error messages you're seeing are harmless, most of them should be hidden by default in the next version.

@aritorhamo
Copy link
Author

I'm sorry for not being more specific. My desktop is Cinnamon. GSmartControl seems to work now, though. I haven't ttried it between answering the latest questions here and this moment, so I don't know when the situation changed. It may have something to do with another problem that I had a few weeks after reporting the issue, namely that one of my two external drives stopped working properly, the symptoms being interrupted file transfers and frequent dismountings. The reason turned out to be a defective SATA cable, which I noticed by changing the cable between the two external drives The faulty cable (or more precisely the dismountings that it caused) probably messed up the drive book-keeping on the system a little. It still doesn't look quite right to me, but GSmartControl has started to work, although maybe not for that reason. I should mention that the faulty cable perhaps isn't the cause for the original problem, because I tested GSmartControl several times with the external drives detached before reporting.

Anyway, it's good to have GSmartControl working again. The reason for the original issue may stay a mystery, but if you still have some questions, I'm glad to answer them.

@ashaduri
Copy link
Owner

Thank you for clarifying.

I guess a routine update to one of the underlying libraries fixed the issue. At least it's good to know it's not hardware-specific.
Still, I've been getting this kind of crash reports on and off for a few years now, and I still can't get to the bottom of it.
I'll close this issue for now, but if it comes back again, please take note of the exact installed versions of gtk, gtkmm, cairo, and glibc.

Thanks!

@ashaduri
Copy link
Owner

A crash with similar symptoms has been fixed, see #13 .

@ashaduri ashaduri added the fixed The issue has been fixed label Jan 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working fixed The issue has been fixed
Projects
None yet
Development

No branches or pull requests

2 participants