Bug 384222 - Do not changed background on login screen
Summary: Do not changed background on login screen
Status: RESOLVED NOT A BUG
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_sddm (show other bugs)
Version: 5.8.7
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-31 10:58 UTC by Yura Shinkarev
Modified: 2017-09-01 09:26 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Login screen settings (51.76 KB, image/png)
2017-08-31 10:58 UTC, Yura Shinkarev
Details
theme.conf.user (40 bytes, text/plain)
2017-08-31 11:13 UTC, Yura Shinkarev
Details
systemsettings5.log (394 bytes, text/x-log)
2017-08-31 11:22 UTC, Yura Shinkarev
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yura Shinkarev 2017-08-31 10:58:38 UTC
Created attachment 107614 [details]
Login screen settings

OS: Kubuntu 16.04 amd64
Plasma: 5.8.7
Can not change background color.
Open 'Login screen (SDDM)' from main menu.
Click on 'Background' > 'Load from file' > choose png/jpg file with resolution as my notebook has. Click 'Apply'. 
But nothing changed.
I still see default blue background.
Comment 1 David Edmundson 2017-08-31 11:07:30 UTC
Can you run systemsettings5 from a command line, reproduce and send me the output. 

Do you get a prompt for a password?

Can you include your /usr/share/sddm/themes/breeze/theme.conf.user

Then set this status back to "unconfirmed"
Comment 2 Yura Shinkarev 2017-08-31 11:13:45 UTC
Created attachment 107615 [details]
theme.conf.user

/usr/share/sddm/themes/breeze/theme.conf.user
Comment 3 Yura Shinkarev 2017-08-31 11:22:36 UTC
Created attachment 107617 [details]
systemsettings5.log

When I click on 'Login screen (SDDM)' item, I get lines in console:
QDBusArgument: read from a write-only object
QDBusArgument: read from a write-only object
QDBusArgument: read from a write-only object
true

When I click on 'Load from file', get:
kf5.kio.core: KSambaShare: Could not find smb.conf!

When I press ESC at opened choose file dialog I get:
XcbConnection: XCB error: 3 (BadWindow), sequence: 4170, resource id: 33569820, major code: 40 (TranslateCoords), minor code: 0

When I press next 'Apply', then showing dialog 'Authentication Required', I get in console:
idx: 0
And some later:
kf5.kauth: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
Save Failed
"DBus Backend error: could not contact the helper. Connection error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.. Message error: "
"DBus Backend error: could not contact the helper. Connection error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.. Message error: "

I input my password. Nothing new in console. 

Strange. I repeat and get some another log.
Comment 4 Yura Shinkarev 2017-08-31 11:28:03 UTC
I record video too: https://youtu.be/nNhQUIW7npA
Comment 5 Yura Shinkarev 2017-08-31 11:30:30 UTC
See from comment3 https://bugs.kde.org/show_bug.cgi?id=384222#c3
Comment 6 David Edmundson 2017-08-31 11:41:04 UTC
>kf5.kauth: "Did not receive a reply. Possible causes include: the remote
application did not send a reply, the message bus security policy blocked the
reply, the reply timeout expired, or the network connection was broken."
Save Failed

Well that explains our problem.

The bit of code that runs as root to update the SDDM settings is either crashing or getting blocked.

That's tricky to debug.

You can try running:
 sudo /usr/lib64/libexec/kauth/kcmsddm_authhelper


then clicking apply from system settings in the next 10 seconds. It should use the executable we started and can then get output. Or even a gdb trace if possible?
Comment 7 Yura Shinkarev 2017-08-31 11:57:39 UTC
I have kcmsddm_authhelper in only specific path: usr/lib/x86_64-linux-gnu/libexec/kauth/kcmsddm_authhelper
Again record video: https://youtu.be/86ZEUATBlp8
kcmsddm_authhelper have no output in console.
Sorry, I have no necessary skills and do not understand what'is gdb and what I need todo more.
Comment 8 Yura Shinkarev 2017-08-31 16:45:07 UTC
Hm, I'm confused.
I'm power off my notebook. Then power on and on login I see correct new background.
But if I lock screen/sleep device and switch on again I see default blue background. Is it correctly? Or in all cases should be one background?
Comment 9 Rog131 2017-08-31 21:04:48 UTC
(In reply to Yura Shinkarev from comment #8)
> Hm, I'm confused.
> I'm power off my notebook. Then power on and on login I see correct new
> background.
> But if I lock screen/sleep device and switch on again I see default blue
> background. Is it correctly? Or in all cases should be one background?

Lock screen background: KDE System Settings > Desktop Behavior > Screen Locking - Wallpaper tab
Comment 10 David Edmundson 2017-09-01 09:26:50 UTC
>I'm power off my notebook. Then power on and on login I see correct new background.

So it worked \o/