Black Screen on Login / Crash on Arch/Manjaro (Qt 5.15.1) (EventCalendar v68 and below) #154
Comments
|
I need the segfault logs, not the logs from when it was running fine. Unfortunately the DrKonqi is in the system tray, which you can't access when plasmashell has crashed. Krunner should still work even if Copy the stack trace in the developer info tab (don't submit it to kde). You should also be able to open firefox with krunner too. |
|
Gonna need to be more specific. I installed |
|
It seems that only v69 release is compatible with qt-declarative 5.15.1. I tried old v66, v67, and v68, all of them break plasmashell. |
|
Then it's either: v68...v69
Will check both this afternoon. Thanks for figuring out that it's probably people using an older version of the widget. Does AUR not automatically update? Or are people not uninstalling eventcalendar in |
# First uninstall v69
kpackagetool5 --type=Plasma/Applet --remove org.kde.plasma.eventcalendar # ~/.local/share/plasma/plasmoids/...
pacman -R plasma5-applets-eventcalandar # /usr/share/plasma/plasmoids/...
# Then installed v68 from git
git clone https://github.com/Zren/plasma-applet-eventcalendar
cd plasma-applet-eventcalendar
git checkout v68
kpackagetool5 --type=Plasma/Applet --install package/
kstart5 -- plasmashell --replace
# crashed!Now to isolate the commit that fixes the bug with git checkout 83e08ab; kpackagetool5 --type=Plasma/Applet --upgrade package/; kstart5 -- plasmashell --replaceNote that |
|
Having this applet installed from AUR should get updated in the user side, right? |
|
I don't use Arch/AUR, so I don't know if it updates manually or when pacman updates. Arch Linux / ManjaroTo check if you have an older version of eventcalendar installed, run: If you see: Then you have 2 versions installed. The To enter this bug, you would have installed v66 from the Add Widgets > Download New Widgets. It installs to Later on, the user may have noticed Since the user never uninstalled the To fix, delete the KDE NeonFor users in other distros, the Discover updater used to update widgets in To fix, delete the |
|
If only I had came here first. I ended up coming to the same solution after 2 hours of messing about 😆 I had an old version installed and it crashed plasmashell after an update. I ended up removing my Eventually I found that I had to manually remove the local folder as described above. For some reason KDE doesn't seem to be able to do it from the widget gui menu. IIRC I also had similar problems trying to install it from there in the first place.
There is probably a way to have it auto update but from my experience on Arch even the normal non AUR updates are manual by default. And thank you so much for making this widget! It is vastly superior to all other clocks I have tried. 😃 |
|
I was struggling with this crash for a while until I finally found it may be related to eventcalendar, and then Googling that led me here. I only had the
That depends. AUR is stuff not officially supported, so it's a case of "you are on your own, it's your responsibility to keep stuff in order." Some people do everything manually, while others, like me, use a so called "AUR helper" which is like a package manager for AUR, so when I run a system update it updates everything, AUR included. I think the issue is that lot of people, me included, uses or used the "Add Widgets > Download New Widgets" route to get plasmoids. |
|
I'm not sure if I'd be butting in here, or adding to the topic. "Crash on arch (Qt 5.15.1)" fits my issue, which is also connected to qt5-declarative. In my case, it's not EventCalandar, but the much more basic PanelSpacer. In short, setting a panel spacer to be flexible vs. static, crashes plasmashell, and the segfault is coming from libQt5Qml 5.15.1. The twist is that this issue only manifests in archlinux32, and not at all with the 64-bit archlinux. For example, this code works on both platforms: This works only on the 64-bit platform, but causes a plasmashell crash on the 32-bit platform: Same with this this - works on 64-bit arch, crashes plasmashell on 32-bit arch32: I'm attaching the stack strace which poiints directly to QV4::QObjectWrapper::getProperty It'd be great to get some feedback on this, even if you'd prefer I open this as a separate ticket. |
|
Hello, adding to this to report that v69 of the applet still crashes latte-dock. I run Manjaro KDE and I have just updated Qt to 5.15.1, I had the eventcalendar widget on a latte dock instead of a normal plasma panel so that is what crashed upon rebooting. I have deleted the local version from Discover and installed v69 from the AUR, now the behaviour with regular plasma panels is as expected but if I add the widget to my latte dock then that is not able to restart (manually or via reboot). |
|
https://www.reddit.com/r/kde/comments/j48t0f/today_in_my_kde_manjaro_after_an_update_and_a/ Has a screenshot with a stacktrace. It seems the It appears to be some bug in I still need to do some testing to reproduce that this fixes it, as I remember being uncertain that was the right commit when I first tested in an Arch VM. |
|
Ooooh, looks like It looks like the // PopupView.qml (FullRepresentation)
MouseArea {
ColumnLayout {
anchors.fill: parent
ColumnLayout {
Layout.fillWidth: true
Layout.fillHeight: true
MeteogramView {}
TimerView {}
MonthView {}
AgendaView {}
}
}
} |
|
@itsmeciao I can seem to reproduce the
Can you run the following? |
Zren
changed the title
Zren
changed the title
|
Hello @Zren, sorry for some reason I didn't get notified when you mentioned me, I just casually found your comment while coming to check if there were any updates.
I have just tried readding eventcalendar to my latte docks and it looks like I cannot reproduce the crash anymore either. Which is strange because, other than removing eventcalendar from the docks and placing another digital clock widget, I have not made any changes to my system these past days, and Manjaro hasn't received updates since. So now I have just readded the widget to both screen's docks, applied different settings to them and I will try to play around with them a little and see if I can spot anything unusual again. Thanks and sorry again that I did not see your comment. |
I don't know what version to provide. But it's necessary to bring up an issue anyway. In AUR someone also mention it.
The text was updated successfully, but these errors were encountered: