Project

General

Profile

Bug #3001

screen freeze after restart of polkit, dbus, xdm

nona - 29 days ago - . Updated 28 days ago.

Status:
unconfirmed
Priority:
bug
Assignee:
-
% Done:

0%


Description

Hello,

When I do this,

#+begin_src bash
sudo killall -HUP polkitd
sudo rc-service dbus restart
sudo rc-service xdm restart
#+end_src

the screen has (what I will probably miscall) an overlay problem: the screen gets frozen, although I get a little strip at the bottom with a bit of indistinguishable motion afterwards or uncontrollably jumping from one unsusable graphical interface to the other. It would seem as if the system is trying to present two screens at once. I am able to execute some commands blindly, as in controlling the LXDE panel with the keyboard and turning off the computer--say =lxpanelctl=.

I was originally trying to debug an overuse of memory from =polkit= (leaks?).

What I was expecting was for the current session to close and go back to type my user and password on =lxdm=.

  • System

#+begin_src bash
uname -r
#+end_src

#+RESULTS:
: 5.11.2-gnu-1

#+begin_src bash :results output
lshw | head -n 20
#+end_src

#+RESULTS:
#+begin_example
localhost
description: Computer
width: 64 bits
capabilities: smp vsyscall32
,*-core
description: Motherboard
physical id: 0
,*-memory
description: System memory
physical id: 0
size: 7936MiB
,*-cpu
product: AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx
vendor: Advanced Micro Devices [AMD]
physical id: 1
bus info: cpu@0
size: 1368MHz
capacity: 2GHz
width: 64 bits
capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp x86-64 constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb hw_pstate sme ssbd sev vmmcall sev_es fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 xsaves clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov succor smca cpufreq
#+end_example

#+begin_src bash
pacman -Q polkit dbus lightdm openrc
#+end_src

#+RESULTS:
polkit 0.118-1.nonsystemd1
dbus 1.12.16-5.nonsystemd1
lightdm 1:1.30.0-4
openrc 0.42.1-7

History

#1

Updated by freemor 28 days ago

Can you attach a photo of the screen messing up.

I can't be sure from your description but it sounds kind of like either a h/V sync issue or a video card being incorrectly initialized. (there is often mode switches that happen when transitioning to/from DMs)

Thanks

#2

Updated by freemor 28 days ago

Also why are you finding it necessary to

#+begin_src bash
sudo killall -HUP polkitd
sudo rc-service dbus restart
sudo rc-service xdm restart
#+end_src

that seems like a fairly drastic maneuver. So I'm wondering the reason for such as opposed to say logging out of and back into your DE.

#3

Updated by nona 28 days ago

freemor wrote:

Can you attach a photo of the screen messing up.

I can't be sure from your description but it sounds kind of like either a h/V sync issue or a video card being incorrectly initialized. (there is often mode switches that happen when transitioning to/from DMs)

Thanks

Sure, I'll do it in some hours. Thank you.

Nevermind, I tried to restart polkit again, and it didn't work. I ended up in the same spot as before. I tried with the regular print-screen command that I have in my lxde-rc.xml
<keybind key="Print">
<action name="Execute">
<execute>scrot</execute>
</action>
</keybind>

But I just got a clear shot of the screen that was supposed to die. Nothing looks funny.

#4

Updated by nona 28 days ago

freemor wrote:

that seems like a fairly drastic maneuver. So I'm wondering the reason for such as opposed to say logging out of and back into your DE.

Initially, I wanted polkit to restart (it didn't, it just died), then I thought of forcing it to restart with dbus (it didn't either) and finally, I thought of just restarting the XDM service. When this happened, it seemed interesting. Upon restart, a similar behaviour lead me to create this report. Funny, right?

By the way, if you have a suggestion to restart polkit without killing my session, I would appreciate it.

Also available in: Atom PDF