| Summary: | Copying text from websites in Firefox causes KDE panel to temporarily freeze. | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | BryanFRitt <BryanFRitt> |
| Component: | Panel | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | justin.zobel, kde |
| Priority: | NOR | ||
| Version First Reported In: | master | ||
| Target Milestone: | 1.0 | ||
| Platform: | Debian stable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
BryanFRitt
2018-04-18 17:08:41 UTC
Was it a long text that you copied? Can you get a backtrace of when plasma freezes? With short text around a word or so it freezes for around a second, but for longer text around a average size paragraph it can freezes around a minute or more. Right now I can see that it has been frozen for close to 5 minutes, and it just now came back to working like nothing happened. No crash dialog box or anything. During the freeze the panel doesn't do anything. With just the text prior to this sentence text copied in at 14:05:44 the panel finally unfroze at 14:08:16, for a total of 2 minutes and 32 seconds frozen. "Can you get a backtrace of when plasma freezes?" How can I do this? It's not 'crashing', so the automatic backtrace box doesn't show up. Just tried running Firefox-esr with '-safe-mode', and this problem doesn't seam to be occurring now, so maybe it's a browser plug-in(s)? It' seams weird that a firefox plug-in might cause plasma panel to freeze when copying text. What plug-in(s) would cause the KDE panel to freeze when copying? Ideally even bad written browser plug-ins shouldn't freeze the kde panel. On console run gdb plasmashell then type r (run), make it freeze and when it does Ctrl+C and type thread apply all bt and paste the output here. This should give us a clue where it freezes, I suspect somewhere in QMimeData. Make sure to install debug packages for at least Plasma (framework, worksapce, desktop). Thanks! "On console run gdb plasmashell then type r (run), make it freeze and when it does Ctrl+C and type thread apply all bt and paste the output here" "Make sure to install debug packages for at least Plasma (framework, worksapce, desktop)." "Reading symbols from plasmashell...(no debugging symbols found)...done." I've tried searching the Debian repositories for "Plasma (framework, worksapce, desktop)." and couldn't find anything for Debian Stable 9.x. - [New Thread 0x7fff1ecac700 (LWP 7069)] [Thread 0x7fff1ecac700 (LWP 7069) exited] thread apply all bt [New Thread 0x7fff1ecac700 (LWP 7281)] [Thread 0x7fff1ecac700 (LWP 7281) exited] [New Thread 0x7fff1ecac700 (LWP 8440)] [New Thread 0x7fff1ecac700 (LWP 8957)] [Thread 0x7fff1ecac700 (LWP 8957) exited] [New Thread 0x7fff1ecac700 (LWP 10446)] [Thread 0x7fff1ecac700 (LWP 10446) exited] thread apply all bt thread apply all bt [New Thread 0x7fff1ecac700 (LWP 12112)] thread apply all bt [Thread 0x7fff1ecac700 (LWP 12112) exited]^C Thread 1 "plasmashell" received signal SIGINT, Interrupt. 0x00007ffff24f067d in poll () from /lib/x86_64-linux-gnu/libc.so.6 Quit A debugging session is active. Inferior 1 [process 6986] will be killed. Quit anyway? (y or n) y It says ["New Thread"...] when the clock etc... goes back to working, then a few seconds later "[Thread" ... "exited"]. The "thread apply all bt" was me either typing it in or pasting it. The ^C...Quit...y was me exiting after testing. I've tried searching the Debian repositories for "Plasma (framework, worksapce, desktop)." and couldn't find anything for Debian Stable 9.x. I meant the debugging packages. Thanks for the report. I've been using Firefox on KDE almost exclusively and haven't had this issue. Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks. I haven't noticed this in a very time, and practically forgot about it. Just tried copying text in Firefox again, and didn't notice this bug happening. So I'm changing it from NEEDSINFO to RESOLVED. |