Summary: | kde-base/printer-applet keeps crashing on kde startup or when run manually | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Markus Wernig <public> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | navid.zamani |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Markus Wernig
2012-01-27 10:31:23 UTC
Ran python-updater, did not solve problem. statereason.py does not seem to be the reason: $ export PYTHONPATH=/usr/share/apps/printer-applet $ python -m trace --count /usr/bin/printer-applet-kde KCrash: Application 'printer-applet-kde' crashing... KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit sock_file=/home/markus/.kde4/socket-envy/kdeinit4__0 Still crashes, but no stacktrace ... Unable to reproduce. Worked with 4.7.4 and 4.8.0 as well. You're still on portage-2.1 therefore I suspect some preserved-lib problem (or rather a consequence of the lack of thereof and thus the need to run revdep-rebuild). What do you mean "still on portage-2.1"? Afaik, Portage is currently at 2.1.10.44 for ~amd64 :-) * sys-apps/portage Latest version available: 2.1.10.44 Latest version installed: 2.1.10.44 Size of files: 763 kB Homepage: http://www.gentoo.org/proj/en/portage/index.xml Description: Portage is the package management and distribution system for Gentoo License: GPL-2 One thing I noted: I have another gentoo machine, which I had been constantly upgrading over the years (reactivated and upgraded to KDE 4.8.0 in order to reproduce this bug) - and it does not show the same behaviour. The machine this bug occurred on is a fresh install that was rebuild from the world file of another working installation (with KDE 4.7.4 on ~x86, which did not show the bug). So one of the differences seems to be that on the machine that shows the behaviour, everything was build together from scratch, while the other one was constantly upgraded. To me this looks like something is missing on the "new" machine, but not on the "old" one - whatever it is, it might have been installed previously, maybe by some other dependency, which is now missing. I have run revdep-rebuild multiple times - to no avail: # revdep-rebuild * Configuring search environment for revdep-rebuild * Checking reverse dependencies * Packages containing binaries and libraries broken by a package update * will be emerged. * Collecting system binaries and libraries * Generated new 1_files.rr * Collecting complete LD_LIBRARY_PATH * Generated new 2_ldpath.rr * Checking dynamic linking consistency [ 100% ] * Dynamic linking on your system is consistent... All done. I mean you're not using portage-2.2 ("masked" but rocking) with preserved-libs feature (no more revdep-rebuild needed in theory and in most cases in practice). Well, you could try the recipe from bug 399261: eselect python set python2.7 python-updater emerge --depclean revdep-rebuild Os otherwise ensure that PyQt4, pykde4 is rebuilt for currently selected python before runnig/installing printer-applet (and system-config-printer-kde which likely fails for you as well). Problem still not solved. I've done: python-updater emerge --depclean revdep-rebuild emerge system-config-printer-common emerge system-config-printer-kde emerge printer-applet allways the same crash OK, remerging the whole bunch solves it for me: emerge PyQt4 && emerge sip && emerge pykde4 && emerge system-config-printer-kde && emerge printer-applet. Thanks for the tipps. (In reply to comment #7) > emerge PyQt4 && emerge sip && emerge pykde4 && emerge > system-config-printer-kde && emerge printer-applet. IMPORTANT: When doing that, be sure to use “emerge -1” for the dependencies, or they will get added to the world file!! Also, usually dependencies are installed first, so this should work exactly the same: > emerge -a1tv PyQt4 sip pykde4 system-config-printer-kde printer-applet (Added --ask, --tree and --verbose, so you can see for yourself, before starting it.) I had the exact same problem, btw. Both system-config-printer-kde and printer-applet crashed when ran. Now they work. There’s a huge load of dupes btw. I think most of them got wrongly closed because they had unknowingly re-compiled of the above packages shortly before, and so the bug didn’t show anymore. And there will be a huge load of them in the future too, unless this is fixed once and for all. Just my two cents… |