Bug 341497 - Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions
Summary: Segfault in Qt since the (at least) the xcb screen backend cannot deal with "...
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: drkonqi
: 339922 343772 343982 344410 344773 344984 345096 345129 345205 345207 345809 346005 346627 346685 346700 347524 347534 347927 347957 347990 348165 348217 348262 348545 348623 348685 348788 349174 350467 350692 350710 350766 350800 351007 351180 351257 351546 352712 353122 353578 353823 354387 355118 355232 355857 355882 355937 356107 356144 356674 358560 358605 359228 360079 360134 360254 360337 360548 360684 361704 362350 362964 363580 364242 364362 364867 365913 366070 369221 380941 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-12-02 17:48 UTC by stephbal1
Modified: 2021-02-08 19:30 UTC (History)
71 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description stephbal1 2014-12-02 17:48:29 UTC 
Application: kwin_x11 (5.1.1)

Qt Version: 5.3.2
Operating System: Linux 3.16.6-2-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed: simply using ARandR to switch display from the second screenback to the laptop screen.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f03e8fc5800 (LWP 26756))]

Thread 5 (Thread 0x7f03cadee700 (LWP 26786)):
#0  0x00007f03e897ca63 in select () at /lib64/libc.so.6
#1  0x00007f03e6ad3c99 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x00007f03e6ad560f in QEventDispatcherUNIXPrivate::doSelect(QFlags<QEventLoop::ProcessEventsFlag>, timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x00007f03e6ad5a6b in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#4  0x00007f03e6a7ea4b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#5  0x00007f03e689deca in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x00007f03e68a2b3f in  () at /usr/lib64/libQt5Core.so.5
#7  0x00007f03df3190a4 in start_thread () at /lib64/libpthread.so.0
#8  0x00007f03e89837fd in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f03baf58700 (LWP 26807)):
#0  0x00007f03df31d05f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
#1  0x00007f03c8addbb3 in  () at /usr/lib64/dri/r600_dri.so
#2  0x00007f03c8add3d7 in  () at /usr/lib64/dri/r600_dri.so
#3  0x00007f03df3190a4 in start_thread () at /lib64/libpthread.so.0
#4  0x00007f03e89837fd in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f03b6289700 (LWP 26811)):
#0  0x00007f03e897ca63 in select () at /lib64/libc.so.6
#1  0x00007f03e6ad3c99 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x00007f03e6ad560f in QEventDispatcherUNIXPrivate::doSelect(QFlags<QEventLoop::ProcessEventsFlag>, timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x00007f03e6ad5a6b in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#4  0x00007f03e6a7ea4b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#5  0x00007f03e689deca in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x00007f03e68a2b3f in  () at /usr/lib64/libQt5Core.so.5
#7  0x00007f03df3190a4 in start_thread () at /lib64/libpthread.so.0
#8  0x00007f03e89837fd in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f03affff700 (LWP 26828)):
#0  0x00007f03df31d05f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
#1  0x00007f03e4e53fbb in  () at /usr/lib64/libQt5Script.so.5
#2  0x00007f03e4e53fe9 in  () at /usr/lib64/libQt5Script.so.5
#3  0x00007f03df3190a4 in start_thread () at /lib64/libpthread.so.0
#4  0x00007f03e89837fd in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f03e8fc5800 (LWP 26756)):
[KCrash Handler]
#5  0x00007f03e6fddf80 in QScreen::handle() const () at /usr/lib64/libQt5Gui.so.5
#6  0x00007f03d2c3e69a in  () at /usr/lib64/qt5/plugins/platforms/libqxcb.so
#7  0x00007f03d2c2f461 in  () at /usr/lib64/qt5/plugins/platforms/libqxcb.so
#8  0x00007f03e6fb94ce in QWindowPrivate::create(bool) () at /usr/lib64/libQt5Gui.so.5
#9  0x00007f03e6fb9888 in QWindow::winId() const () at /usr/lib64/libQt5Gui.so.5
#10 0x00007f03e8521c97 in  () at /usr/lib64/libkwin.so.5
#11 0x00007f03e8523de4 in  () at /usr/lib64/libkwin.so.5
#12 0x00007f03e852501b in  () at /usr/lib64/libkwin.so.5
#13 0x00007f03e6a7def0 in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) () at /usr/lib64/libQt5Core.so.5
#14 0x00007f03d2c2c438 in  () at /usr/lib64/qt5/plugins/platforms/libqxcb.so
#15 0x00007f03d2c2d78b in  () at /usr/lib64/qt5/plugins/platforms/libqxcb.so
#16 0x00007f03e6ab0716 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5
#17 0x00007f03e7721cfc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#18 0x00007f03e7726c36 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#19 0x00007f03e6a80b35 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#20 0x00007f03e6a82987 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#21 0x00007f03e6ad59f4 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#22 0x00007f03d2c7d4bd in  () at /usr/lib64/qt5/plugins/platforms/libqxcb.so
#23 0x00007f03e6a7ea4b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#24 0x00007f03e6a860a6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
#25 0x00007f03e8c4abbb in kdemain () at /usr/lib64/libkdeinit5_kwin_x11.so
#26 0x00007f03e88bfb05 in __libc_start_main () at /lib64/libc.so.6
#27 0x000000000040088e in _start ()

