Description of problem: It just crashed after installing the plugin. Version-Release number of selected component: hplip-3.18.12-1.fc29 Additional info: reporter: libreport-2.9.7 backtrace_rating: 3 cmdline: /usr/bin/python3 /usr/bin/hp-plugin crash_function: Fm::FileLauncher::showError executable: /usr/bin/python3.7 journald_cursor: s=909f1cee770746bba82c46f73798c57f;i=3e34c;b=51255f72e7164283ba55dd3e260a895d;m=de7b59046d;t=580c565fe4e1c;x=a80c2223a7951592 kernel: 4.19.13-300.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 Fm::FileLauncher::showError at /usr/src/debug/libfm-qt-0.13.1-2.fc29.x86_64/src/core/gioptrs.h:112 #1 Fm::BasicFileLauncher::openFolder at /usr/src/debug/libfm-qt-0.13.1-2.fc29.x86_64/src/core/gobjectptr.h:16 #2 Fm::BasicFileLauncher::launchFiles at /usr/src/debug/libfm-qt-0.13.1-2.fc29.x86_64/src/core/basicfilelauncher.cpp:77 #3 Fm::FileLauncher::launchFiles at /usr/src/debug/libfm-qt-0.13.1-2.fc29.x86_64/src/filelauncher.cpp:43 #4 Fm::FileMenu::onOpenTriggered at /usr/src/debug/libfm-qt-0.13.1-2.fc29.x86_64/src/filemenu.cpp:283 #6 QtPrivate::QSlotObjectBase::call at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:376 #7 QMetaObject::activate at kernel/qobject.cpp:3754 #8 QAction::triggered at .moc/moc_qaction.cpp:376 #9 QAction::activate at kernel/qaction.cpp:1166 #10 QMenuPrivate::activateCausedStack at widgets/qmenu.cpp:1371
Created attachment 1525523 [details] File: backtrace
Created attachment 1525524 [details] File: cgroup
Created attachment 1525525 [details] File: core_backtrace
Created attachment 1525526 [details] File: cpuinfo
Created attachment 1525527 [details] File: dso_list
Created attachment 1525528 [details] File: environ
Created attachment 1525529 [details] File: exploitable
Created attachment 1525530 [details] File: limits
Created attachment 1525531 [details] File: maps
Created attachment 1525532 [details] File: mountinfo
Created attachment 1525533 [details] File: open_fds
Created attachment 1525534 [details] File: proc_pid_status
Hi Karel, thank you for reporting the issue! Actually, I'm not able to reproduce the issue in Gnome, so it is maybe lxqt issue specific. Segfault seems to happen too deep in qt itself to be hp-plugin responsible. I'm reassigning to libfm-qt for more investigation.
What plugin is this all about?
hp-plugin script, which downloads proprietary shared libraries for several types of HP printers. By default, when you start it without any parameter, it starts Qt5 GUI, which seems to crash in lxqt environment - backtrace seems to go deep into qt, so imo hp-plugin does not have to be responsible.
Is pcmanfm-qt installed and running? Do you see any dialog that prompts to select an application? As far as I can understand the sources, there is no application available in the crashing system to handle the mime type "inode/directory". Upstream seems to have forgot to generate a proper error message. The crash happens somewhere in the headers because the used pointer for that err variable there is invalid. https://github.com/lxqt/libfm-qt/blob/422f867a94442fdfe5db06836403b5bc7b5c68db/src/filelauncher.cpp#L68 https://github.com/lxqt/libfm-qt/blob/422f867a94442fdfe5db06836403b5bc7b5c68db/src/core/basicfilelauncher.cpp#L137
No help from LXQt SIG. Forwarding to Qt5 core.
I thought this was clearly demonstrated to be a deficiency and/or missing feature of libfm-qt, why re-assign elsewhere?
"missing feature" like what? I doubt LXQt upstream cares about proprietary software as the plugin is. Better someone should ask at HP. Well, no response so far to my questions towards pcmanfm-qt. Karel, can you still reproduce?
I was referring to the upstream code comment // FIXME: show error properly?
Someone 'd report this to upstream then. Karel, can you do that?
Is this still reproducible?
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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 '29'. 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 29 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.
(In reply to Raphael Groner from comment #22) > Is this still reproducible? sorry for late reply - no, I haven't seen this since ... I think this has gone away after zdohnal did some changes in packaging