Bug 418333 - Driver Manager crashes collecting information.
Summary: Driver Manager crashes collecting information.
Status: RESOLVED WORKSFORME
Alias: None
Product: KDE Config Driver Manager
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: Harald Sitter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-29 18:37 UTC by lnxusr
Modified: 2022-11-17 05:13 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lnxusr 2020-02-29 18:37:30 UTC
SUMMARY
Driver Manager displays 'Something wind terribly wrong. Please hit the 'Refresh Driver List' button' while collecting information on drivers.


STEPS TO REPRODUCE
1. Open System Settings -> Driver Manager
2. 
3. 

OBSERVED RESULT
After a few seconds, above message is displayed.  Hitting 'Refresh Driver List' button results in same error message.


EXPECTED RESULT
Information on drivers should be displayed.


SOFTWARE/OS VERSIONS

KDE Plasma Version: 5.18.2
KDE Frameworks Version: 5.67.0
Qt Version: 5.14.1

ADDITIONAL INFORMATION
The following is logged to syslog:
Feb 29 12:21:50 razorback rtkit-daemon[2790]: Supervising 5 threads of 2 processes of 1 users.
Feb 29 12:22:07 razorback dbus-daemon[2604]: [session uid=1000 pid=2604] Activating service name='org.kubuntu.DriverManager' requested by ':1.149' (uid=1000 pid=7977 comm="/usr/bin/systemsettings5 " label="unconfined")
Feb 29 12:22:07 razorback org.kubuntu.DriverManager[2604]: Traceback (most recent call last):
Feb 29 12:22:07 razorback org.kubuntu.DriverManager[2604]:   File "/usr/lib/x86_64-linux-gnu/libexec/DriverManager_DBus", line 26, in <module>
Feb 29 12:22:07 razorback org.kubuntu.DriverManager[2604]:     from dbus.mainloop.pyqt5 import DBusQtMainLoop
Feb 29 12:22:07 razorback org.kubuntu.DriverManager[2604]: ModuleNotFoundError: No module named 'dbus.mainloop.pyqt5'
Feb 29 12:22:07 razorback org.kubuntu.DriverManager[2604]: Error in sys.excepthook:
Feb 29 12:22:07 razorback org.kubuntu.DriverManager[2604]: Traceback (most recent call last):
Feb 29 12:22:07 razorback org.kubuntu.DriverManager[2604]:   File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 145, in apport_excepthook
Feb 29 12:22:07 razorback org.kubuntu.DriverManager[2604]:     os.O_WRONLY | os.O_CREAT | os.O_EXCL, 0o640), 'wb') as f:
Feb 29 12:22:07 razorback org.kubuntu.DriverManager[2604]: FileNotFoundError: [Errno 2] No such file or directory: '/var/crash/_usr_lib_x86_64-linux-gnu_libexec_DriverManager_DBus.1000.crash'
Feb 29 12:22:07 razorback org.kubuntu.DriverManager[2604]: Original exception was:
Feb 29 12:22:07 razorback org.kubuntu.DriverManager[2604]: Traceback (most recent call last):
Feb 29 12:22:07 razorback org.kubuntu.DriverManager[2604]:   File "/usr/lib/x86_64-linux-gnu/libexec/DriverManager_DBus", line 26, in <module>
Feb 29 12:22:07 razorback org.kubuntu.DriverManager[2604]:     from dbus.mainloop.pyqt5 import DBusQtMainLoop
Feb 29 12:22:07 razorback org.kubuntu.DriverManager[2604]: ModuleNotFoundError: No module named 'dbus.mainloop.pyqt5'
Feb 29 12:22:07 razorback dbus-daemon[2604]: [session uid=1000 pid=2604] Activated service 'org.kubuntu.DriverManager' failed: Process org.kubuntu.DriverManager exited with status 1
Comment 1 Justin Zobel 2022-10-03 10:37:44 UTC
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Comment 2 Bug Janitor Service 2022-10-18 04:58:25 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 lnxusr 2022-10-18 16:01:08 UTC
(In reply to Justin Zobel from comment #1)
> Thank you for reporting this crash in KDE software. As it has been a while
> since this issue was reported, can we please ask you to see if you can
> reproduce the crash with a recent software version?
> 
> If you can reproduce the issue, please change the status to "CONFIRMED" when
> replying. Thank you!

Neon is on Plasma 5.26 and Frameworks 5.98 now, and I no longer see a Driver Manager selection in the Settings.  I suppose this bug can be closed, but I don't know what the status should be set as.
Comment 4 Bug Janitor Service 2022-11-02 05:05:47 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2022-11-17 05:13:04 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!