Summary: | Dragging a binary onto widget causes panel crash | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Andrew Crouthamel <andrew.crouthamel> |
Component: | Icons-only Task Manager | Assignee: | Eike Hein <hein> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | jr, nate, plasma-bugs |
Priority: | NOR | ||
Version: | 5.12.0 | ||
Target Milestone: | 1.0 | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Andrew Crouthamel
2018-02-13 18:58:53 UTC
Unfortunately I can't reproduce this crash. Without a backtrace I can't really do much. Also, no, currently dropping a binary wouldn't create a launcher. (In reply to Eike Hein from comment #1) > Unfortunately I can't reproduce this crash. Without a backtrace I can't > really do much. > > Also, no, currently dropping a binary wouldn't create a launcher. I'd be glad to produce a backtrace, but need a little help with what to run. I've installed kdelibs5-dbg and gdb. What should I run to launch a new panel via gdb with the task manager on it? I'm assuming gdb <something>. kdelibs5-dbg is KDE 4's libraries debug symbols. You need debug symbols for Qt and plasma-workspace and plasma-desktop. Then, typically you wouldn't need to run gdb manually - a crash dialog should come up. After the shell crashes you should see a crash icon in the tray. Clicking it should bring up a dialog with a Backtrace tab. If this doesn't work for some reason, you can do: 1. gdb plasmashell 2. 'run' 3. crash 4. 'bt' (In reply to Eike Hein from comment #3) > kdelibs5-dbg is KDE 4's libraries debug symbols. > > You need debug symbols for Qt and plasma-workspace and plasma-desktop. > > Then, typically you wouldn't need to run gdb manually - a crash dialog > should come up. After the shell crashes you should see a crash icon in the > tray. Clicking it should bring up a dialog with a Backtrace tab. > > If this doesn't work for some reason, you can do: > > 1. gdb plasmashell > 2. 'run' > 3. crash > 4. 'bt' Oh, thanks. Someone should update https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports since it recommended kdelibs5-dbg. Of course I updated to 5.12.1 and now the crash has gone away. :) Thanks for following up! > Oh, thanks. Someone should update https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports since it recommended kdelibs5-dbg.
It's a wiki, so that somebody could be you! ;)
(In reply to Nate Graham from comment #6) > > Oh, thanks. Someone should update https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports since it recommended kdelibs5-dbg. > > It's a wiki, so that somebody could be you! ;) LOL, stop making work for me Nate! (In reply to Eike Hein from comment #3) > kdelibs5-dbg is KDE 4's libraries debug symbols. > > You need debug symbols for Qt and plasma-workspace and plasma-desktop. > > Then, typically you wouldn't need to run gdb manually - a crash dialog > should come up. After the shell crashes you should see a crash icon in the > tray. Clicking it should bring up a dialog with a Backtrace tab. > > If this doesn't work for some reason, you can do: > > 1. gdb plasmashell > 2. 'run' > 3. crash > 4. 'bt' Any chance I could get a hint on what the dbg packages are named on Ubuntu? My searches for "plasma dbg" are coming up empty. I'll update the Wiki as well if you can help me figure it out. Debug symbols can be installed from the Dr Konqi crash handler which should work out what the right ones are https://i.imgur.com/DThprvi.png this installed libqt5core5a-dbgsym when I ran it just now other bits that might be handy include: libkf5plasma5-dbgsym plasma-framework-dbgsym plasma-workspace-dbg plasma-integration-dbg plasma-desktop-dbg but of course it depends on the particular library you're interested in |