https://labs.parabola.nu/https://labs.parabola.nu/favicon.ico?15367742552021-03-23T20:00:06ZParabola Issue TrackerPackages - Bug #3001: screen freeze after restart of polkit, dbus, xdmhttps://labs.parabola.nu/issues/3001?journal_id=159822021-03-23T20:00:06Zfreemor
<ul></ul><p>Can you attach a photo of the screen messing up.</p>
<p>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)</p>
<p>Thanks</p> Packages - Bug #3001: screen freeze after restart of polkit, dbus, xdmhttps://labs.parabola.nu/issues/3001?journal_id=159892021-03-23T20:12:09Zfreemor
<ul></ul><p>Also why are you finding it necessary to </p>
<pre><code>#+begin_src bash<br /> sudo killall -HUP polkitd<br /> sudo rc-service dbus restart<br /> sudo rc-service xdm restart<br /> #+end_src</code></pre>
<p>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.</p> Packages - Bug #3001: screen freeze after restart of polkit, dbus, xdmhttps://labs.parabola.nu/issues/3001?journal_id=159902021-03-23T20:30:57Znona
<ul></ul><p>freemor wrote:</p>
<blockquote>
<p>Can you attach a photo of the screen messing up.</p>
</blockquote>
<p><del>Sure, I'll do it in some hours. Thank <em>you</em>.</del></p>
<p>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<br /> <keybind key="Print"><br /> <action name="Execute"><br /> <execute>scrot</execute><br /> </action><br /> </keybind></p>
<p>But I just got a clear shot of the screen that was supposed to die. Nothing looks funny.</p> Packages - Bug #3001: screen freeze after restart of polkit, dbus, xdmhttps://labs.parabola.nu/issues/3001?journal_id=159922021-03-23T20:38:08Znona
<ul></ul><p>freemor wrote:</p>
<blockquote>
<p>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.</p>
</blockquote>
<p>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?</p>
<p>By the way, if you have a suggestion to restart polkit without killing my session, I would appreciate it.</p>