Reported using DrKonqi
Comment 1 Thomas Lübking 2014-12-02 20:37:20 UTC 
The bug is in Qt, when you change the resolution (and depending on how you do it) there might be a moment where there's no screen - and Qt5 crashes hard in this case.
Comment 2 Thomas Lübking 2015-02-20 23:36:59 UTC 
*** Bug 344410 has been marked as a duplicate of this bug. ***
Comment 3 Thomas Lübking 2015-03-09 23:14:40 UTC 
*** Bug 344984 has been marked as a duplicate of this bug. ***
Comment 4 Thomas Lübking 2015-03-12 21:35:14 UTC 
*** Bug 345096 has been marked as a duplicate of this bug. ***
Comment 5 Thomas Lübking 2015-03-16 13:26:55 UTC 
*** Bug 345207 has been marked as a duplicate of this bug. ***
Comment 6 Marc Schiffbauer 2015-03-16 13:55:08 UTC 
Thanks. For those who do not want to search for it in the QT bug: Should be fixed in QT 5.5
Comment 7 Thomas Lübking 2015-04-02 18:11:29 UTC 
*** Bug 345809 has been marked as a duplicate of this bug. ***
Comment 8 Thomas Lübking 2015-04-16 20:00:13 UTC 
*** Bug 346005 has been marked as a duplicate of this bug. ***
Comment 9 Thomas Lübking 2015-04-27 19:50:23 UTC 
*** Bug 346627 has been marked as a duplicate of this bug. ***
Comment 10 Thomas Lübking 2015-04-27 19:51:24 UTC 
*** Bug 346685 has been marked as a duplicate of this bug. ***
Comment 11 Thomas Lübking 2015-05-12 13:07:07 UTC 
*** Bug 347534 has been marked as a duplicate of this bug. ***
Comment 12 Thomas Lübking 2015-05-19 09:24:05 UTC 
*** Bug 347927 has been marked as a duplicate of this bug. ***
Comment 13 Christoph Feck 2015-05-20 22:45:18 UTC 
*** Bug 347957 has been marked as a duplicate of this bug. ***
Comment 14 Christoph Feck 2015-05-23 15:30:18 UTC 
*** Bug 347990 has been marked as a duplicate of this bug. ***
Comment 15 Christoph Feck 2015-05-31 14:01:06 UTC 
*** Bug 348165 has been marked as a duplicate of this bug. ***
Comment 16 Christoph Feck 2015-05-31 14:01:26 UTC 
*** Bug 348217 has been marked as a duplicate of this bug. ***
Comment 17 Christoph Feck 2015-06-07 10:04:37 UTC 
*** Bug 348545 has been marked as a duplicate of this bug. ***
Comment 18 Christoph Feck 2015-06-07 10:05:09 UTC 
*** Bug 348623 has been marked as a duplicate of this bug. ***
Comment 19 Christoph Feck 2015-06-07 10:05:27 UTC 
*** Bug 348685 has been marked as a duplicate of this bug. ***
Comment 20 Christoph Feck 2015-06-16 17:34:05 UTC 
*** Bug 349174 has been marked as a duplicate of this bug. ***
Comment 21 Marcelo Bossoni 2015-07-13 23:27:35 UTC 
So,
I've just updated to Qt5.5 from ArchLinux testing repositories.
All of the crashes seems gone, except by one when switching from TV (1920x1080) to Monitor (1680x1050)

