Description of problem: - I looked for the GSmartControl in activities and opened it, then I typed my administrator password, - the program showed the main window and closed suddenly Version-Release number of selected component: gsmartcontrol-1.1.3-2.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/sbin/gsmartcontrol crash_function: Gdk::Pixbuf::gobj executable: /usr/sbin/gsmartcontrol journald_cursor: s=90c81264243a4dca82d6decefa2a9386;i=1b3c;b=66f3e63c11da4b45b3f507ebc4295b7e;m=dbcef9bb;t=57733629e3a95;x=ea7f7c2c6e64f770 kernel: 4.18.9-200.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 Gdk::Pixbuf::gobj at /usr/include/gdkmm-3.0/gdkmm/pixbuf.h:385 #1 GscMainWindowIconView::on_cell_data_render at gsc_main_window_iconview.h:226 #2 sigc::slot1<void, Gtk::TreeIter const&>::operator() at /usr/include/sigc++-2.0/sigc++/functors/slot_base.h:335 #3 celllayout.cc at celllayout.cc:41 #4 apply_cell_attributes at gtkcellarea.c:1257 #5 g_hash_table_foreach at ghash.c:1626 #6 gtk_cell_area_real_apply_attributes at gtkcellarea.c:1286 #7 gtk_cell_area_box_apply_attributes at gtkcellareabox.c:1310 #8 _gtk_marshal_VOID__OBJECT_BOXED_BOOLEAN_BOOLEANv at gtkmarshalers.c:4982 #9 _g_closure_invoke_va at gclosure.c:867
Created attachment 1489234 [details] File: backtrace
Created attachment 1489235 [details] File: cgroup
Created attachment 1489236 [details] File: core_backtrace
Created attachment 1489237 [details] File: cpuinfo
Created attachment 1489238 [details] File: dso_list
Created attachment 1489239 [details] File: environ
Created attachment 1489240 [details] File: exploitable
Created attachment 1489241 [details] File: limits
Created attachment 1489242 [details] File: maps
Created attachment 1489243 [details] File: mountinfo
Created attachment 1489244 [details] File: open_fds
Created attachment 1489245 [details] File: proc_pid_status
It is always happen? Can be reproduced?
(In reply to Vasiliy Glazov from comment #13) > It is always happen? Can be reproduced? Yes, it aways happen, I'd say it's been about 2 months since this started.
No one has same issue. Try reinstall it.
(In reply to Vasiliy Glazov from comment #15) > No one has same issue. Try reinstall it. I tried thatI actually tried this, including reinstalling the gdk and gtkmm packages. I also tried removing the gsmartcontrol configuration files, with the same results. Finally I downloaded the source code of gsmartcontrol 1.1.3.2 and compiled it, the same problems, so I tried to debug the software for some time because I think it might be a problem with the gsmartcontrol add_entry () method in the gsc_main_window_iconview class or B) gtkmm or gdk problem. However, I failed to debug the program because I know almost nothing about autotools and automake. I tested gsmartcontrol on my other machine, and it worked perfectly, but I do not think that says much, maybe it's a problem related to my specific configuration (msata SSD + Sata HDD) and I'd like to find out exactly what. Smartctl command line (which is used by gsmartcontrol) works without errors in my system. grateful for the attention, I keep waiting for some idea :)
You can try install gsmartcontrol-debuginfo package, run gdb gsmartcontrol and receive good backtrace. I can't help with it but may be author can help you. Or just ask author.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.