[systemsettings] [Bug 389068] New: systemsettings on wayland exits on mouse configuration
bugzilla_noreply at kde.org
bugzilla_noreply at kde.org
Tue Jan 16 20:46:47 GMT 2018
https://bugs.kde.org/show_bug.cgi?id=389068
Bug ID: 389068
Summary: systemsettings on wayland exits on mouse configuration
Product: systemsettings
Version: 5.11.95
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: kcm_mouse
Assignee: unassigned-bugs at kde.org
Reporter: bug2017 at wolke7.net
CC: unassigned-bugs at kde.org
Target Milestone: ---
It tries to access some X11 stuff while running on wayland.
Not a crash but exits with code 1:
Using Wayland-EGL
Using the 'xdg-shell-v6' shell integration
KActivities: Database connection:
"kactivities_db_resources_139755836218368_readonly"
query_only: QVariant(qlonglong, 1)
journal_mode: QVariant(QString, "wal")
wal_autocheckpoint: QVariant(qlonglong, 100)
synchronous: QVariant(qlonglong, 0)
Nothing to load - the client id is empty
Nothing to load - the client id is empty
Trying to convert empty KLocalizedString to QString.
Trying to convert empty KLocalizedString to QString.
Trying to convert empty KLocalizedString to QString.
Empty filename passed to function
KActivitiesStats( 0x55bf40cd16a0 ) ResultModelPrivate::onResultScoreUpdated
result added: "kcm:kcm_keyboard.desktop" score: 4 last: 1516135619 first:
1511554586
Trying to convert empty KLocalizedString to QString.
Trying to convert empty KLocalizedString to QString.
Trying to convert empty KLocalizedString to QString.
Empty filename passed to function
KActivitiesStats( 0x55bf40cd16a0 ) ResultModelPrivate::onResultScoreUpdated
result added: "kcm:joystick.desktop" score: 0 last: 1516135623 first:
1516135623
kcm_input: Using X11 backend
X Error of failed request: BadAtom (invalid Atom parameter)
Major opcode of failed request: 131 (XInputExtension)
Minor opcode of failed request: 59 ()
Atom id in failed request: 0x0
Serial number of failed request: 23
Current serial number in output stream: 23
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
More information about the Unassigned-bugs
mailing list