Thread 1 (Thread 0x7f58b5461800 (LWP 1258)):
[KCrash Handler]
#5  0x00007f58afc14520 in QScreen::availableGeometry() const () from /usr/lib/libQt5Gui.so.5
#6  0x00007f58b4f1b54f in PlasmaQuick::Dialog::popupPosition(QQuickItem*, QSize const&) () from /usr/lib/libKF5PlasmaQuick.so.5
#7  0x00007f58b4f1cb42 in PlasmaQuick::Dialog::setVisible(bool) () from /usr/lib/libKF5PlasmaQuick.so.5
#8  0x00007f58af6bde77 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5
#9  0x00007f58af6caf38 in QTimer::timerEvent(QTimerEvent*) () from /usr/lib/libQt5Core.so.5
#10 0x00007f58af6bee63 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5
#11 0x00007f58b0a5e00c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#12 0x00007f58b0a634e6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#13 0x00007f58af68f89b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#14 0x00007f58af6e505d in QTimerInfoList::activateTimers() () from /usr/lib/libQt5Core.so.5
#15 0x00007f58af6e5561 in ?? () from /usr/lib/libQt5Core.so.5
#16 0x00007f58ab04d9fd in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#17 0x00007f58ab04dce0 in ?? () from /usr/lib/libglib-2.0.so.0
#18 0x00007f58ab04dd8c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#19 0x00007f58af6e623f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#20 0x00007f58af68d26a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#21 0x00007f58af69520c in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#22 0x000000000042ed66 in main ()
Comment 22 Thomas Lübking 2015-07-14 07:05:21 UTC 
Looks like a(n unrelated) bug in PlasmaQuick::Dialog, please file a new one against frameworks-plasma.
QScreen::availableGeometry just returns a private member, so that class either accesses a dangeling pointer or an out of bounds array.
Comment 23 Christoph Feck 2015-07-28 11:58:53 UTC 
*** Bug 350692 has been marked as a duplicate of this bug. ***
Comment 24 Thomas Lübking 2015-07-28 13:43:31 UTC 
*** Bug 350467 has been marked as a duplicate of this bug. ***
Comment 25 Christoph Feck 2015-08-02 09:34:00 UTC 
*** Bug 350710 has been marked as a duplicate of this bug. ***
Comment 26 Christoph Feck 2015-08-02 09:34:23 UTC 
*** Bug 350766 has been marked as a duplicate of this bug. ***
Comment 27 Christoph Feck 2015-08-02 09:34:45 UTC 
*** Bug 350800 has been marked as a duplicate of this bug. ***
Comment 28 Thomas Lübking 2015-08-14 13:26:45 UTC 
*** Bug 351257 has been marked as a duplicate of this bug. ***
Comment 29 Thomas Lübking 2015-08-22 18:19:00 UTC 
Bug's reported as NOT fixed in 5.5
https://bugreports.qt.io/browse/QTBUG-47385
Comment 30 Christoph Feck 2015-09-23 14:58:55 UTC 
*** Bug 352712 has been marked as a duplicate of this bug. ***
Comment 31 Thomas Lübking 2015-09-24 06:25:46 UTC 
*** Bug 353122 has been marked as a duplicate of this bug. ***
Comment 32 Thomas Lübking 2015-10-05 13:26:53 UTC 
Thats one of the many variants of

