Summary: | Plasma crashes on startup after a faulty python-qt update (Debian Testing) | ||
---|---|---|---|
Product: | [Unmaintained] plasma4 | Reporter: | Raúl <erre.benito> |
Component: | scriptengines | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DOWNSTREAM | ||
Severity: | crash | CC: | abdeb, agharti81, amerikasend, andresbajotierra, asraniel, axel101, belion, jack192.168, kelvalok, msoos, p.zdunek90 |
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Raúl
2009-11-16 11:25:48 UTC
Bug 214776 looks indeed related, so I would do the same question: - Are your python-qt , python-kde (kdebindings) packages updated ? The crash seems to be caused by a version mismatch between Python/Python-Qt/Qt as you probably have some python widget in your desktop. Thanks (In reply to comment #1) > Bug 214776 looks indeed related, so I would do the same question: > > - Are your python-qt , python-kde (kdebindings) packages updated ? > The crash seems to be caused by a version mismatch between Python/Python-Qt/Qt > as you probably have some python widget in your desktop. > > Thanks Doing an "aptitude update && aptitude full-upgrade" shows all packages to be up to date, with the usual "no packages will be updated, installed or removed". The versions of those packages installed on my system are as follows: python-qt4: 4.6-1 python-kde4: 4:4.2.2-3 As far as I can tell, those are the latest available for Debian Testing (so I guess upgrading to the versions from the unstable repos or deleting my plasma config file could do the trick, but I won't do either yet just in case a better solution is found). If you need any more info, I'll be happy to do what I can to provide it. Thanks. You have "python-kde4: 4:4.2.2-3" while your KDE is 4.3.2. In the debian page I see "python-kde4 4:4.3.2-1" in Sid. So I guess this could be a Debian problem, or may be they simply need to recompile their python-kde4 package or something... (In reply to comment #3) > You have "python-kde4: 4:4.2.2-3" while your KDE is 4.3.2. In the debian page I > see "python-kde4 4:4.3.2-1" in Sid. > So I guess this could be a Debian problem, or may be they simply need to > recompile their python-kde4 package or something... I don't have the Sid repos enabled, and python-kde4 4:4.2.2-3 is the latest available in the Testing repos. But there was an upgrade for some python packages that I applied yesterday (I think python-qt4 was one of them), which may be the cause for this crash. If deleting my plasma config doesn't work I'll try upgrading those packages to the versions in Sid, and I'll report back either way. I think the problem is that python-kde4 (even the old "4.2.2" version) should be recompiled against this new python-qt version. Otherwise it will fail like this. *** Bug 214776 has been marked as a duplicate of this bug. *** I just asked to the Debian-KDE packagers and they told me it is a Python-qt problem, which is fixed in Unstable and it should arrive into Testing soon. In the meanwhile try not using Python widgets in your desktop. (you may need to move out your Plasma config files to start with a clean config, sorry) Regards Ok, I just installed the python-kde4 package from the unstable repositories (version 4.3.2-1); restarted plasma and now it is working again. Thank you so much, Dario! Thanks for confirming that the update fixes the problem. You are welcome Upgrading python-kde4 to the version in the unstable repos fixed it for me too. Thanks for your help. *** Bug 215163 has been marked as a duplicate of this bug. *** I have deleted my widgtes (all of them from google) from ~/.kde/share/apps/plasma, and now kde starts fine... removing python plasmoid, or upgrading to the unstable package also fixes the problem for me (using debian testing) *** Bug 215680 has been marked as a duplicate of this bug. *** *** Bug 215988 has been marked as a duplicate of this bug. *** *** Bug 216713 has been marked as a duplicate of this bug. *** *** Bug 217327 has been marked as a duplicate of this bug. *** *** Bug 217780 has been marked as a duplicate of this bug. *** *** Bug 212876 has been marked as a duplicate of this bug. *** *** Bug 218524 has been marked as a duplicate of this bug. *** |