You are not logged in.
Am I the only one who is suffering frequent plasmashell crashes without visible cause in the last time?
Offline
Am I the only one who is suffering frequent plasmashell crashes without visible cause in the last time?
No, you're not :-(
Offline
I found the according bug I suppose:
https://bugs.kde.org/show_bug.cgi?id=349794
https://bugs.kde.org/show_bug.cgi?id=349677
Offline
Am I the only one who is suffering frequent plasmashell crashes without visible cause in the last time?
I'm getting crashes with no real detail until I noticed that my HipChat client would be doing it's pulse thing when I get new messages causing a crash.
Offline
I don't use/have HipChat so that can't be the cause...
Offline
Am I the only one who is suffering frequent plasmashell crashes without visible cause in the last time?
No, it crashes pretty frequently on my laptop too, since the 5.3.2 update.
Offline
I just disabled the "Instant Messaging" from the System Tray settings. Subjective feeling is that it is better, no crashes for the last two hours.
Offline
Is it possible to make it so using the krunner shortcut will close it if the window is open? Alternatively (if not possible), by pressing enter with empty input?
Offline
Has anyone else the problem that plasma-nm has no icon after boot?
As a workaound I first set plasma-nm to hidden and then to visible again.
Offline
i have the same problem and use the same "solution"
Offline
I have problems with my new 4K display.
When I make a off/on cicle, the screen won't work because he says has lost the signal, but if I change to VT cosole, the screen/signal is back, but when switch again to VT7 (KDE VT), the screen losing the signal again.
This behavior not happen in SDDM screen, but if I enter to plasma, and I make again the on/off cicle, the error comes again
in dmseg see a tons of programs have a segfault (telegram-desktop, yakuake, plasma, kwin..)
if turn off the copositor and desktop effects. and switch render to Xrender, if making the off/on cicle again, the error is "gone". but I get segfaults again. like kwin, plasmashell, etc.
anyone has the same problem?
the screen is a Asus PB287Q and a EVGA GTX770 2GB (beta drivers) connected with DP (1.2). all with Plasma 5.3.2-2
EDIT: one of the segfaults http://sl1pkn07.wtf/paste/view/b54cc1e0 http://sl1pkn07.wtf/paste/view/5b593850
greetings
Last edited by sl1pkn07 (2015-07-13 15:56:04)
Offline
I have problems with my new 4K display.
This sounds like Xorg is crashing on the display because of some bug in either the Xserver handling that monitor, or in the DRM/kernel layer handling the physical interface. If its over HDMI 2.0 or Displayport 1.3 it is brand new tech that might not be well baked, especially if you are using an AMD display adapter.
You can easily test this by running startx without KDE set from a VT. If xorg doesn't crash, its a kde bug. Everything else is crashing because Kwin is crashing. Kwin is crashing in refresh rate handling in Qt libs, which like I said is probably Xorg crashing on some xrandr query during startup it cannot handle, but if it is not it might be a bug in Qt.
You want to know that its a Qt / KDE bug first though, so try running startx. And then if it is you should either enable testing or manually pull down Qt 5.5 to see if its fixed there, because every major Qt release fixes a ton of this stuff.
Offline
nope, the Xorg still running without any error, is in plasma5/qt5 side. have active testing repo. no success (test with testing/extra)
Last edited by sl1pkn07 (2015-07-15 13:30:58)
Offline
You could try clearing your preferences and seeing if default plasma / kwin works. If you don't want to lose all your configurations just rename .config for a bit and try it clean slate. It might be trying to set an invalid refresh rate in krandr, for example.
Offline
I'm really looking forward to kf5, will there be a walkthru/step-by-step guide to switching from kde4 to kf5?
There seems to be lots of info about what to do but it's all over the net and somewhere central specific to Arch would be nice. Perhaps a wiki page?
Thoughts?
Offline
I'm really looking forward to kf5, will there be a walkthru/step-by-step guide to switching from kde4 to kf5?
There seems to be lots of info about what to do but it's all over the net and somewhere central specific to Arch would be nice. Perhaps a wiki page?
Thoughts?
You should really read the Arch news posts, this one in particular. Also have a read of the Intro and Installation sections of the KDE article.
In short, there is no sudden transition. KF5 and Plasma are already here, in the official repos, and applications are being ported over to KF5 one by one.
Offline
For a while with recent releases plasma (and sometimes krunner) keeps segfaulting at random times and nearly always on logout. Any one else experiencing this / found a fix?
And if I kquitapp plasmashell, it segfaults and the crash handler restarts it. (Intel graphics)
Last edited by courageux (2015-07-15 15:15:15)
Offline
For a while with recent releases plasma (and sometimes krunner) keeps segfaulting at random times and nearly always on logout. Any one else experiencing this / found a fix?
And if I kquitapp plasmashell, it segfaults and the crash handler restarts it. (Intel graphics)
The crash handler always restarts plasmashell while kwin is running a plasma session. I think thats intended. Random segfaults are not, but Plasma 5 is pretty much a whole new stack so it should surprise no one it crashes in places. At least it almost always restarts. I get 2-3 segfaults a day but just ignore them now because, one, its almost always in multithreading libraries.
Offline
I did a KF5/Plasma fresh install.
All works fine except a issue with the splash screen whatever the theme selected :
The progress bar doesn't work, it stays static, there is no visual feedback of the kde startup.
any ideas ?
Last edited by hamelg (2015-07-15 20:58:57)
Offline
I did a KF5/Plasma fresh install.
All works fine except a issue with the splash screen whatever the theme selected :
The progress bar doesn't work, it stays static, there is no visual feedback of the kde startup.
any ideas ?
I have two PCs running Plasma 5, and on one the progress bar works fine and on the other it immediately freezes. The difference is the first is a notebook with a 1080p panel, and the later is a desktop with 6 displays.
If its doing a significant amount of modesetting of displays behind the scenes (ie, SDDM or TTY -> Xorg) the displays freeze out during it, and then Kwin won't paint anything until they are configured properly so your progress bar hangs. It might have a QOA fix in the future but its mostly the display freezing for krandr more than anything else.
At least thats my experience. You can disable the splash screen if you want more visual feedback, because then you would see Plasma loading its components on the desktop. It usually goes wallpaper- > widgets -> panel.
Last edited by zanny (2015-07-15 21:02:03)
Offline
For a while with recent releases plasma (and sometimes krunner) keeps segfaulting at random times and nearly always on logout. Any one else experiencing this / found a fix?
And if I kquitapp plasmashell, it segfaults and the crash handler restarts it. (Intel graphics)
I have that segfault at logout every time (nvidia driver).
Offline
I'm having the most annoying bug ever : when I right click any title bar, the context window won't disappear, unless I click an action in it.
Last edited by Tromzy (2015-07-16 11:48:52)
Offline
Something similar here, too. It does work sometimes though
[ Arch x86_64 | linux | Framework 13 | AMD Ryzen™ 5 7640U | 32GB RAM | KDE Plasma Wayland ]
Offline
@Tromzy: just noticed the same thing here…
Offline
I'm having the most annoying bug ever : when I right click any title bar, the context window won't disappear, unless I click an action in it.
Or rightclick the titlebar again. Which is a bit better.
Offline