| Summary: | Crash when starting and using rpm-ostree updates | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | Henning <boredsquirrel> |
| Component: | rpm-ostree Backend | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | aleixpol, fella, mariamfahmy66, tim, travier |
| Priority: | NOR | ||
| Version First Reported In: | 5.27.5 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Henning
2023-06-22 09:00:31 UTC
Hi, we don't make things optional to work around crashes. Please provide a backtrace for your crash instead. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports for how to do that Yes makes sense of course, but in general 1. On rpm-ostree layering packages through a GUI may be a false impression 2. Doing such a huge update right when you start the app is horrible. It is already horrible on normal Package managers, as you want to install Flatpaks or maybe layer apps with rpm-ostree update --install APPNAME So it makes no sense. Either you dont want to install RPMs, then the store may just crash because of overload, or you want to layer RPMs but the image gets already created and then reopened and an app layered to it. So you do double the work. *** Bug 470994 has been marked as a duplicate of this bug. *** Please do the following and report the crash backtrace: ``` # Layer gdb-minimal $ sudo rpm-ostree install gdb-minimal # Setup a symlink $ sudo ln -nsf /usr/bin/gdb-minimal /usr/local/bin/gdb # Trigger the crash again. DrKonqi should get you a backtrace now ``` 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! Currently not reproducible. Maybe you reduced the load? System updates stay at 5% when launching disover, but it doesnt crash. 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! 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! |