Summary: | ~kde-base/printer-applet-4.3.2 crash: printer-applet-kde refuses to start | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Rahul Jain <rahul> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | frares, fridge.batta, ghutzl, reavertm |
Priority: | High | Flags: | tampakrap:
Bugday+
|
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Rahul Jain
2009-10-13 20:39:35 UTC
Please try to get some valuable backtrace. printer-applet is a python application, so it should be possible to get full backtrace. Oh, I cannot reproduce it and I'm using 4.3.9999 (same code in printer-applet as in 4.3.2). OK, I tried to get a trace using python-ptrace (gdb does not recognize printer-applet-kde as an executable) and here is what I get. Please tell me if there is any other way / better way of doing this. rahul@googly ~ $ strace.py -v /usr/bin/printer-applet-kde execve(/usr/bin/printer-applet-kde, ['/usr/bin/printer-applet-kde'], [/* 40 vars */]) = 11068 Attach <PtraceProcess #11068> to debugger Set <PtraceProcess #11068> options to 1 brk(NULL) = 0x08cc1000 access('/etc/ld.so.preload', <R_OK> (4)) = -2 (No such file or directory) open('/etc/ld.so.cache', O_RDONLY) = 3 fstat64(3, 0xbff30808) = 0 mmap2(NULL, 130722, <PROT_READ> (1), 2, 3, 0) = 0xb789f000 close(3) = 0 open('/lib/libc.so.6', O_RDONLY) = 3 read(3, 0xbff30924, 512) = 512 (0x00000200) fstat64(3, 0xbff3084c) = 0 mmap2(NULL, 4096, <PROT_READ|PROT_WRITE> (3), 34, -1, 0) = 0xb789e000 mmap2(NULL, 1325352, <PROT_READ|PROT_EXEC> (5), 2050, 3, 0) = 0xb775a000 mmap2(0xb7898000, 12288, <PROT_READ|PROT_WRITE> (3), 2066, 3, 318) = 0xb7898000 mmap2(0xb789b000, 10536, <PROT_READ|PROT_WRITE> (3), 50, -1, 0) = 0xb789b000 close(3) = 0 mmap2(NULL, 4096, <PROT_READ|PROT_WRITE> (3), 34, -1, 0) = 0xb7759000 set_thread_area(<user_desc entry_number=6L, base_addr=3077936832L, limit=1048575L, _bits_='Q'>) = 0 mprotect(0xb7898000, 8192, 1) = 0 mprotect(0x0804d000, 4096, 1) = 0 mprotect(0xb78dc000, 4096, 1) = 0 munmap(0xb789f000, 130722) = 0 brk(NULL) = 0x08cc1000 brk(0x08ce2000) = 0x08ce2000 open('/usr/lib/locale/locale-archive', <O_LARGEFILE> (0100000)) = 3 fstat64(3, 0xb789aae0) = 0 mmap2(NULL, 2097152, <PROT_READ> (1), 2, 3, 0) = 0xb7559000 mmap2(NULL, 4096, <PROT_READ> (1), 2, 3, 569) = 0xb78be000 close(3) = 0 Debugger error: [ProcessSignal] Signal signal<133> Traceback (most recent call last): File "/usr/bin/strace.py", line 248, in _main self.runDebugger() File "/usr/bin/strace.py", line 236, in runDebugger self.syscallTrace(process) File "/usr/bin/strace.py", line 182, in syscallTrace self.syscall(process) File "/usr/bin/strace.py", line 186, in syscall syscall = state.event(self.syscall_options) File "/usr/lib/python2.6/site-packages/ptrace/debugger/syscall_state.py", line 13, in event return self.exit() File "/usr/lib/python2.6/site-packages/ptrace/debugger/syscall_state.py", line 38, in exit self.process.waitSignals(SIGTRAP) File "/usr/lib/python2.6/site-packages/ptrace/debugger/process.py", line 712, in waitSignals return self.debugger.waitSignals(*signals, **{'pid': self.pid}) File "/usr/lib/python2.6/site-packages/ptrace/debugger/debugger.py", line 176, in waitSignals raise event ProcessSignal: Signal signal<133> Quit debugger Terminate <PtraceProcess #11068> Maybe this is what you were looking for: rahul@googly ~ $ python -m trace --count /usr/bin/printer-applet-kde Traceback (most recent call last): File "/usr/lib/python2.6/runpy.py", line 122, in _run_module_as_main "__main__", fname, loader, pkg_name) File "/usr/lib/python2.6/runpy.py", line 34, in _run_code exec code in run_globals File "/usr/lib/python2.6/trace.py", line 813, in <module> main() File "/usr/lib/python2.6/trace.py", line 801, in main t.run('execfile(%r)' % (progname,)) File "/usr/lib/python2.6/trace.py", line 498, in run exec cmd in dict, dict File "<string>", line 1, in <module> File "/usr/bin/printer-applet-kde", line 66, in <module> from statereason import StateReason ImportError: No module named statereason Does your printer-applet package install statereason.py? Do you have system-config-printer-common installed? Please wait a bit for system-config-printer-common1.1.13 to be added to tree, it may fix your issue. (In reply to comment #4) > Does your printer-applet package install statereason.py? googly rahul # find / -iname "statereason.py" /usr/share/system-config-printer/statereason.py /usr/share/apps/printer-applet/statereason.py > Do you have system-config-printer-common installed? googly rahul # eix system-config-printer-common [I] app-admin/system-config-printer-common Available versions: (~)1.1.8 (~)1.1.12 (~)1.1.13[1] {doc} Installed versions: 1.1.13[1](09:11:00 09/24/09)(-doc) Homepage: http://cyberelk.net/tim/software/system-config-printer/ Description: Common modules of Red Hat's printer administration tool [1] "kde" /usr/local/portage/layman/kde-testing > Please wait a bit for system-config-printer-common1.1.13 to be added to tree, > it may fix your issue. > Well, I already have it installed (kde-testing overlay). Maybe the inclusion in portage fixes it .... how I don't know (unless there is an update I am not aware of). I reinstalled the following packages: app-admin/system-config-printer-common-1.1.13 kde-base/system-config-printer-kde-4.3.2 kde-base/printer-applet-4.3.2 It did not solve my problem. Well, I'm running out of ideas, your sip and PyQt4 version? your could try to run emerge -vaDu world to ensure system is in consistent state. Also, have you been upgrading python recently? (and/or for instance switched to python3) dev-python/sip-4.9 dev-python/PyQt-4.6 Both from the qting-edge overlay. This could be the problem. (In reply to comment #8) > dev-python/sip-4.9 > dev-python/PyQt-4.6 > > Both from the qting-edge overlay. This could be the problem. > I have the same error. Next command solved it. Try that: printer-applet-kde --show perhaps this bug is a reflex in a bug somewhere else $ printer-applet-kde --show ASSERT failure in QDBusConnection::registerObject: "Invalid object path given", file qdbusconnection.cpp, line 706 KCrash: Application 'printer-applet-kde' crashing... Is this still a problem with more recent versions (kde, pyqt, sip, ...)? This problem is resolved in recent versions. Please, close bug I'm sorry, there is no problem for kde 4.4, but i don't know what about 4.3 Well 4.3 is gone now... printer-applet crashed too. KDE 4.7.4 denise@LAPdenise ~ $ printer-applet-kde KCrash: Application 'printer-applet-kde' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit sock_file=/home/denise/.kde4/socket-LAPdenise/kdeinit4__0 Any ideas? |