https://bugs.kde.org/show_bug.cgi?id=478780
--- Comment #4 from yun...@proton.me ---
Similar error on another Intel laptop.
Resolution: 2560x1600 (16:10)
Scale: 100%
Refresh Rate: 60Hz & 90Hz & 120Hz
```
Dec 21 18:19:29 fedora kwin_wayland[1659]: QObject::startTimer: Timers cannot
be started from another thread
Dec 21 18:19:30 fedora kwin_wayland[1659]: QObject::killTimer: Timers cannot be
stopped from another thread
Dec 21 18:19:31 fedora kwin_wayland[1659]: QObject::startTimer: Timers cannot
be started from another thread
Dec 21 18:19:32 fedora kwin_wayland[1659]: QObject::killTimer: Timers cannot be
stopped from another thread
Dec 21 18:19:32 fedora kwin_wayland[1659]: QObject::startTimer: Timers cannot
be started from another thread
Dec 21 18:19:33 fedora kwin_wayland[1659]: QObject::killTimer: Timers cannot be
stopped from another thread
Dec 21 18:19:33 fedora kwin_wayland[1659]: QSqlDatabasePrivate::database:
requested database does not belong to the calling thread.
Dec 21 18:19:33 fedora kwin_wayland[1659]: kde.plasma.activitiesstats:
PlasmaActivities: Database is not open: "" "" QSqlError("", "Driver not
loaded", "Driver not loaded")
Dec 21 18:19:33 fedora kwin_wayland[1659]: kde.plasma.activitiesstats: Plasma
Activities ERROR: There is no database. This probably means that you do not
have the Activity Manager running, or that something else is broken on your
system. Recent documen>
Dec 21 18:19:33 fedora kwin_wayland[1659]: QObject::startTimer: Timers cannot
be started from another thread
Dec 21 18:19:34 fedora kwin_wayland[1659]: QObject::killTimer: Timers cannot be
stopped from another thread
```
--
You are receiving this mail because:
You are watching all bug changes.
