Bug 390390 - Dragging a binary onto widget causes panel crash
Summary: Dragging a binary onto widget causes panel crash
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Icons-only Task Manager (show other bugs)
Version: 5.12.0
Platform: Neon Linux
: NOR crash
Target Milestone: 1.0
Assignee: Eike Hein
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-13 18:58 UTC by Andrew Crouthamel
Modified: 2018-02-19 12:36 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Crouthamel 2018-02-13 18:58:53 UTC
When dragging a custom binary (such as godot) onto the Icons-Only Task Manager, it causes the panel to crash and restart. Unfortunately I do not receive a notification about it, and I can't take a video of it, as Peek stops recording when it happens.

This is always reproducible. Please let me know if you would like to to run some diags and I'll provide output.

Related to this, is dragging binaries onto the Task Manager supported? I would expect it should work that way. The only way I can get binaries to have a shortcut on the Icons-Only Task Manager is to run it, then right click the icon and Pin it.

KDE Plasma Version: 5.12.0
KDE Frameworks Version: 5.42.0
Qt Version: 5.9.3
Kernel Version 4.13.0-32-generic
OS Type: 64-bit
Comment 1 Eike Hein 2018-02-14 12:29:08 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.
Comment 2 Andrew Crouthamel 2018-02-14 15:10:06 UTC
(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>.
Comment 3 Eike Hein 2018-02-14 15:24:16 UTC
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'
Comment 4 Andrew Crouthamel 2018-02-14 15:55:56 UTC
(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. :)
Comment 5 Eike Hein 2018-02-14 15:59:08 UTC
Thanks for following up!
Comment 6 Nate Graham 2018-02-14 17:04:56 UTC
> 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! ;)
Comment 7 Andrew Crouthamel 2018-02-14 17:06:50 UTC
(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!
Comment 8 Andrew Crouthamel 2018-02-18 05:28:54 UTC
(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.
Comment 9 Jonathan Riddell 2018-02-19 12:36:04 UTC
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