http://bugzilla.suse.com/show_bug.cgi?id=1080305 http://bugzilla.suse.com/show_bug.cgi?id=1080305#c5 Ancor Gonzalez Sosa <ancor@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ancor@suse.com Flags| |needinfo?(projects.rg@smart | |.ms) --- Comment #5 from Ancor Gonzalez Sosa <ancor@suse.com> --- This is at the end of the YaST logs. Right before everything blows away: modules/Service.rb:168 Reloading service 'display-manager' yast2/systemctl.rb:32 systemctl show display-manager.service --property=Id --property=MainPID --property=Description --property=LoadState --property=ActiveState --property=SubState --property=UnitFileState --property=FragmentPath yast2/systemctl.rb:32 systemctl reload display-manager.service IMHO this is a problem in the display manager service. Reloading it should not cause an full X11 restart. That used to happen in the very early versions of Tumbleweed in almost every display-manager update, but it got fixed long time ago. I assume a similar fix can/must be applied here. Which display manager / desktop environment do you use? -- You are receiving this mail because: You are on the CC list for the bug.