| Summary: | kwin_x11 crashed without good reason with segmentation fault | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Aram <aram.pakhchanian> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | 6yearold, groot, nate |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.24.6 | ||
| Target Milestone: | --- | ||
| Platform: | FreeBSD Ports | ||
| OS: | FreeBSD | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Aram
2023-01-17 18:23:31 UTC
Can you attach the full backtrace content? Looks like it didn't come through. Thanks! 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! (In reply to Nate Graham from comment #1) > Can you attach the full backtrace content? Looks like it didn't come > through. Thanks! Unfortunately, I have a regular install of KDE, and to my knowledge it does not come with debug info, so I am not sure how to provide a backtrace. You may be able to re-compile yourself with debug symbols, then. But in general, if your distro doesn't provide debug symbols, that's a problem, and it will make it impossible for you to submit actionable crash reports. I'd recommend discussing it with the developers of your distro. (In reply to Nate Graham from comment #4) > You may be able to re-compile yourself with debug symbols, then. > > But in general, if your distro doesn't provide debug symbols, that's a > problem, and it will make it impossible for you to submit actionable crash > reports. I'd recommend discussing it with the developers of your distro. It's FeeBSD, not a distro. I will check to see if I can install debug into files from the repository to be sure that if something happens again (the same bug did repeat up yet), I will be able to submit a relevant bug report. Thank you! (In reply to Aram from comment #5) > I will check to see if I can install debug into > files from the repository to be sure that if something happens again (the > same bug did repeat up yet), I will be able to submit a relevant bug report. > Thank you! There are no debugging info packages in FreeBSD at the moment. You'll need to build a port from source to get the debugging info. Here are the quick steps: 1. Obtain the Ports tree with "portsnap" or "git clone". 2. cd <ports_dir> 3. Gather the list of packages required to compile: make -C x11-wm/plasma5-kwin/ build-depends-list | xargs -L 1 -J % make -C % -V '${PKGNAMEPREFIX}${PORTNAME}${PKGNAMESUFFIX}' 4. "pkg install -A" them. 5. Build and install debug version of the port make -C x11-wm/plasma5-kwin WITH_DEBUG=yes install This will allow you to get sensible backtrace from gdb. After you're done remember to run make -C x11-wm/plasma5-kwin clean or remove <ports_dir> altogether. (In reply to Gleb Popov from comment #6) Gleb, thank you very much indeed! I once tried building a browser from the ports, and it took a few days on my notebook (you may imagine it's not a top notch one, as you need a reasonably seasoned notebook to run FreeBSD without driver issues). I can imagine building kwin will take about the same time. I do have the ports installed though. Will try, but again, not sure I will be able to reproduce the bug. (In reply to Aram from comment #7) > I once tried building a browser from the ports, and it took a few days on my > notebook (you may imagine it's not a top notch one, as you need a reasonably > seasoned notebook to run FreeBSD without driver issues). I can imagine > building kwin will take about the same time. Not really. Browsers are enormous codebases. KWin is a quite small piece of software compared to them. Instructions I gave you minimizes the amount of code you have to compile, so it should take no more than an hour even on moderate hardware. 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! |