https://bugreports.qt.io/browse/QTBUG-42985

And no, not fixed, not even with all patches in that bug.
Please report more info there, to give them a better chance to fix it and raise awareness, the kde bugtracker doesn't help for that.
Comment 33 Thomas Lübking 2015-10-05 13:27:15 UTC 
*** Bug 351007 has been marked as a duplicate of this bug. ***
Comment 34 Thomas Lübking 2015-10-05 13:27:36 UTC 
*** Bug 351546 has been marked as a duplicate of this bug. ***
Comment 35 Thomas Lübking 2015-10-05 13:27:43 UTC 
*** Bug 348788 has been marked as a duplicate of this bug. ***
Comment 36 Bhushan Shah 2015-10-12 11:02:05 UTC 
*** Bug 353823 has been marked as a duplicate of this bug. ***
Comment 37 Damian Kaczmarek 2015-10-14 07:51:08 UTC 
According to this comment https://bugreports.qt.io/browse/QTBUG-42985?focusedCommentId=294803&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-294803 "KDE developers should make sure not to 1) assume that QScreen* returned from any Qt function is guaranteed to be non-null 2) hold any QScreen pointers." - so maybe it is a KDE bug after all?
Comment 38 Martin Flöser 2015-10-14 08:07:48 UTC 
> so maybe it is a KDE bug after all?

The specific case here does neither 1 nor 2. It's Qt itself crashing as they don't check 1 and 2.
Comment 39 Thomas Lübking 2015-10-14 08:33:47 UTC 
Fwwi, *every* single backtrace I've seen in this regard was a Qt internal nullptr resolution.

The design was changed and left tons of unconditional (primary) screen accesses in Qt behind and instead of going for the obvious and just add a dummy screen (preserving source compatibility as well), they chose to "if (QGuiApplication::primaryScreen()) { ... }" on every single occurrence. Workloading approach, but not our problem at all.

Once Qt stops crashing by itself, there *might* popup KDE (and other Qt client) code issues from "QWidget * QDesktopWidget::screen(int screen = -1)", but so far, we didn't make it into client code because Qt crashed before.
If we see them once, we got to fix them then.
Comment 40 Thomas Lübking 2015-10-26 09:01:28 UTC 
*** Bug 354387 has been marked as a duplicate of this bug. ***
Comment 41 kde 2015-11-10 20:26:36 UTC 
Is there any known workaround for this issue? I'm using KDE as my primary desktop for work and this is making life very difficult.
Comment 42 Thomas Lübking 2015-11-10 20:33:15 UTC 
a) Don't use Qt5 software
b) Don't change the screen layout/resolution/frequency while using Qt5 software
Comment 43 Thomas Lübking 2015-11-14 14:26:38 UTC 
*** Bug 355118 has been marked as a duplicate of this bug. ***
Comment 44 Marco Martin 2015-11-25 09:51:30 UTC 
*** Bug 355857 has been marked as a duplicate of this bug. ***
Comment 45 Thomas Lübking 2015-11-25 10:14:55 UTC 
*** Bug 355882 has been marked as a duplicate of this bug. ***
Comment 46 Thomas Lübking 2015-11-26 12:36:03 UTC 
*** Bug 355937 has been marked as a duplicate of this bug. ***
Comment 47 Thomas Lübking 2015-11-30 10:35:28 UTC 
*** Bug 356107 has been marked as a duplicate of this bug. ***
Comment 48 Thomas Lübking 2015-12-01 07:30:08 UTC 
*** Bug 356144 has been marked as a duplicate of this bug. ***
Comment 49 David Edmundson 2015-12-14 13:32:36 UTC 
*** Bug 353578 has been marked as a duplicate of this bug. ***
Comment 50 Kai Uwe Broulik 2015-12-15 22:37:46 UTC 
*** Bug 356674 has been marked as a duplicate of this bug. ***
Comment 51 Thomas Lübking 2016-01-26 20:56:35 UTC 
*** Bug 358605 has been marked as a duplicate of this bug. ***
Comment 52 Thomas Lübking 2016-03-04 16:06:10 UTC 
*** Bug 360079 has been marked as a duplicate of this bug. ***
Comment 53 Thomas Lübking 2016-03-09 20:34:14 UTC 
*** Bug 360337 has been marked as a duplicate of this bug. ***
Comment 54 Thomas Lübking 2016-03-15 09:42:55 UTC 
*** Bug 360548 has been marked as a duplicate of this bug. ***
Comment 55 Thomas Lübking 2016-03-18 09:18:11 UTC 
*** Bug 360684 has been marked as a duplicate of this bug. ***
Comment 56 Thomas Lübking 2016-04-13 07:11:33 UTC 
*** Bug 361704 has been marked as a duplicate of this bug. ***
Comment 57 Martin Steigerwald 2016-04-13 09:34:48 UTC 
Just to make it clear here, the QT-BUG – https://bugreports.qt.io/browse/QTBUG-42985 – also refers to disappearing windows, not just crashes. From reading from the QTBUG I bet the issue is fixed in Qt 5.5.1 with patches and hopefully in 5.6.
Comment 58 Thomas Lübking 2016-04-27 12:25:09 UTC 
*** Bug 362350 has been marked as a duplicate of this bug. ***
Comment 59 Michael Butash 2016-05-05 19:47:46 UTC 
Is a backport possible for 16.04 ubuntu users not likely to see this in lts until 18.04?

