Since starting "mpv" after reboot, again, broke kwin/plasmashell, who knows...
I thought of:
Settings>Compositor Settings for Desktop Effects
untick "allow application to block compositing"
Then "apply"
=> kwin/plasmashell crash!
Then logout: no way to have cursor/mouse pointer with sddm
Even aft
I've spent huge time perusing the journalctl -b -n output: this is why I
haven't came sooner here.
I might have found a couple of things, but not sure yet.
I, below, answer the questions you asked.
On Saturday, May 27, 2017 8:02:02 PM CEST Felix Miata wrote:
> inkbottle composed on 2017-05-27 17:
kamaraju kusumanchi composed on 2017-05-28 11:00 (UTC-0400):
> Felix Miata wrote:
>> ISTR recently seeing KDE people with sddm errors solve their trouble by
>> switching to a different display manager, TDM, lightdm, KDM, GDM, so
>> including
>> sddm in your Googling too might produce fruit.
> N
On Sat, May 27, 2017 at 8:02 PM, Felix Miata wrote:
>
> ISTR recently seeing KDE people with sddm errors solve their trouble by
> switching to a different display manager, TDM, lightdm, KDM, GDM, so including
> sddm in your Googling too might produce fruit.
>
Hi Felix,
Not sure if you are aware.
inkbottle composed on 2017-05-27 17:47 (UTC+0200):
>> > (dual screen w. display port (rather external than dual), thinkpad x230,
>> > intel graphics, lid closed: I am the one and only experiencing that...
>> > however that might change when testing-sid is the new stable)
Please provide output fro
On Saturday, May 27, 2017 4:38:09 PM CEST Ferdinand Thommes wrote:
> Did you check the journal? A quest like 'journalctl -b -1' would show the
Thanks for the command...
It happens there are tones of errors,
from 3 sources
kscreen (like journalctl -b -3|egrep kscreen|wc -l =>
Did you check the journal? A quest like 'journalctl -b -1' would show the logs
of your last boot, not the current one. I have not experienced that behaviour
in Sid at all.
> inkbottle hat am 26. Mai 2017 um 18:32 geschrieben:
>
>
> Still this very problematic issue I am the only one to exper
On Friday, May 26, 2017 6:32:44 PM CEST inkbottle wrote:
> Still this very problematic issue I am the only one to experience.
>
> 1 - upgrade
> 2 - clicking "reboot"
> a - take at least 4 minutes to.. actually only logout.
> b - then click on "reboot"
> Does reboot but actually it hasn't shown the
Still this very problematic issue I am the only one to experience.
1 - upgrade
2 - clicking "reboot"
a - take at least 4 minutes to.. actually only logout.
b - then click on "reboot"
Does reboot but actually it hasn't shown the "booting debian splash screen" (I
might have missed it though).
c - w
9 matches
Mail list logo
