Closed Bug 1424687 Opened 7 years ago Closed 7 years ago

Nightly crashes when pasting text from Linux/Qt 5 clipboard

Categories

(Core :: General, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: rverschelde, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0 Build ID: 20171210220040 Steps to reproduce: 1. Open Firefox Nightly [59.0a1 (2017-12-10) (64-bit)] 2. Copy text in the system clipboard (Linux / KDE Plasma 5) outside of Nightly (e.g. from the Konsole terminal emulator) 3. Paste text in an edit area in Nightly with Ctrl+V (triggers the bug reliably in GitHub comments and Riot.im chatbox from what I could see) 4. Nightly crashes instantly This is a recent regression, it started happening on Sunday morning UTC for me (I believe [59.0a1 (2017-12-09) (64-bit)] at that time), so it should be from a commit staged less than 48 hours ago. Actual results: See steps to reproduce; instant crash. Expected results: No crash :o)
A few debugging crashes later (sorry for the crash report spam :)), some more info: - Crashes happen when you paste, whether with Ctrl+V or with Right Click > Paste (so not hotkey related). - Crashes happen only when pasting content that was copied from a Qt application (5, haven't tried 4). So copying from Konsole, Kate or QtCreator will trigger a crash when pasting, but not when copying from Nightly itself (GTK+3), VS Code (Electron) or a native X11 application (Godot Engine). - Crashes happen when pasting to a GitHub comment or the Riot.im chat box, and likely other areas too, but not all. No crashes happen when pasting in a Bugzilla comment for example.
Summary: Nightly crashes when pasting text from Linux/KDE Plasma 5 clipboard → Nightly crashes when pasting text from Linux/Qt 5 clipboard
Some more system info: - OS: Mageia 6 x86_64, kernel 4.9.56, X11 1.19.5, nvidia proprietary drivers 384.98 - Application layer: Plasma 5.8.7 with Qt 5.6.2 TL;DR: Doesn't seem related to a system update. *** In case it could be a regression on my end, last batch of system updates from 24h before I started experiencing crashes: libxcursor1-1.1.14-6.1.mga6.i586 Sat Dec 9 00:51:04 2017 lib64xfont2_2-2.0.1-4.2.mga6.x86_64 Sat Dec 9 00:51:04 2017 lib64xfont1-1.5.2-1.2.mga6.x86_64 Sat Dec 9 00:51:03 2017 lib64ffmpeg-devel-3.3.5-1.mga6.tainted.x86_64 Sat Dec 9 00:51:02 2017 grub2-mageia-theme-2.02.0-1.mga6.noarch Sat Dec 9 00:51:02 2017 synfig-1.2.1-2.mga6.x86_64 Sat Dec 9 00:51:01 2017 lib64xcursor-devel-1.1.14-6.1.mga6.x86_64 Sat Dec 9 00:50:59 2017 lib64synfig-devel-1.2.1-2.mga6.x86_64 Sat Dec 9 00:50:59 2017 lib64xcursor1-1.1.14-6.1.mga6.x86_64 Sat Dec 9 00:50:58 2017 lib64etl-devel-1.2.1-1.mga6.x86_64 Sat Dec 9 00:50:57 2017 ffmpeg-3.3.5-1.mga6.tainted.x86_64 Sat Dec 9 00:50:56 2017 lib64synfig0-1.2.1-2.mga6.x86_64 Sat Dec 9 00:50:55 2017 grub2-2.02.0-1.mga6.x86_64 Sat Dec 9 00:50:54 2017 grub2-common-2.02.0-1.mga6.x86_64 Sat Dec 9 00:50:52 2017 lib64avfilter6-3.3.5-1.mga6.tainted.x86_64 Sat Dec 9 00:50:50 2017 lib64avformat57-3.3.5-1.mga6.tainted.x86_64 Sat Dec 9 00:50:49 2017 lib64swscaler4-3.3.5-1.mga6.tainted.x86_64 Sat Dec 9 00:50:48 2017 lib64postproc54-3.3.5-1.mga6.tainted.x86_64 Sat Dec 9 00:50:48 2017 lib64avresample3-3.3.5-1.mga6.tainted.x86_64 Sat Dec 9 00:50:48 2017 lib64avcodec57-3.3.5-1.mga6.tainted.x86_64 Sat Dec 9 00:50:47 2017 lib64swresample2-3.3.5-1.mga6.tainted.x86_64 Sat Dec 9 00:50:46 2017 lib64avutil55-3.3.5-1.mga6.tainted.x86_64 Sat Dec 9 00:50:45 2017 The xcursor and xfont updates were for https://advisories.mageia.org/MGASA-2017-0443.html and https://advisories.mageia.org/MGASA-2017-0442.html but I don't think they would affect the X11 clipboard (and I had no crashes on Sat 9 Dec though I used Nightly a lot the whole day).
Hi Remi! It does not happen here when I copy+paste from konsole to the edit section of https://gist.github.com/ on xfce on mageia 7 x86-64 with nightly.
It is fine when pasting to a github issue comment as well.
Thanks for testing Shlomi. I could reproduce the bug most of the week, but it seems to have been fixed with yesterday morning's update for me too. I don't have the permissions to close as RESOLVED FIXED, so using WORKSFORME.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.