Sadly, kde4 was terrible with unfixed bugs for setting up xrandr geometry as well that made it unusable when relying on radeon modules, upgraded to 5 (and 16.04 to do so), was massively better, but affected by this now as well it seems.  Going back to 4 really isn't an option being left unresolved too.

I'm using 3x displays, 48" 4k samsung tv's as my desk monitors, which don't do dpms keepalive over hdmi cables it seems.  Rather they shut off/down, and "go away" on the wire to the video card and xrandr, leaving it without a native display, or your "dummy display" concept it seem to keep it sane when it has none.  Waking up the displays, and thus xrand + kde figuring out where to put things back to, is an entire crapshoot now whether it 1) lives perfect, 2) lives broken needing xrandr fixing, 3) needs sddm restart from different tty, or 4) needs rebooted as nothing wakes it up.  Feels windoze-y now.

Oddly, it doesn't always crash kwin, and sometimes recovers perfectly.  Other times not so much, but its very random sadly.  

I've created xrandr scripts myself and with arandr to deal with it when kde5 as a whole decides to go weird, but it's also seeming to have identity issues with what is the "primary" display as well, as it seems to change upon these events which is really primary, or which primary is really linked to which monitor index.  Sometimes I just have to try setting the primary monitor randomly to figure out which it thinks is currently actually display 2 for example.

