App does not respect Gnome's 'Dark Mode' when toggled.
Expected Behavior
Application should switch to dark theme when gnome 'Dark Mode' button is toggled.
Steps To Reproduce
Installed SimpleX debian pkg.
Changed Settings => Appearance => Color mode => to System
Also tried launching the app from the terminal to force dark mode and that failed as well
GTK_THEME=Adwaita-dark /opt/simplex/bin/simplex
Relevant log output
D: useDatabaseKey true
D: sendCmd: apiSetAppFilePaths
D: sendCmd response type cmdOk
D: sendCmd: apiSetEncryptLocalFiles
D: sendCmd response type cmdOk
D: sendCmd: showActiveUser
D: sendCmd response type activeUser
D: user: User(remoteHostId=null, userId=1, userContactId=1, localDisplayName=Seth-mini, profile=LocalProfile(profileId=1, displayName=Seth-mini, fullName=, image=null, localAlias=, contactLink=null, preferences=null), fullPreferences=FullChatPreferences(timedMessages=TimedMessagesPreference(allow=YES, ttl=null), fullDelete=SimpleChatPreference(allow=NO), reactions=SimpleChatPreference(allow=YES), voice=SimpleChatPreference(allow=YES), calls=SimpleChatPreference(allow=YES)), activeUser=true, showNtfs=true, sendRcptsContacts=true, sendRcptsSmallGroups=true, viewPwdHash=null, uiThemes=null)
D: sendCmd: apiSetNetworkConfig
D: sendCmd response type cmdOk
D: sendCmd: startChat
D: sendCmd response type chatStarted
D: sendCmd: listUsers
D: sendCmd response type usersList
D: sendCmd: apiShowMyAddress
D: sendCmd response type userContactLink
D: sendCmd: apiGetChatItemTTL
D: sendCmd response type chatItemTTL
D: sendCmd: apiGetChats
D: sendCmd response type apiChats
D: ChatController startReceiver
D: sendCmd: setLocalDeviceName
D: sendCmd response type cmdOk
D: startChat: started
D: Unexpected JSON token at offset 8: Serializer for subclass 'hostConnected' is not found in the polymorphic scope of 'CR' at path: $.resp
Check if class with serial name 'hostConnected' exists and serializer is registered in a corresponding SerializersModule.
To be registered automatically, class 'hostConnected' has to be '@Serializable', and the base class 'CR' has to be sealed and '@Serializable'.
JSON input: {"resp":{"type":"hostConnected","protocol":"smp","transportHost":"smp14.simplex.im"}}
D: chatRecvMsg: * hostConnected
D: chatRecvMsg json: {"resp":{"type":"hostConnected","protocol":"smp","transportHost":"smp14.simplex.im"}}
D: unsupported event: * hostConnected
D: Unexpected JSON token at offset 8: Serializer for subclass 'hostConnected' is not found in the polymorphic scope of 'CR' at path: $.resp
Check if class with serial name 'hostConnected' exists and serializer is registered in a corresponding SerializersModule.
To be registered automatically, class 'hostConnected' has to be '@Serializable', and the base class 'CR' has to be sealed and '@Serializable'.
JSON input: {"resp":{"type":"hostConnected","protocol":"smp","transportHost":"smp12.simplex.im"}}
D: chatRecvMsg: * hostConnected
D: chatRecvMsg json: {"resp":{"type":"hostConnected","protocol":"smp","transportHost":"smp12.simplex.im"}}
D: unsupported event: * hostConnected
D: Unexpected JSON token at offset 8: Serializer for subclass 'hostConnected' is not found in the polymorphic scope of 'CR' at path: $.resp
Check if class with serial name 'hostConnected' exists and serializer is registered in a corresponding SerializersModule.
To be registered automatically, class 'hostConnected' has to be '@Serializable', and the base class 'CR' has to be sealed and '@Serializable'.
JSON input: {"resp":{"type":"hostConnected","protocol":"smp","transportHost":"smp8.simplex.im"}}
D: chatRecvMsg: * hostConnected
D: chatRecvMsg json: {"resp":{"type":"hostConnected","protocol":"smp","transportHost":"smp8.simplex.im"}}
D: unsupported event: * hostConnected
D: Unexpected JSON token at offset 8: Serializer for subclass 'hostConnected' is not found in the polymorphic scope of 'CR' at path: $.resp
Check if class with serial name 'hostConnected' exists and serializer is registered in a corresponding SerializersModule.
To be registered automatically, class 'hostConnected' has to be '@Serializable', and the base class 'CR' has to be sealed and '@Serializable'.
JSON input: {"resp":{"type":"hostConnected","protocol":"smp","transportHost":"smp9.simplex.im"}}
D: chatRecvMsg: * hostConnected
D: chatRecvMsg json: {"resp":{"type":"hostConnected","protocol":"smp","transportHost":"smp9.simplex.im"}}
D: unsupported event: * hostConnected
D: Unexpected JSON token at offset 8: Serializer for subclass 'hostConnected' is not found in the polymorphic scope of 'CR' at path: $.resp
Check if class with serial name 'hostConnected' exists and serializer is registered in a corresponding SerializersModule.
To be registered automatically, class 'hostConnected' has to be '@Serializable', and the base class 'CR' has to be sealed and '@Serializable'.
JSON input: {"resp":{"type":"hostConnected","protocol":"smp","transportHost":"smp10.simplex.im"}}
D: chatRecvMsg: * hostConnected
D: chatRecvMsg json: {"resp":{"type":"hostConnected","protocol":"smp","transportHost":"smp10.simplex.im"}}
D: unsupported event: * hostConnected
D: sendCmd: listRemoteHosts
D: sendCmd response type remoteHostList
D: Unexpected JSON token at offset 8: Serializer for subclass 'hostConnected' is not found in the polymorphic scope of 'CR' at path: $.resp
Check if class with serial name 'hostConnected' exists and serializer is registered in a corresponding SerializersModule.
To be registered automatically, class 'hostConnected' has to be '@Serializable', and the base class 'CR' has to be sealed and '@Serializable'.
JSON input: {"resp":{"type":"hostConnected","protocol":"smp","transportHost":"smp11.simplex.im"}}
D: chatRecvMsg: * hostConnected
D: chatRecvMsg json: {"resp":{"type":"hostConnected","protocol":"smp","transportHost":"smp11.simplex.im"}}
D: unsupported event: * hostConnected
D: chatRecvMsg: newChatItem
D: notifyMessageReceived #3
D: chatRecvMsg: networkStatuses
D: Unexpected JSON token at offset 8: Serializer for subclass 'userContactSubSummary' is not found in the polymorphic scope of 'CR' at path: $.resp
Check if class with serial name 'userContactSubSummary' exists and serializer is registered in a corresponding SerializersModule.
To be registered automatically, class 'userContactSubSummary' has to be '@Serializable', and the base class 'CR' has to be sealed and '@Serializable'.
JSON input: {"resp":{"type":"userContactSubSummary.....
D: chatRecvMsg: * userContactSubSummary
D: chatRecvMsg json: {"resp":{"type":"userContactSubSummary","user":{"userId":1,"agentUserId":"1","userContactId":1,"localDisplayName":"Seth-mini","profile":{"profileId":1,"displayName":"Seth-mini","fullName":"","localAlias":""},"fullPreferences":{"timedMessages":{"allow":"yes"},"fullDelete":{"allow":"no"},"reactions":{"allow":"yes"},"voice":{"allow":"yes"},"calls":{"allow":"yes"}},"activeUser":true,"showNtfs":true,"sendRcptsContacts":true,"sendRcptsSmallGroups":true},"userContactSubscriptions":[{"userContact":{"userContactLinkId":1,"connReqContact":"simplex:/contact#/?v=2-5&smp=smp%3A%2F%2F6iIcWT_dF2zN_w5xzZEY7HI2Prbh3ldP07YTyDexPjE%3D%40smp10.simplex.im%2F0awCtuDqCuRfxoohg2JubSdL5Fr5vGH2%23%2F%3Fv%3D1-2%26dh%3DMCowBQYDK2VuAyEA6e09xL1XzuP4jvxSKCEYUacneCrWv9HWcaF21vAsKyQ%253D%26srv%3Drb2pbttocvnbrngnwziclp2f4ckjq65kebafws6g4hy22cdaiv5dwjqd.onion"}}]}}
D: unsupported event: * userContactSubSummary
D: chatRecvMsg: chatItemDeleted
Is there an existing issue for this?
Platform
Linux
OS version
PureOS 11 (Crimson)
App version
5.8.1
Current Behavior
App does not respect Gnome's 'Dark Mode' when toggled.
Expected Behavior
Application should switch to dark theme when gnome 'Dark Mode' button is toggled.
Steps To Reproduce
Installed SimpleX debian pkg.
Changed Settings => Appearance => Color mode => to System
Also tried launching the app from the terminal to force dark mode and that failed as well
GTK_THEME=Adwaita-dark /opt/simplex/bin/simplex
Relevant log output