SDDM also has recovery issues with are likely to be related but their own beast, yet systemic of the fact no one seems to actually test kde with multiple monitors extensively.  I was using kde4 happily with amd blob drivers and 6x 1080p montiors that did the setup itself for years, but using radeon now (with 4.x kernels that amd doesn't support yet for blob), which now works 2000x better, breaks this with xrandr quirks like this.
Comment 60 Thomas Lübking 2016-05-05 19:56:49 UTC 
This is not a bug in KDE (let alone KWin)

The bug exists in every Qt 5.5 version. Older Qt versions have randr related sefaults in QtQuick (will affect plasmashell, kwin and everything else that has QML bits) and so does at least Qt 5.6.0 (unstashed by the restorage of the pre 5.5 behavior to prevent these crashes)

Ubuntu could likely "backport" this in Qt - while the resolving commit is a bit bigger, the breaking one is just (afaics pretty much unmotivated other than the broken anyway QtQuick part)  http://code.qt.io/cgit/qt/qtbase.git/commit/src/plugins/platforms/xcb/qxcbconnection.cpp?id=51ada7734ad780178ecced11e0dff454dfc2e5f2
Comment 61 Thomas Lübking 2016-05-27 13:22:58 UTC 
*** Bug 363580 has been marked as a duplicate of this bug. ***
Comment 62 Thomas Lübking 2016-06-12 15:27:31 UTC 
*** Bug 364242 has been marked as a duplicate of this bug. ***
Comment 63 Thomas Lübking 2016-06-16 05:09:04 UTC 
*** Bug 364362 has been marked as a duplicate of this bug. ***
Comment 64 Thomas Lübking 2016-06-16 19:00:46 UTC 
*** Bug 364388 has been marked as a duplicate of this bug. ***
Comment 65 Thomas Lübking 2016-06-28 19:18:44 UTC 
*** Bug 364867 has been marked as a duplicate of this bug. ***
Comment 66 Thomas Lübking 2016-07-20 20:46:40 UTC 
*** Bug 365913 has been marked as a duplicate of this bug. ***
Comment 67 Nate Graham 2021-02-08 19:19:23 UTC 
*** Bug 360134 has been marked as a duplicate of this bug. ***
Comment 68 Nate Graham 2021-02-08 19:24:07 UTC 
*** Bug 348262 has been marked as a duplicate of this bug. ***
Comment 69 Nate Graham 2021-02-08 19:24:28 UTC 
*** Bug 358560 has been marked as a duplicate of this bug. ***
Comment 70 Nate Graham 2021-02-08 19:25:11 UTC 
*** Bug 351180 has been marked as a duplicate of this bug. ***
Comment 71 Nate Graham 2021-02-08 19:25:30 UTC 
*** Bug 346700 has been marked as a duplicate of this bug. ***
Comment 72 Nate Graham 2021-02-08 19:25:53 UTC 
*** Bug 339922 has been marked as a duplicate of this bug. ***
Comment 73 Nate Graham 2021-02-08 19:26:38 UTC 
*** Bug 380941 has been marked as a duplicate of this bug. ***
Comment 74 Nate Graham 2021-02-08 19:26:40 UTC 
*** Bug 359228 has been marked as a duplicate of this bug. ***
Comment 75 Nate Graham 2021-02-08 19:27:19 UTC 
*** Bug 355232 has been marked as a duplicate of this bug. ***
Comment 76 Nate Graham 2021-02-08 19:27:51 UTC 
*** Bug 360254 has been marked as a duplicate of this bug. ***
Comment 77 Nate Graham 2021-02-08 19:28:20 UTC 
*** Bug 343772 has been marked as a duplicate of this bug. ***
Comment 78 Nate Graham 2021-02-08 19:28:54 UTC 
*** Bug 345205 has been marked as a duplicate of this bug. ***
Comment 79 Nate Graham 2021-02-08 19:28:57 UTC 
*** Bug 344773 has been marked as a duplicate of this bug. ***
Comment 80 Nate Graham 2021-02-08 19:28:58 UTC 
*** Bug 343982 has been marked as a duplicate of this bug. ***
Comment 81 Nate Graham 2021-02-08 19:29:13 UTC 
*** Bug 345129 has been marked as a duplicate of this bug. ***
Comment 82 Nate Graham 2021-02-08 19:29:46 UTC 
*** Bug 362964 has been marked as a duplicate of this bug. ***
Comment 83 Nate Graham 2021-02-08 19:29:50 UTC 
*** Bug 369221 has been marked as a duplicate of this bug. ***
Comment 84 Nate Graham 2021-02-08 19:29:54 UTC 
*** Bug 366070 has been marked as a duplicate of this bug. ***
Comment 85 Nate Graham 2021-02-08 19:30:59 UTC 
*** Bug 347524 has been marked as a duplicate of this bug. ***